CrowdSupport Wiki

Broadband & nbn™

cancel

International routing, latency and ping

Many people contact us in regards to latency (high pings) issues that they are experiencing within the BigPond network.  Please be aware that there are many factors (apart from routing) that contribute to latency.

Some common factors include:

  • The physical distance between hops on the network (a latency result of 170-200ms would be expected when connecting to a server in the US)
  • Using a wireless connection to your router.
  • The configuration of any firewalls or antivirus programs.
  • Your internet connection speed (or the utilisation of the bandwidth), either on the your individual service, or in the local exchange (congestion)
  • Retransmissions and/or errors within the network, as each hop can increase the latency slightly during conversion and routing processes.
  • TCP stack / network protocol engineering

What we need to remember is that regardless of how advanced the technology is, networking is limited to the speed of electricity and light.

Any tests conducted from a ping or traceroute may be considered low priority traffic, and that missed hops or intermittent drops may not actually be indicative of a fault condition. Network devices may be set up with queuing, policing, blocking etc. This may be to protect the network from reconnaissance, denial of service or to give priority to time sensitive traffic, VOIP for example. 

If you believe you are experiencing latency you can try the following basic troubleshooting:

  • Connect your device directly to your modem via an Ethernet cable.  A direct Ethernet connection gives you a better flow of data. 
  • Make sure no one else is using your internet connection.  Kick other users off, check to see what other devices are connected and turn them off or disconnect their connection.
  • Check what other applications are running in the background using your bandwidth, and turn them off.  Examples of these applications include Peer-2-peer/torrenting programs downloading and uploading music and video, cloud services syncing data to the cloud and Malware or virus’ and in some cases, Internet Browser Add-ons or extensions.
  • Other applications which may be limiting your connection are firewalls and antivirus programs.  Many firewalls substantially slow down internet connection speed. Disabling firewalls that directly monitor web traffic will lower your ping. (Please be aware that doing this will open your device up to risks of contracting a virus)
  • Choose a server which is the geographically closest to you. The following map shows the international links Telstra Global maps, try for the shortest.
  • Reset your modem to factory default settings.
  • You could also try changing your DNS settings, try the Google public DNS server (8.8.8.8, 8.8.4.4) and see if there is any change.
  • Test on a different device to see if it is a device issue or a network issue.

As pings and traceroutes may be treated as low priority traffic, it is important to keep this in mind when using test tools 

Please be aware that BigPond doesn't guarantee any set Pings times or Latency, so our Technical Support team will be unable to help in this area. Further reading: How to optimise your gaming performanceOur Customer Terms.


More information

The internet is a network of interconnecting servers, each one is owned by various entities and providers. When reporting issues with routing, your service provider may not be able to escalate the issue directly to the owner of the affected server.

This is reflected in a similar way to reporting a broadband fault in Australia, the user needs to contact their ISP to report the fault, who then contacts the owner of the physical infrastructure to investigate and resolve. The same happens on a larger scale with routing issues. 

Due to the number of organisations that the issue may need to be escalated through, it can take some time for the communication to reach the provider needing to complete the work, and may be resolved faster if reported by the provider closest to the problem server.

In the below traceroute example, a problem with routing in the AT&T network would be escalated from Telstra BigPond to Telstra Global, who will escalate to Savvis, who escalates it to AT&T. If the problem was within Savvis, then the quickest path to report this is via AT&T.  You can find out more about peering here.
 

Telstra
Tracing the route to 12.129.209.68
VRF info: (vrf in name/id, vrf out name/id)
1 bundle-ether3-100.exi-core1.melbourne.telstra.net (203.50.80.1) 4 msec 4 msec 4 msec
2 bundle-ether12.chw-core2.sydney.telstra.net (203.50.11.74) 18 msec 15 msec 16 msec
3 bundle-ether1.oxf-gw2.sydney.telstra.net (203.50.6.90) 19 msec 19 msec 16 msec
4 203.50.13.38 16 msec 20 msec 16 msec
5 i-0-4-0-1.paix-core01.bx.telstraglobal.net (202.84.249.57) [AS 4637] 162 msec
i-0-4-0-3.paix-core01.bx.telstraglobal.net (202.84.140.70) [AS 4637] 164 msec
i-0-4-0-4.paix-core01.bx.telstraglobal.net (202.84.140.90) [AS 4637] 164 msec
6 i-0-4-0-6.paix02.bi.telstraglobal.net (202.40.149.58) [AS 4637] 162 msec
i-0-0-0-0.paix02.bi.telstraglobal.net (202.84.251.70) [AS 4637] 161 msec 162 msec
7 205.216.164.9 173 msec
206.24.240.149 172 msec
205.216.164.9 174 msec
8 esr2-xe-8-0-0.pax.savvis.net (204.70.192.38) 174 msec
esr2-xe-4-0-0.pax.savvis.net (204.70.192.34) 173 msec 173 msec
9 er1-ten-7-0-0.sjq.savvis.net (204.70.200.202) 173 msec
er1-ten-9-4.sjq.savvis.net (206.28.98.181) 173 msec
er1-ten-4-8.sjq.savvis.net (206.28.96.198) 172 msec
10 er2-xe-7-0-0.SanJoseEquinix.savvis.net (204.70.198.142) 173 msec 174 msec 205 msec
11 192.205.33.97 180 msec 180 msec 179 msec
12 cr1.sffca.ip.att.net (12.122.114.54) [MPLS: Label 17327 Exp 0] 179 msec 179 msec 180 msec
13 cr1.la2ca.ip.att.net (12.122.3.122) [MPLS: Labels 0/17309 Exp 0] 178 msec 175 msec 176 msec
14 gar5.lsrca.ip.att.net (12.122.85.33) 173 msec 174 msec 173 msec
15 12.122.251.186 175 msec 174 msec 174 msec
16 206.16.68.42 175 msec 174 msec
206.16.68.50 176 msec

 
In the following examples, you can see that the ping time between each service provider and their international routing peer are very similar.

