CrowdSupport®
Qy
Level 3: Gumshoe

Telstra introduced lag into the internet network

I have done a tracert from my home using my computer, using 2 internet providers Telstra & TPG

 

The results have shocked me

 

Tracert From Telstra

 

tracert 162.245.204.234


Tracing route to 162.245.204.234 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.0.0.138
  2     *        *        *     Request timed out.
  3    12 ms    12 ms    15 ms  CPE-58-160-252-2.wa.bigpond.net.au [58.160.252.2]
  4    19 ms    12 ms    12 ms  bundle-ether4.pie-edge902.perth.telstra.net [203.50.112.52]
  5    14 ms    15 ms    15 ms  bundle-ether7.pie-core1.perth.telstra.net [203.50.6.188]
  6    48 ms    40 ms    40 ms  bundle-ether6.way-core4.adelaide.telstra.net [203.50.11.16]
  7    53 ms    53 ms    57 ms  bundle-ether9.exi-core10.melbourne.telstra.net [203.50.11.93]
  8    73 ms    66 ms    69 ms  bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]
  9    65 ms    71 ms    63 ms  bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]
 10    65 ms    67 ms    66 ms  bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]
 11    70 ms    66 ms    67 ms  i-0-1-0-17.sydo-core04.bi.telstraglobal.net [202.84.222.62]
 12   251 ms   251 ms   247 ms  i-34.eqnx-core01.bx.telstraglobal.net [202.84.136.33]
 13   362 ms   318 ms   319 ms  i-0-4-0-3.ny8a-core01.bi.telstraglobal.net [202.40.149.169]
 14   309 ms   315 ms   311 ms  i-0-1-0-2.tnrt-core01.bi.telstraglobal.net [202.84.137.69]
 15   429 ms   397 ms   400 ms  i-0-3-0-2.ulhc-core01.bx.telstraglobal.net [202.84.143.230]
 16   390 ms   395 ms   391 ms  202.84.178.10
 17     *        *        *     Request timed out.
 18   411 ms   401 ms   422 ms  20ge.cr0-fr0.smartdc.rtm.i3d.net [109.200.218.77]
 19   411 ms   411 ms   409 ms  20ge.lr0-cr0.th-n.lhr.i3d.net [109.200.218.153]
 20   482 ms   486 ms   499 ms  10ge.iadr0-lr0.csva01.iad.i3d.net [109.200.218.150]
 21   531 ms   524 ms   524 ms  10ge.dfwr0-iadr0.vwdal01.dfw.i3d.net [109.200.218.189]
 22   541 ms   543 ms   549 ms  10ge.laxr0-dfwr0.csla02.lax.i3d.net [109.200.218.193]
 23   547 ms   546 ms   546 ms  162.245.204.234

Trace complete.

 

tracert From TPG

 

tracert 162.245.204.234

Tracing route to 162.245.204.234 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  10.0.0.139
  2    25 ms    25 ms    25 ms  xx.xx.xx.xx
  3    25 ms    25 ms    27 ms  202-7-180-233.static.tpgi.com.au [202.7.180.233]
  4    25 ms    24 ms    25 ms  bri-nxg-alf-crt2-POS-5-1.tpgi.com.au [202.7.171.245]
  5    81 ms    77 ms    79 ms  syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au [203.26.22.105]
  6   168 ms    80 ms   156 ms  203-221-3-3.tpgi.com.au [203.221.3.3]
  7   225 ms   234 ms   228 ms  as49544.any2-la.coresite.com [206.72.211.4]
  8   227 ms   227 ms   227 ms  162.245.204.234

Trace complete.

 

The destination is the same, and the my home is the sourse.

 

As you can see Telstra take 23 hops to get to the location

and TPG takes 8 hops for the same location.

 

AS you can see Telstras has double the response time as TPG.

so when your bowser asks sends a request to the other end Telstra takes twice a long to get there.

 

Also Telstra seems to be trying to use all the routers it has and this adds to the delay in the network.

TPG can do the same job using 1/3 as many hops as Telstra. in a shorter time.

 

