Menu
What's New
By:
Filters

Absurd ping times

I am not sure how to read this:

tracert rp.entropiauniverce.com

Tracing route to rp.entropiauniverce.com [204.13.160.25]
over a maximum of 30 hops:

1 7 ms 7 ms 7 ms 10.234.224.1
2 7 ms 7 ms * 68.86.112.97
3 7 ms 7 ms * 68.87.208.25
4 9 ms 8 ms * 68.87.208.34
5 8 ms * 8 ms 68.87.208.38
6 * * 8 ms 12.119.17.5
7 11 ms 8 ms 9 ms tbr1-p013901.la2ca.ip.att.net [12.123.222.90]
8 * 7 ms 8 ms 12.127.3.217
9 8 ms 9 ms 9 ms br1-a3110s9.attga.ip.att.net [192.205.33.230]
10 9 ms 9 ms 9 ms ae-12-51.car2.LosAngeles1.Level3.net [4.68.102.1
3]
11 8 ms 9 ms 10 ms 4.78.194.22
12 10 ms 17 ms 13 ms host204-13-160-25.oversee.net [204.13.160.25]

Trace complete.
 
Hi,
Recently, I've been having even worse ping times, around 800 ms when I used to have below 100 ms some months ago.
I downloaded the freeware app "ping plotter", and this is the result:

[br]Click to enlarge[/br]

After some investigation on the telia network setup, it seems that "ldn" stands for a router in London and "hbg" stands for another router in Hamburg, both part of the telia carrier backbone.

It really seems to me that everything is ok except the link between London and Hamburg, but I contacted telia support and they said that the fault is not on their side. To me, this trace indicates that the packets get to London from my PC in 75 ms, but the next hop is 700 ms away... Isn't it?

Any kind soul with expertise in analyzing routing info who can confirm if the fault is either in the telia part of in my ISP (telefonica) ???

Please, help. I'm desperate ! :)

/jdegre.
 
nice,

i downloaded the plotter and I am in the green - and I do not see no telia... at all

Target Name: rp.entropiauniverce.com
IP: 66.45.232.75
Date/Time: 10/26/2006 1:30:25 PM to 10/26/2006 1:31:10 PM