iiNET
Tracing the route to 12.129.209.68
1 gi2-35.mel-pipe-bdr1.iinet.net.au (203.215.6.43) 0 msec 4 msec 0 msec
2 ae6-15.cr1.mel4.on.ii.net (150.101.33.102) 4 msec 0 msec 0 msec
3 ae2.br1.syd7.on.ii.net (150.101.33.28) 16 msec 16 msec 12 msec
4 te-0-2-1-3.br1.sjc2.on.ii.net (150.101.33.251) 169 msec
te0-1-1-2.br1.sjc2.on.ii.net (150.101.33.193) 188 msec
te0-2-1-2.br1.sjc2.on.ii.net (150.101.33.147) 168 msec
5 sl-st31-sj-.sprintlink.net (144.232.191.193) 172 msec 173 msec 172 msec
6 144.232.1.70 196 msec 204 msec 240 msec
7 cr2.sffca.ip.att.net (12.122.200.14) 173 msec 168 msec 176 msec
8 cr2.la2ca.ip.att.net (12.122.31.133) 169 msec 168 msec 172 msec
9 12.123.132.209 172 msec 164 msec 168 msec
10 12-122-254-230.attens.net (12.122.254.230) 201 msec 201 msec 200 msec
11 206.16.68.50 168 msec 164 msec
mdf001c7613r0003-gig-10-1.lax1.attens.net (12.129.193.242) 172 msec

 

TPG

Tracing the route to 12.129.209.68
1 Sydney-ge-3-1-0.tpgi.com.au (202.7.173.241) 12 msec
syd-pow-cla-crt-2-pos-5-0.tpgi.com.au (202.7.162.210) 0 msec
Sydney-ge-3-1-0.tpgi.com.au (202.7.173.241) 8 msec
2 syd-pow-cla-crt1-ge-6-1-0.tpgi.com.au (202.7.171.166) 12 msec
syd-nxg-men-crt2-ge-3-0-0.tpgi.com.au (202.7.162.194) 12 msec
syd-pow-cla-crt1-ge-6-1-0.tpgi.com.au (202.7.171.166) 12 msec
3 hagg-04-xe-0-2-0.ptld.twtelecom.net (66.193.45.5) 152 msec
66.162.129.149 152 msec
hagg-04-xe-0-2-0.ptld.twtelecom.net (66.193.45.5) 152 msec
4 64-129-238-70.static.twtelecom.net (64.129.238.70) 156 msec 156 msec 156 msec
5 12.118.34.9 156 msec 156 msec 156 msec
6 cr2.st6wa.ip.att.net (12.122.146.210) [MPLS: Label 17022 Exp 1] 188 msec 188 msec 188 msec
7 cr2.ptdor.ip.att.net (12.122.30.149) [MPLS: Labels 22489/17331 Exp 1] 188 msec 188 msec 188 msec
8 12.122.2.74 [MPLS: Labels 22701/17331 Exp 1] 192 msec 188 msec 188 msec
9 cr2.la2ca.ip.att.net (12.122.31.133) [MPLS: Labels 0/17331 Exp 1] 188 msec 188 msec 184 msec
10 12.123.132.209 188 msec 184 msec 184 msec
11 12-122-254-226.attens.net (12.122.254.226) 188 msec 188 msec 188 msec
12 206.16.68.42 184 msec
mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246) 184 msec
206.16.68.50 184 msec

 