If you want to try this for yourself just ping an if address and see (eg: in a command window type ping 162.245.204.234)

and if you have another internet or a friend is not with telstra then get them to do the ping test (ping 162.245.204.234)

The ping comand just gives you a delay and does not show you all the paths inbetween.

 

 

and post your reply here.

 

My ping test using Telstra

 

ping 162.245.204.234

 

Pinging 162.245.204.234 with 32 bytes of data:

Reply from 162.245.204.234: bytes=32 time=549ms TTL=43

Reply from 162.245.204.234: bytes=32 time=546ms TTL=43

Reply from 162.245.204.234: bytes=32 time=547ms TTL=43

Reply from 162.245.204.234: bytes=32 time=549ms TTL=43

 

Ping statistics for 162.245.204.234:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 546ms, Maximum = 549ms, Average = 547ms

 

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
12 REPLIES 12
Telstra (Retired)
Telstra (Retired)

Re: Telstra introduced lag into the internet network

Hi Qy, 

 

In the Telstra network pings and traceroutes are considered low priority traffic and may reflect increased response times as other traffic is prioritised. It is important to keep this in mind when using test tools.

For more information see: 

 

http://crowdsupport.telstra.com.au/t5/General-Internet-KB/International-routing-latency-and-ping/ta-...

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Hi Kenobi

 

Thanks for your response, nice try at an answer but it seems to be incorrect.

 

Yes it is true that ICMP can be routed via different paths and since tracert on windows uses ICMP this also applies to using tracert.

 

 It’s true Telstra can do whatever they like with protocol, drop it, send it the long way around etc.

But do they, I don’t thinks so.

 

So I decided to test it with the TCP protocol since that is what web browsers and emails use and I assume this protocol is high priority.

 

I used a trace that uses the TCP protocol.

 

Trace from Telstra using TCP

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       *       *       *       Request timed out.

2       *       *       *       Request timed out.

3       14 ms   12 ms   23 ms   58.160.252.2    [CPE-58-160-252-2.wa.bigpond.net.au]

4       14 ms   13 ms   10 ms   203.50.112.52   [bundle-ether4.pie-edge902.perth.telstra.net]

5       24 ms   11 ms   12 ms   203.50.6.188    [bundle-ether7.pie-core1.perth.telstra.net]

6       39 ms   41 ms   57 ms   203.50.11.16    [bundle-ether6.way-core4.adelaide.telstra.net]

7       55 ms   53 ms   55 ms   203.50.11.93    [bundle-ether9.exi-core10.melbourne.telstra.net]

8       87 ms   65 ms   66 ms   203.50.11.124   [bundle-ether12.chw-core10.sydney.telstra.net]

9       87 ms   66 ms   65 ms   203.50.6.93     [bundle-ether1.oxf-gw11.sydney.telstra.net]

10      69 ms   68 ms   68 ms   203.50.13.98    [bundle-ether1.sydo-core03.sydney.reach.com]

11      65 ms   68 ms   68 ms   202.84.222.66   [i-0-1-0-18.sydo-core04.bi.telstraglobal.net]

12      252 ms  246 ms  261 ms  202.84.136.33   [i-34.eqnx-core01.bx.telstraglobal.net]

13      347 ms  318 ms  354 ms  202.84.136.93   [i-0-4-0-10.ny8a-core01.bi.telstraglobal.net]

14      389 ms  443 ms  314 ms  202.84.137.69   [i-0-1-0-2.tnrt-core01.bi.telstraglobal.net]

15      384 ms  393 ms  382 ms  202.40.148.34   [i-0-0-0-0.ulco01.bi.telstraglobal.net]

16      397 ms  399 ms  380 ms  202.84.178.10

17      405 ms  *       *       109.200.218.77  [20ge.cr0-fr0.smartdc.rtm.i3d.net]

18      399 ms  398 ms  402 ms  109.200.218.5   [20ge.cr1-fr0.smartdc.rtm.i3d.net]

19      416 ms  404 ms  491 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