1 7 ms 10 ms 7 ms 9 ms 7 ms 7 ms 8 ms 7 ms 7 ms 8 ms [10.240.64.1]
2 7 ms 9 ms 10 ms 10 ms 10 ms 7 ms 9 ms 9 ms 7 ms 10 ms gig3-17.igwdca1-rtr1.socal.rr.com [76.166.2.190]
3 8 ms 11 ms 9 ms 9 ms 9 ms 28 ms 9 ms 11 ms 8 ms 8 ms tge9-3.sclaca2-rtr1.socal.rr.com [76.166.1.12]
4 10 ms 10 ms 8 ms 8 ms 8 ms 9 ms 9 ms 10 ms 9 ms 10 ms tge9-3.wxlaca1-rtr1.socal.rr.com [76.166.1.10]
5 10 ms 10 ms 9 ms 9 ms 9 ms 10 ms 10 ms 10 ms 9 ms 8 ms tge9-3.bwlaca1-rtr3.socal.rr.com [76.166.1.8]
6 9 ms 10 ms 11 ms 10 ms 11 ms 10 ms 10 ms 10 ms 9 ms 9 ms tge9-3.bwlaca1-rtr1.socal.rr.com [76.166.1.6]
7 * 10 ms 10 ms 13 ms 9 ms 9 ms 9 ms 10 ms 12 ms 14 ms tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]
8 9 ms 12 ms 9 ms 9 ms 10 ms 10 ms 9 ms 8 ms 11 ms 9 ms [12.127.137.21]
9 20 ms 21 ms 21 ms 21 ms 23 ms 20 ms 218 ms 127 ms 23 ms 22 ms gbr5-p90.la2ca.ip.att.net [12.123.199.210]
10 20 ms 20 ms 21 ms 21 ms 22 ms 20 ms 23 ms 23 ms 23 ms 22 ms tbr1-p013501.la2ca.ip.att.net [12.122.11.137]
11 24 ms 23 ms 24 ms 23 ms 24 ms 23 ms 23 ms 24 ms 24 ms 28 ms tbr1-cl3.sffca.ip.att.net [12.122.10.25]
12 20 ms 20 ms 21 ms 21 ms 22 ms 21 ms 21 ms 20 ms 20 ms 21 ms [12.123.12.1]
13 24 ms 26 ms 23 ms 24 ms 29 ms 23 ms 25 ms 23 ms 28 ms 24 ms so-6-1-0.mpr2.sjc7.us.above.net [64.125.13.49]
14 25 ms 25 ms 23 ms 36 ms 34 ms 29 ms 25 ms 24 ms 31 ms 23 ms so-5-0-0.mpr3.sjc2.us.above.net [64.125.30.174]
15 * 78 ms 78 ms 77 ms 76 ms 77 ms 78 ms 78 ms 77 ms 76 ms so-5-1-0.cr1.ord2.us.above.net [64.125.30.210]
16 80 ms 78 ms 76 ms 80 ms 77 ms 76 ms 77 ms 76 ms 77 ms 76 ms so-0-0-0.cr2.ord2.us.above.net [64.125.29.186]
17 96 ms 89 ms 88 ms 86 ms 93 ms 87 ms 87 ms 95 ms 89 ms N/A so-1-1-0.mpr4.lga1.us.above.net [64.125.27.34]
18 87 ms 90 ms 89 ms 88 ms 87 ms 87 ms 88 ms 88 ms 88 ms N/A so-1-0-0.cr2.lga1.us.above.net [64.125.27.242]
19 88 ms 89 ms 89 ms 87 ms 88 ms 92 ms 90 ms 89 ms 234 ms N/A so-1-0-0.mpr1.lga1.us.above.net [64.125.27.150]
20 94 ms 92 ms 92 ms 92 ms 100 ms 91 ms 93 ms 90 ms 276 ms N/A 64.124.44.213.interserver.com [64.124.44.213]
21 92 ms 92 ms 92 ms 93 ms 91 ms 90 ms 94 ms 93 ms 92 ms N/A core-01-teb.njiix.net [64.20.32.174]
22 93 ms 94 ms 92 ms 92 ms 95 ms 92 ms 91 ms 92 ms 91 ms N/A edge-04-teb.njiix.net [64.20.32.37]
23 91 ms 93 ms 91 ms 91 ms 92 ms 91 ms 92 ms 92 ms 91 ms N/A [66.45.232.75]

Ping statistics for rp.entropiauniverce.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 91ms, Maximum = 93ms, Average = 91ms
Click to expand...
 
fresco said:
nice,

i downloaded the plotter and I am in the green - and I do not see no telia... at all
Click to expand...

Try sending the pings to rp.entropiauniverse.com, instead of rp.entropiauniverce.com :)

Amazing that the other domain exists too, I wonder where does it point to....

/jdegre.
 
Belgian Re.trace :

Code: 
Tracing route to 217.212.240.131 [217.212.240.131]   (217-212-240-131.customer.teliacarrier.com  |  .COM | US Commercial)
Hop 1  Time : 3     
Hop 2  Time : 26    
Hop 3  Time : 29      
Hop 4  Time : 28      
Hop 5  Time : 27      
Hop 6  Time : 31     
Hop 7  Time : 37      
Hop 8  Time : 54      (s-bb1-link.telia.net  |  .NET | Network)
Hop 9  Time : 53      (s-b4-pos12-0.telia.net  |  .NET | Network)
Hop 10 Time : 55      (s-hdn-i4-link.telia.net  |  .NET | Network)
Hop 11 Time : 51      (217-212-240-131.customer.teliacarrier.com  |  .COM | US Commercial)
 
jdegre said:
Try sending the pings to rp.entropiauniverse.com, instead of rp.entropiauniverce.com :)

Amazing that the other domain exists too, I wonder where does it point to....

/jdegre.
Click to expand...

LOL!

here then:

Target Name: rp.entropiauniverse.com
IP: 217.212.240.132
Date/Time: 10/26/2006 3:27:28 PM to 10/26/2006 3:28:13 PM

1 7 ms 8 ms 8 ms 7 ms 8 ms 8 ms 18 ms 7 ms 8 ms 7 ms [10.240.64.1]
2 8 ms 8 ms 7 ms 7 ms 9 ms 8 ms 9 ms 7 ms 8 ms 8 ms gig1-17.igwdca1-rtr1.socal.rr.com [76.166.2.188]
3 8 ms 9 ms 8 ms 7 ms 9 ms 18 ms 8 ms 8 ms 7 ms 8 ms tge9-3.sclaca2-rtr1.socal.rr.com [76.166.1.12]
4 8 ms 9 ms 8 ms 8 ms 8 ms 9 ms 8 ms 11 ms 8 ms 10 ms tge9-3.wxlaca1-rtr1.socal.rr.com [76.166.1.10]
5 10 ms 8 ms 9 ms 8 ms 8 ms 9 ms 8 ms 10 ms 15 ms 10 ms tge9-3.bwlaca1-rtr3.socal.rr.com [76.166.1.8]
6 10 ms 9 ms 8 ms 9 ms 10 ms 8 ms 10 ms 8 ms 10 ms 10 ms tge9-3.bwlaca1-rtr1.socal.rr.com [76.166.1.6]
7 8 ms 9 ms 8 ms 9 ms 9 ms 227 ms 9 ms 8 ms 9 ms 8 ms tge9-2.bwlaca1-rtr1.socal.rr.com [76.166.1.4]
8 8 ms 9 ms 9 ms 8 ms 8 ms 9 ms 9 ms 8 ms 8 ms 11 ms [12.127.137.21]
9 8 ms 8 ms 9 ms 10 ms 10 ms 10 ms 10 ms 10 ms 11 ms 10 ms gbr5-p90.la2ca.ip.att.net [12.123.199.210]
10 9 ms 10 ms 10 ms 8 ms 10 ms 11 ms 9 ms 10 ms 10 ms 10 ms tbr2-p013501.la2ca.ip.att.net [12.122.11.153]
11 10 ms 9 ms 8 ms 9 ms 8 ms 11 ms 10 ms 11 ms 19 ms 19 ms ggr2-p3140.la2ca.ip.att.net [12.123.222.37]
12 8 ms 9 ms 9 ms 8 ms 9 ms 10 ms 9 ms 9 ms 9 ms 10 ms [192.205.33.6]
13 45 ms 45 ms * * 45 ms 44 ms 54 ms 46 ms 49 ms 46 ms dsl-bb1-pos7-0-0.telia.net [213.248.80.14]
14 82 ms 84 ms 84 ms 83 ms 83 ms 83 ms 83 ms 83 ms 86 ms 84 ms nyk-bb2-link.telia.net [213.248.80.10]
15 171 ms 169 ms 169 ms 170 ms 193 ms 170 ms 169 ms 170 ms 169 ms 171 ms kbn-bb2-link.telia.net [213.248.82.102]
16 177 ms 179 ms 177 ms 179 ms 178 ms 179 ms 182 ms 179 ms 178 ms 178 ms s-bb2-link.telia.net [213.248.65.165]
17 183 ms 183 ms 184 ms 326 ms 184 ms 184 ms 183 ms 184 ms 184 ms 184 ms s-b4-pos5-0.telia.net [213.248.66.14]
18 175 ms 339 ms 175 ms 177 ms 176 ms 176 ms 177 ms 177 ms 175 ms 176 ms s-hdn-i4-link.telia.net [80.91.249.209]
19 185 ms 182 ms 180 ms 185 ms 180 ms 184 ms 191 ms 182 ms 183 ms 182 ms 217-212-240-132.customer.teliacarrier.com [217.212.240.132]

Ping statistics for rp.entropiauniverse.com
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 180ms, Maximum = 191ms, Average = 183ms
 
On an average day from here:

Code: 
Tracing route to 217-212-240-131.customer.teliacarrier.com [217.212.240.131]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  router.starbase.se [192.168.1.1]
  2     1 ms     1 ms    <1 ms  10.65.8.1
  3    34 ms     3 ms     1 ms  172.30.0.53
  4    23 ms    20 ms     1 ms  82.209.168.22
  5     1 ms     1 ms     1 ms  kg15-0-l-2-5-mkb.mlm.bredband2.net [82.209.170.69]
  6     3 ms     3 ms     3 ms  gi3-14.ar3.CPH1.gblx.net [64.210.19.41]
  7    16 ms    18 ms    18 ms  ffm-b3-geth0-2-1.telia.net [213.248.77.181]
  8    17 ms    18 ms    19 ms  ffm-bb2-link.telia.net [80.91.249.142]
  9    25 ms    26 ms    26 ms  hbg-bb2-pos6-1-0.telia.net [213.248.65.122]
 10    28 ms    27 ms    29 ms  s-bb2-pos7-3-0.telia.net [213.248.64.37]
 11    27 ms    27 ms    27 ms  s-b4-pos5-0.telia.net [213.248.66.14]
 12    27 ms     *       30 ms  s-hdn-i4-link.telia.net [80.91.249.209]
 13    31 ms    30 ms    30 ms  217-212-240-131.customer.teliacarrier.com [217.212.240.131]

Trace complete.

If I turn of my hosting servers and and teamspeak server and so, I'll have 10-20ms less.
 
Also in Spain (telefonica)