AAPT
Tracing the route to 12.129.209.68
1 gi9-11.mburndist01.nw.aapt.net.au (202.10.15.156) [MPLS: Label 148 Exp 0] 8 msec
gi9-11.mburndist02.nw.aapt.net.au (202.10.15.158) [MPLS: Label 148 Exp 0] 8 msec
gi9-11.mburndist01.nw.aapt.net.au (202.10.15.156) [MPLS: Label 148 Exp 0] 16 msec
2 te2-1-110.mburndist01.aapt.net.au (202.10.12.138) [MPLS: Labels 1288/1398 Exp 0] 12 msec
te0-3-4-0.mburncore01.aapt.net.au (202.10.12.15) [MPLS: Labels 17466/1398 Exp 0] 16 msec
te2-1-110.mburndist01.aapt.net.au (202.10.12.138) [MPLS: Labels 1288/1398 Exp 0] 12 msec
3 bu2.sclarcore01.aapt.net.au (202.10.10.74) [MPLS: Labels 17875/1398 Exp 0] 12 msec
te0-3-4-0.mburncore01.aapt.net.au (202.10.12.15) [MPLS: Labels 17704/1398 Exp 0] 12 msec
bu2.sclarcore01.aapt.net.au (202.10.10.74) [MPLS: Labels 17875/1398 Exp 0] 12 msec
4 bu2.sclarcore01.aapt.net.au (202.10.10.74) [MPLS: Labels 17556/1398 Exp 0] 12 msec
te2-2.sclardist01.aapt.net.au (202.10.12.2) [MPLS: Label 1398 Exp 0] 16 msec
bu2.sclarcore01.aapt.net.au (202.10.10.74) [MPLS: Labels 17556/1398 Exp 0] 12 msec
5 bu8.sclarbrdr11.aapt.net.au (202.10.14.23) 12 msec
te2-2.sclardist01.aapt.net.au (202.10.12.2) [MPLS: Label 1398 Exp 0] 16 msec
bu8.sclarbrdr11.aapt.net.au (202.10.14.23) 12 msec
6 bu8.sclarbrdr11.aapt.net.au (202.10.14.23) 12 msec
203-219-106-137.tpgi.com.au (203.219.106.137) [AS 7545] 16 msec
bu8.sclarbrdr11.aapt.net.au (202.10.14.23) 12 msec
7 203-219-35-67.static.tpgi.com.au (203.219.35.67) [AS 7545] 16 msec
203-219-106-137.tpgi.com.au (203.219.106.137) [AS 7545] 12 msec
203-219-35-67.static.tpgi.com.au (203.219.35.67) [AS 7545] 16 msec
8 203-219-35-67.static.tpgi.com.au (203.219.35.67) [AS 7545] 16 msec
te0-0-0-2.ccr21.lax04.atlas.cogentco.com (38.104.210.9) [AS 174] 184 msec
203-219-35-67.static.tpgi.com.au (203.219.35.67) [AS 7545] 12 msec
9 be2076.mpd22.lax01.atlas.cogentco.com (154.54.2.166) [AS 174] 188 msec
te0-0-0-2.ccr21.lax04.atlas.cogentco.com (38.104.210.9) [AS 174] 188 msec
be2019.ccr21.lax01.atlas.cogentco.com (154.54.88.9) [AS 174] 188 msec
10 be2019.ccr21.lax01.atlas.cogentco.com (154.54.88.9) [AS 174] 192 msec
be2178.ccr23.lax05.atlas.cogentco.com (154.54.41.118) [AS 174] 188 msec
be2021.mpd21.lax01.atlas.cogentco.com (154.54.87.249) [AS 174] 188 msec
11 att.lax05.atlas.cogentco.com (154.54.13.150) [AS 174] 204 msec
be2178.ccr23.lax05.atlas.cogentco.com (154.54.41.118) [AS 174] 188 msec
att.lax05.atlas.cogentco.com (154.54.13.150) [AS 174] 204 msec
12 att.lax05.atlas.cogentco.com (154.54.13.150) [AS 174] 204 msec
cr1.la2ca.ip.att.net (12.123.132.138) [AS 7018] [MPLS: Label 17309 Exp 0] 204 msec
att.lax05.atlas.cogentco.com (154.54.13.150) [AS 174] 204 msec
13 gar5.lsrca.ip.att.net (12.122.85.33) [AS 7018] 200 msec
cr1.la2ca.ip.att.net (12.123.132.138) [AS 7018] [MPLS: Label 17309 Exp 0] 200 msec
gar5.lsrca.ip.att.net (12.122.85.33) [AS 7018] 232 msec
14 gar5.lsrca.ip.att.net (12.122.85.33) [AS 7018] 200 msec
12.122.251.186 [AS 7018] 200 msec
gar5.lsrca.ip.att.net (12.122.85.33) [AS 7018] 204 msec
15 206.16.68.42 [AS 17233] 200 msec
12.122.251.186 [AS 7018] 376 msec
206.16.68.42 [AS 17233] 200 msec
16 206.16.68.42 [AS 17233] 200 msec * 
206.16.68.50 [AS 17233] 200 msec

Version history
Revision #:
27 of 27
Last update:
May 2018
Updated by:
 

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
Find out more about the Telstra 24x7 App ×
Manage your services and take advantage of offers while you’re out and about with the Telstra 24x7® App Download now
Earn points on our new rewards program and enjoy tier benefits like discounted movie tickets and moreFind out more

Need a hand or want to share your expertise?
Register for CrowdSupport and get involved

Register now