20      513 ms  511 ms  498 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

21      516 ms  546 ms  549 ms  109.200.218.193 [10ge.laxr0-dfwr0.csla02.lax.i3d.net]

22      541 ms  Destination Reached in 550 ms. Port closed on 162.245.204.234

Trace Complete.

 

Tracert from TPG using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       2 ms    2 ms    2 ms    hidden

2       26 ms   26 ms   26 ms   hidden

3       27 ms   25 ms   26 ms   202.7.180.233   [202-7-180-233.static.tpgi.com.au]

4       27 ms   25 ms   26 ms   202.7.171.245   [bri-nxg-alf-crt2-POS-5-1.tpgi.com.au]

5       79 ms   79 ms   81 ms   203.26.22.105   [syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au]

6       85 ms   87 ms   82 ms   203.221.3.3     [203-221-3-3.tpgi.com.au]

7       236 ms  236 ms  235 ms  206.72.211.4    [as49544.any2-la.coresite.com]

8       Destination Reached in 228 ms. Port closed on 162.245.204.234

Trace Complete.

 

As you can see the results using the TCP protocol are the same as using ping (ICMP)

Your statement,

 

 “In the Telstra network pings and traceroutes are considered low priority traffic and may reflect increased response times as other traffic is prioritised.”

Is not valid.

 

You may need to get back to Telstra to find the source of that statement.

 

My original statement “Telstra introduced lag into the internet network” still seems to hold true.

 

I have provided evidence of my statement, in return no evidence has been presented that refutes my statement.

 

AS has been demonstrated you can get a valid result by the ping and tracert commands on the Telstra network.

 

 

 

 

 

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Hi Kenobi,

 

Thanks for your response, nice try at an answer but it seems to be incorrect.

 

Yes it is true that ICMP can be routed via different paths and since tracert on windows uses ICMP this also applies to using tracert.

 

 It’s true Telstra can do whatever they like with protocol, drop it, send it the long way around etc.

But do they, I don’t thinks so.

 

So I decided to test it with the TCP protocol since that is what web browsers and emails use and I assume this protocol is high priority.

 

I used a trace that uses the TCP protocol.

 

Trace from Telstra using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       *       *       *       Request timed out.

2       *       *       *       Request timed out.

3       14 ms   12 ms   23 ms   58.160.252.2    [CPE-58-160-252-2.wa.bigpond.net.au]

4       14 ms   13 ms   10 ms   203.50.112.52   [bundle-ether4.pie-edge902.perth.telstra.net]

5       24 ms   11 ms   12 ms   203.50.6.188    [bundle-ether7.pie-core1.perth.telstra.net]

6       39 ms   41 ms   57 ms   203.50.11.16    [bundle-ether6.way-core4.adelaide.telstra.net]

7       55 ms   53 ms   55 ms   203.50.11.93    [bundle-ether9.exi-core10.melbourne.telstra.net]

8       87 ms   65 ms   66 ms   203.50.11.124   [bundle-ether12.chw-core10.sydney.telstra.net]

9       87 ms   66 ms   65 ms   203.50.6.93     [bundle-ether1.oxf-gw11.sydney.telstra.net]

10      69 ms   68 ms   68 ms   203.50.13.98    [bundle-ether1.sydo-core03.sydney.reach.com]

11      65 ms   68 ms   68 ms   202.84.222.66   [i-0-1-0-18.sydo-core04.bi.telstraglobal.net]

12      252 ms  246 ms  261 ms  202.84.136.33   [i-34.eqnx-core01.bx.telstraglobal.net]

13      347 ms  318 ms  354 ms  202.84.136.93   [i-0-4-0-10.ny8a-core01.bi.telstraglobal.net]

14      389 ms  443 ms  314 ms  202.84.137.69   [i-0-1-0-2.tnrt-core01.bi.telstraglobal.net]

15      384 ms  393 ms  382 ms  202.40.148.34   [i-0-0-0-0.ulco01.bi.telstraglobal.net]

16      397 ms  399 ms  380 ms  202.84.178.10

