Singapore (Singnet) - Newark data centre peering problem
I have a customer in Singapore, using a mobile connection from Singnet, who has trouble accessing a VPS in the Newark data centre.
Here are his speedtests to Newark and the local Singapore data centre: https://imgur.com/a/V1rjNfA
As you can see, he has terrible latency and can't upload. I plan on moving the VPS, but thought you should be aware of this issue.
1 Reply
jhartman
Linode Staff
Although our SpeedTest tools can be a great surface-level way to determine connection speeds between yourself and our various data centers, our Support & Admin Teams require a bit more verbose information to be able troubleshoot potential routing issues. Specifically, we ask that you and/or your clients provide bi-directional MTR Reports that capture the traffic between yourself and the target Linode.
In order to gather all of the necessary information about the route, as well as any unexpected latency or packet loss, we ask that you open a ticket (or respond to an existing one) with the full output of the following MTR syntax:
From your client device/computer to your Linode:
mtr -rwbzc100 $LINODE_IP
From your Linode to your client/computer:
mtr -rwbzc100 $LOCAL_IP
The additional option flags provide the following outputs which are useful for both teams during our investigation:
- r: Report Mode, which runs for the number of cycles specified in count (c)
- c100: Replicates the route 100 times to provide a thorough analysis of traffic. Performing a single or low cycle traceroute may not accurately or definitely prove on-going issues or can misrepresent intermittent issues as if they are ongoing
- w: Wide Mode provides the full hostname of each hop
- b: Displays both the hostname and IP address of each hop
- z: Provides the Autonomous System (AS) number associated with each hop
Similar to our Community Posts, our tickets can render basic Markdown notation, so we ask that you submit the MTR results using individual "code blocks/fences". These code blocks will help make sure the results are presented in a clean, organized manner like this:
example command input:
MTR output
By providing us with these results, we can help identify either issues with the Linode or traffic routes themself, and when possible, escalate accordingly to fix issues with our infrastructure or with outbound peering neighbors.