Oh look, exactly the same node bottleneck :(


tracert 217.212.240.131 said:
Tracing route to 217-212-240-131.customer.teliacarrier.com [217.212.240.131]

over a maximum of 30 hops:



1 <1 ms <1 ms <1 ms 192.168.1.1

2 51 ms 52 ms 51 ms 192.168.153.1

3 52 ms 51 ms 50 ms 226.Red-80-58-116.staticIP.rima-tde.net [80.58.116.226]

4 63 ms 63 ms 63 ms 141.Red-80-58-81.staticIP.rima-tde.net [80.58.81.141]

5 * * * Request timed out.

6 85 ms 84 ms 84 ms So1-2-0-0-grtparix3.red.telefonica-wholesale.net [213.140.43.186]

7 92 ms 91 ms 92 ms GE2-1-0-0-grtparix1.red.telefonica-wholesale.net [213.140.36.157]

8 86 ms 88 ms 87 ms Telia-3-1-3-0-grtparix1.red.telefonica-wholesale.net [213.140.53.74]

9 80 ms 80 ms 79 ms prs-bb2-pos0-2-0.telia.net [213.248.65.81]

10 301 ms 303 ms 298 ms ffm-bb2-pos6-0-0.telia.net [213.248.65.118]

11 308 ms 311 ms 310 ms hbg-bb2-pos6-1-0.telia.net [213.248.65.122]

12 323 ms 320 ms 318 ms s-bb2-pos7-3-0.telia.net [213.248.64.37]

13 201 ms 199 ms 200 ms s-b4-pos5-0.telia.net [213.248.66.14]

14 203 ms 202 ms 201 ms s-hdn-i4-link.telia.net [80.91.249.209]

15 205 ms 205 ms 206 ms 217-212-240-131.customer.teliacarrier.com [217.212.240.131]



Trace complete.
Click to expand...
 
Dem said:
Also in Spain (telefonica)

Oh look, exactly the same node bottleneck :(
Click to expand...

Yeah, it looks like the same type of bottleneck but with different routers. In your case, the bad link seems to be from "prs" (Paris) to "ffm" (Frankfurt). Also, at the time of your test (around 11pm), it is not so bad as when I did my test (around 8pm, peak hour for internet use), but still >300ms, which is really bad if you're hunting.

Anyway, Telia blames Telefonica for this fault, but I really don't see why. Looks like we're stalled here with no solution.

/jdegre.
 
I fail to see how Telia can blame Telefonica?

It's plainly obvious the bottleneck is in the Telia network!
 
From Home (Sweden ComHem Cable)

PING rp.entropiauniverse.com (217.212.240.131) 56(84) bytes of data.
64 bytes from 217-212-240-131.customer.teliacarrier.com (217.212.240.131): icmp_seq=1 ttl=116 time=27.0 ms
64 bytes from 217-212-240-131.customer.teliacarrier.com (217.212.240.131): icmp_seq=2 ttl=116 time=25.5 ms
64 bytes from 217-212-240-131.customer.teliacarrier.com (217.212.240.131): icmp_seq=3 ttl=116 time=49.0 ms
64 bytes from 217-212-240-131.customer.teliacarrier.com (217.212.240.131): icmp_seq=4 ttl=116 time=25.0 ms
64 bytes from 217-212-240-131.customer.teliacarrier.com (217.212.240.131): icmp_seq=5 ttl=116 time=27.2 ms

--- rp.entropiauniverse.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4012ms
rtt min/avg/max/mdev = 25.093/30.792/49.036/9.160 ms

1: gateway.damage.inc.local (192.168.133.201) 0.610ms
2: hbg-doc-1-cable7-0-0.comhem.se (83.249.128.1) asymm 3 17.240ms
3: 83.255.240.201 (83.255.240.201) 19.378ms
4: hlm-bb-r-01-to-hs-bb-r-01.comhem.se (83.255.252.168) 16.448ms
5: ld-bb-r-01-to-hlm-bb-r-01.comhem.se (83.255.252.164) 19.295ms
6: lib-bb-r-01-to-ld-bb-r-01.comhem.se (83.255.252.160) 33.029ms
7: lib-pr-r-01-to-lib-bb-r-01.comhem.se (83.255.252.226) 23.447ms
8: kbn-b1-lunk.telia.net (213.248.97.253) 16.868ms
9: kbn-bb1-pos1-0-0.telia.net (213.248.65.9) asymm 10 15.719ms
10: s-bb1-pos7-0-0.telia.net (213.248.65.26) asymm 11 34.621ms
11: s-b4-pos12-0.telia.net (213.248.66.6) 29.054ms
12: s-hdn-i4-link.telia.net (80.91.249.209) 37.654ms
13: no reply

Odd thing is that Hop 13 is rp.entropiauniverse.com but doesnt respond...


From work (Telia ADSL)

Tracing route to rp.entropiauniverse.com [217.212.240.133]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Gw2.ldlab.net [192.168.200.2]
2 <1 ms <1 ms <1 ms 192.168.211.17
3 5 ms 5 ms 5 ms h1n1fls34o985.telia.com [213.65.19.1]
4 6 ms 5 ms 5 ms 213.65.16.237
5 6 ms 6 ms 5 ms m-b-c1-link.se.telia.net [81.228.72.136]
6 6 ms 6 ms 6 ms ld-h-peer1-link.se.telia.net [81.228.73.197]
7 7 ms 7 ms 6 ms kbn-b2-pos14-0.telia.net [213.248.78.126]
8 7 ms 7 ms 9 ms kbn-bb2-pos1-3-0.telia.net [213.248.64.57]
9 15 ms 15 ms 15 ms s-bb1-link.telia.net [213.248.65.141]
10 18 ms 19 ms 18 ms s-b4-pos12-0.telia.net [213.248.66.6]
11 15 ms 15 ms 16 ms s-hdn-i4-link.telia.net [80.91.249.209]
12 21 ms 19 ms 19 ms 217-212-240-133.customer.teliacarrier.com [217.212.240.133]

Here rp.entropiauniverse.com does respond...
 
Contact Telia

Send your ping and tracert data to telia themselfs

they are normally quite interested to pick up issues that may be happening - and dont mind non telia customers contact them.

telia are one of the main backbones around ;) also tracert can sometimes be usless as the rout's can change

try sending 1mb pings and for a couple of mins and look at the response times then ;P

Also try adding some additional dns servers in to your network setup and it may find a different route ;)

also any network is only as fast as the network connection the other end ;)

sweden do have 100 mb broadband though ;)

download sandra and this will give you well detailed analysis of netowkr connectivity and you con monitor it then as well ;P


http://www.sisoftware.co.uk/
 
Last edited:
You must log in or register to reply here.
Back
Top