17      405 ms  *       *       109.200.218.77  [20ge.cr0-fr0.smartdc.rtm.i3d.net]

18      399 ms  398 ms  402 ms  109.200.218.5   [20ge.cr1-fr0.smartdc.rtm.i3d.net]

19      416 ms  404 ms  491 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

20      513 ms  511 ms  498 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

21      516 ms  546 ms  549 ms  109.200.218.193 [10ge.laxr0-dfwr0.csla02.lax.i3d.net]

22      541 ms  Destination Reached in 550 ms. Port closed on 162.245.204.234

Trace Complete.

 

Tracert from TPG using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       2 ms    2 ms    2 ms    hidden

2       26 ms   26 ms   26 ms   hidden

3       27 ms   25 ms   26 ms   202.7.180.233   [202-7-180-233.static.tpgi.com.au]

4       27 ms   25 ms   26 ms   202.7.171.245   [bri-nxg-alf-crt2-POS-5-1.tpgi.com.au]

5       79 ms   79 ms   81 ms   203.26.22.105   [syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au]

6       85 ms   87 ms   82 ms   203.221.3.3     [203-221-3-3.tpgi.com.au]

7       236 ms  236 ms  235 ms  206.72.211.4    [as49544.any2-la.coresite.com]

8       Destination Reached in 228 ms. Port closed on 162.245.204.234

Trace Complete.

 

As you can see the results using the TCP protocol are the same as using ping (ICMP)

 

Your statement,

 “In the Telstra network pings and traceroutes are considered low priority traffic and may reflect increased response times as other traffic is prioritised.”

Is not valid.

 

You may need to get back to Telstra to find the source of that statement.

 

My original statement “Telstra introduced lag into the internet network” still seems to hold true.

 

I have provides evidence of my statement, in return no evidence has been presented that refutes my statement.

 

AS has been demonstrated you can get a valid result by the use of the ping and tracert commands on the Telstra network.

 

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Hi Kenobi,

 

Thanks for your response, nice try at an answer but it seems to be incorrect.

 

Yes it is true that ICMP can be routed via different paths and since tracert on windows uses ICMP this also applies to using tracert.

 

 It’s true Telstra can do whatever they like with protocol, drop it, send it the long way around etc.

But do they, I don’t thinks so.

 

So I decided to test it with the TCP protocol since that is what web browsers and emails use and I assume this protocol is high priority.

 

I used a trace that uses the TCP protocol.

 

Trace from Telstra using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       *       *       *       Request timed out.

2       *       *       *       Request timed out.

3       14 ms   12 ms   23 ms   58.160.252.2    [CPE-58-160-252-2.wa.bigpond.net.au]

4       14 ms   13 ms   10 ms   203.50.112.52   [bundle-ether4.pie-edge902.perth.telstra.net]

5       24 ms   11 ms   12 ms   203.50.6.188    [bundle-ether7.pie-core1.perth.telstra.net]

6       39 ms   41 ms   57 ms   203.50.11.16    [bundle-ether6.way-core4.adelaide.telstra.net]

7       55 ms   53 ms   55 ms   203.50.11.93    [bundle-ether9.exi-core10.melbourne.telstra.net]

8       87 ms   65 ms   66 ms   203.50.11.124   [bundle-ether12.chw-core10.sydney.telstra.net]

9       87 ms   66 ms   65 ms   203.50.6.93     [bundle-ether1.oxf-gw11.sydney.telstra.net]

10      69 ms   68 ms   68 ms   203.50.13.98    [bundle-ether1.sydo-core03.sydney.reach.com]

11      65 ms   68 ms   68 ms   202.84.222.66   [i-0-1-0-18.sydo-core04.bi.telstraglobal.net]

12      252 ms  246 ms  261 ms  202.84.136.33   [i-34.eqnx-core01.bx.telstraglobal.net]

13      347 ms  318 ms  354 ms  202.84.136.93   [i-0-4-0-10.ny8a-core01.bi.telstraglobal.net]

14      389 ms  443 ms  314 ms  202.84.137.69   [i-0-1-0-2.tnrt-core01.bi.telstraglobal.net]

15      384 ms  393 ms  382 ms  202.40.148.34   [i-0-0-0-0.ulco01.bi.telstraglobal.net]

16      397 ms  399 ms  380 ms  202.84.178.10

17      405 ms  *       *       109.200.218.77  [20ge.cr0-fr0.smartdc.rtm.i3d.net]

18      399 ms  398 ms  402 ms  109.200.218.5   [20ge.cr1-fr0.smartdc.rtm.i3d.net]

19      416 ms  404 ms  491 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

20      513 ms  511 ms  498 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

21      516 ms  546 ms  549 ms  109.200.218.193 [10ge.laxr0-dfwr0.csla02.lax.i3d.net]

22      541 ms  Destination Reached in 550 ms. Port closed on 162.245.204.234

Trace Complete.

 

Tracert from TPG using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       2 ms    2 ms    2 ms    hidden

2       26 ms   26 ms   26 ms   hidden

3       27 ms   25 ms   26 ms   202.7.180.233   [202-7-180-233.static.tpgi.com.au]

4       27 ms   25 ms   26 ms   202.7.171.245   [bri-nxg-alf-crt2-POS-5-1.tpgi.com.au]

5       79 ms   79 ms   81 ms   203.26.22.105   [syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au]

6       85 ms   87 ms   82 ms   203.221.3.3     [203-221-3-3.tpgi.com.au]

7       236 ms  236 ms  235 ms  206.72.211.4    [as49544.any2-la.coresite.com]

8       Destination Reached in 228 ms. Port closed on 162.245.204.234

Trace Complete.

 

As you can see the results using the TCP protocol are the same as using ping (ICMP)

 

Your statement,

 “In the Telstra network pings and traceroutes are considered low priority traffic and may reflect increased response times as other traffic is prioritised.”

Is not valid.

 

You may need to get back to Telstra to find the source of that statement.

 

My original statement “Telstra introduced lag into the internet network” still seems to hold true.

 

I have provides evidence of my statement, in return no evidence has been presented that refutes my statement.

 

AS has been demonstrated you can get a valid result by the use of the ping and tracert commands on the Telstra network.

 

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Every time I post a reply to Kenobi, my post disappears,

what’s going on?

 

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Hi Kenobi,

 

Thanks for your response, nice try at an answer but it seems to be incorrect.

 

Yes it is true that ICMP can be routed via different paths and since tracert on windows uses ICMP this also applies to using tracert.

 

 It’s true Telstra can do whatever they like with protocol, drop it, send it the long way around etc.

But do they, I don’t thinks so.

 

So I decided to test it with the TCP protocol since that is what web browsers and emails use and I assume this protocol is high priority.

 

I used a trace that uses the TCP protocol.

 

Trace from Telstra using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       *       *       *       Request timed out.

2       *       *       *       Request timed out.

3       14 ms   12 ms   23 ms   58.160.252.2    [CPE-58-160-252-2.wa.bigpond.net.au]

4       14 ms   13 ms   10 ms   203.50.112.52   [bundle-ether4.pie-edge902.perth.telstra.net]

5       24 ms   11 ms   12 ms   203.50.6.188    [bundle-ether7.pie-core1.perth.telstra.net]

6       39 ms   41 ms   57 ms   203.50.11.16    [bundle-ether6.way-core4.adelaide.telstra.net]

7       55 ms   53 ms   55 ms   203.50.11.93    [bundle-ether9.exi-core10.melbourne.telstra.net]

8       87 ms   65 ms   66 ms   203.50.11.124   [bundle-ether12.chw-core10.sydney.telstra.net]

9       87 ms   66 ms   65 ms   203.50.6.93     [bundle-ether1.oxf-gw11.sydney.telstra.net]

10      69 ms   68 ms   68 ms   203.50.13.98    [bundle-ether1.sydo-core03.sydney.reach.com]

11      65 ms   68 ms   68 ms   202.84.222.66   [i-0-1-0-18.sydo-core04.bi.telstraglobal.net]

12      252 ms  246 ms  261 ms  202.84.136.33   [i-34.eqnx-core01.bx.telstraglobal.net]

13      347 ms  318 ms  354 ms  202.84.136.93   [i-0-4-0-10.ny8a-core01.bi.telstraglobal.net]

14      389 ms  443 ms  314 ms  202.84.137.69   [i-0-1-0-2.tnrt-core01.bi.telstraglobal.net]

15      384 ms  393 ms  382 ms  202.40.148.34   [i-0-0-0-0.ulco01.bi.telstraglobal.net]

16      397 ms  399 ms  380 ms  202.84.178.10

17      405 ms  *       *       109.200.218.77  [20ge.cr0-fr0.smartdc.rtm.i3d.net]

18      399 ms  398 ms  402 ms  109.200.218.5   [20ge.cr1-fr0.smartdc.rtm.i3d.net]

19      416 ms  404 ms  491 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

20      513 ms  511 ms  498 ms  109.200.218.150 [10ge.iadr0-lr0.csva01.iad.i3d.net]

21      516 ms  546 ms  549 ms  109.200.218.193 [10ge.laxr0-dfwr0.csla02.lax.i3d.net]

22      541 ms  Destination Reached in 550 ms. Port closed on 162.245.204.234

Trace Complete.

 

Continued on next post

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Continued from previous post

 

 

Tracert from TPG using TCP

 

tracetcp 162.245.204.234

 

Tracing route to 162.245.204.234 on port 80

Over a maximum of 30 hops.

1       2 ms    2 ms    2 ms    hidden

2       26 ms   26 ms   26 ms   hidden

3       27 ms   25 ms   26 ms   202.7.180.233   [202-7-180-233.static.tpgi.com.au]

4       27 ms   25 ms   26 ms   202.7.171.245   [bri-nxg-alf-crt2-POS-5-1.tpgi.com.au]

5       79 ms   79 ms   81 ms   203.26.22.105   [syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au]

6       85 ms   87 ms   82 ms   203.221.3.3     [203-221-3-3.tpgi.com.au]

7       236 ms  236 ms  235 ms  206.72.211.4    [as49544.any2-la.coresite.com]

8       Destination Reached in 228 ms. Port closed on 162.245.204.234

Trace Complete.

 

As you can see the results using the TCP protocol are the same as using ping (ICMP)

 

Your statement,

 “In the Telstra network pings and traceroutes are considered low priority traffic and may reflect increased response times as other traffic is prioritised.”

Is not valid.

 

You may need to get back to Telstra to find the source of that statement.

 

My original statement “Telstra introduced lag into the internet network” still seems to hold true.

 

I have provides evidence of my statement, in return no evidence has been presented that refutes my statement.

 

AS has been demonstrated you can get a valid result by the use of the ping and tracert commands on the Telstra network.

 

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Seems to be a limit on the message length

I have split the reply into 2 parts above

It would be nice if there was a message that said reply length exceeded or

a counter that showed the number of characters left to use.

Telstra (Retired)
Telstra (Retired)

Re: Telstra introduced lag into the internet network

Are you still experiencing this issue?

 

- Shelly

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Hi Shelly

 

Wow what a result see trace, Thanks

 

Tracert From Telstra

 

tracert 162.245.204.234

 

Tracing route to 162.245.204.234 over a maximum of 30 hops

 

  1    <1 ms    <1 ms    <1 ms  10.0.0.138

  2     *        *        *     Request timed out.

  3    14 ms    12 ms    11 ms  CPE-58-160-252-2.wa.bigpond.net.au [58.160.252.2]

  4    11 ms    11 ms    12 ms  bundle-ether4.pie-edge902.perth.telstra.net [203.50.112.52]

  5    11 ms    15 ms    14 ms  bundle-ether7.pie-core1.perth.telstra.net [203.50.6.188]

  6    38 ms    39 ms    39 ms  bundle-ether6.way-core4.adelaide.telstra.net [203.50.11.16]

  7    51 ms    52 ms    51 ms  bundle-ether9.exi-core10.melbourne.telstra.net [203.50.11.93]

  8    65 ms    69 ms    63 ms  bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124]

  9    89 ms    63 ms    67 ms  bundle-ether1.oxf-gw11.sydney.telstra.net [203.50.6.93]

 10    65 ms    67 ms    64 ms  bundle-ether1.sydo-core03.sydney.reach.com [203.50.13.98]

 11   214 ms   210 ms   210 ms  i-13.paix-core01.bx.telstraglobal.net [202.84.136.198]

 12   214 ms   211 ms   209 ms  i-0-4-0-3.paix02.bi.telstraglobal.net [202.84.251.106]

 13   210 ms   211 ms   210 ms  80.157.128.205

 14   219 ms   215 ms   218 ms  217.239.47.249

 15   226 ms   223 ms   224 ms  i3D-net.lax-sb2.LAX.US.NET.DTAG.DE [87.128.237.70]

 16   260 ms   263 ms   257 ms  162.245.204.234

 

Trace complete.

 

tracert From TPG

 

tracert 162.245.204.234

 

Tracing route to 162.245.204.234 over a maximum of 30 hops

 

  1    <1 ms    <1 ms    <1 ms  hidden

  2    25 ms    25 ms    25 ms  hidden

  3    25 ms    33 ms    26 ms  202-7-180-233.static.tpgi.com.au [202.7.180.233]

  4    25 ms    27 ms    25 ms  bri-nxg-alf-crt2-POS-5-1.tpgi.com.au [202.7.171.245]

  5    80 ms    78 ms    79 ms  syd-gls-har-crt1-tg-0-0-0-13.tpgi.com.au [203.26.22.105]

  6    79 ms    86 ms    87 ms  203-221-3-3.tpgi.com.au [203.221.3.3]

  7   230 ms   226 ms   225 ms  as49544.any2-la.coresite.com [206.72.211.4]

  8   227 ms   227 ms   227 ms  162.245.204.234

 

Trace complete.

 

That is a big improvement.

Still not a good as TPG

What was done?

Looks like the traffic was routed through a shorter path.

 

Telstra is supposed to be the best in the country and yet is outdone by TPG.

 

 

Qy
Level 3: Gumshoe

Re: Telstra introduced lag into the internet network

Hi  Technical Support

 

You might want to remove the statement

 

“It is also important to remember that any tests conducted from a traceroute or ping is considered low priority traffic and as such will reflect increased response times as other traffic is prioritised, or the ping packets dropped from the queuing traffic.”

 

From this link

 

http://crowdsupport.telstra.com.au/t5/General-Internet-KB/International-routing-latency-and-ping/ta-...

 

 as it has been proven to be incorrect.

 

 

Also moderators are using it as an excuse for dismissing customer’s complaints, that use ping and tracert commands to voice their concerns with high ping.

Telstra (Retired)
Telstra (Retired)

Re: Telstra introduced lag into the internet network

Thanks for that feedback, Qy. I have edited the KB article to advise that it may be handled as low priority traffic.  

 

Every hop between your device and the destination is still responding with potentially low priority traffic (ICMP) while the destination may respond with TCP ACK, providing it's listening on the correct port. If the destination does respond, it should give you an accurate trip time; although the destination server itself may be congested which means that you can never be entirely sure how much of the latency is due to the path taken or congestion on the destination server. 


Each server along the route may not respond via the same path, which is why the hops in between may have a higher latency than the destination result. 

 

If you read the entire article, it does go on to explain how the internet functions as a group of autonomous systems and that Telstra only controls the servers within our network. It is up to each server and the destination to determine the path back to the source of the trace route.  This is why, when you perform a trace route, you are only seeing half the picture.

 

- Shelly

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit
Find out more about the Telstra 24x7 App and direct debit ×
Manage your services and take advantage of offers while you’re out and about with the Telstra 24x7® App Find out more

Avoid queueing up and never worry about late fees againSet up direct debit

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

Register now