Absurd ping times

jdegre

Elite
Joined
Dec 24, 2005
Posts
2,961
Location
Madrid, Spain
Society
Survival Program
Avatar Name
Jesus jdegre de Gregorio
I'm having ping times to the EU servers in the order of 600-700 ms. Needless to say, I cannot play with this kind of latency (I only hunt and I miss more shots than I hit).
This has started happening this week, and it does not seem to be a very general problem since other people I talk to, don't seem to have this problem.
I can ping other servers worldwide with no problems (< 100 ms).

This is the traceroute log from my PC to EU server:
Code:
  1    <1 ms    <1 ms    <1 ms  . [192.168.0.1]
  2    49 ms    44 ms    43 ms  192.168.153.1
  3    43 ms    43 ms    43 ms  114.Red-81-46-70.staticIP.rima-tde.net [81.46.70.114]
  4     *       44 ms    45 ms  141.Red-80-58-81.staticIP.rima-tde.net [80.58.81.141]
  5     *       43 ms    43 ms  So7-0-0-0-grtmadde2.red.telefonica.wholesale.net [84.16.8.113]
  6    71 ms    72 ms    71 ms  So1-2-0-0-grtparix3.red.telefonica-wholesale.net [213.140.43.186]
  7    63 ms    71 ms    61 ms  GE1-1-0-0-grtparix1.red.telefonica-wholesale.net [213.140.43.33]
  8    71 ms    73 ms    70 ms  Telia-3-1-3-0-grtparix1.red.telefonica-wholesale.net [213.140.53.74]
  9    64 ms    65 ms    63 ms  prs-bb2-pos0-2-0.telia.net [213.248.65.81]
 10   698 ms   698 ms   704 ms  ffm-bb2-pos6-0-0.telia.net [213.248.65.118]
 11   345 ms   345 ms   352 ms  hbg-bb2-pos6-1-0.telia.net [213.248.65.122]
 12   734 ms   728 ms   735 ms  s-bb2-pos7-3-0.telia.net [213.248.64.37]
 13   730 ms   737 ms   738 ms  s-b4-pos5-0.telia.net [213.248.66.14]
 14   730 ms   736 ms   733 ms  s-hdn-i4-link.telia.net [80.91.249.209]
 15   729 ms   723 ms   713 ms  rp.entropiauniverse.com [217.212.240.131]

It seems that problems start when packets go through the telia routers, before even reaching the EU servers.
Am I the only one experiencing this??? Any hint would be really appreciated.

Cheers,
/jdegre.
 
I just pinged from UK and got 43ms ave

Traceroute report:

Code:
===================================================================================
=== VisualRoute (R) 2006 Server Edition (v10.0j) report on 04-Oct-2006 18:43:51 ===
===================================================================================

Report for rp.entropiauniverse.com [217.212.240.133]

Analysis: 'rp.entropiauniverse.com' [217-212-240-133.customer.teliacarrier.com]  was found in 9 hops 
(TTL=120). 

------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| Hop | %Loss | IP Address      | Node Name                              | Location         | Tzone  | ms | Graph      | Network                                       |
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0   |       | 205.177.182.160 | visualroute.visualware.co.uk           | *                |        |    |            | Defender Technologies Group, LLC DTGL-BNA42-6 |
| 1   |       | 205.177.182.1   | ge0-23.uk.telecity.defenderhosting.com | London, UK       | *      | 0  | x          | Defender Technologies Group, LLC DTGL-BNA42-6 |
| 2   | 20    | 213.248.74.45   | ldn-tci-col2-link.telia.net            | London, UK       | *      | 0  | x          | Telia International Carrier                   |
| 3   |       | 213.248.100.221 | ldn-b2-geth4-0.telia.net               | London, UK       | *      | 0  | x          | Telia International Carrier                   |
| 4   |       | 80.91.249.186   | ldn-bb1-link.telia.net                 | London, UK       | *      | 3  | x-         | Telia International Carrier                   |
| 5   |       | 80.91.249.11    | hbg-bb1-link.telia.net                 | Hamburg, Germany | +01:00 | 15 | x-         | Telia International Carrier                   |
| 6   |       | 80.91.249.221   | s-bb1-link.telia.net                   | ...              |        | 28 |  x         | Telia International Carrier                   |
| 7   |       | 213.248.66.6    | s-b4-pos12-0.telia.net                 | ...              |        | 37 |  x----     | Telia International Carrier                   |
| 8   |       | 80.91.249.209   | s-hdn-i4-link.telia.net                | ...              |        | 88 |  --x------ | Telia International Carrier                   |
| 9   |       | 217.212.240.133 | rp.entropiauniverse.com                | ?(Sweden)        | +01:00 | 26 |  x         | Mindark AB                                    |
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
 
Blake Seven said:
I just pinged from UK and got 43ms ave

I can only dream on that. Best I've ever got is around 100 ms, when things work perfect.

The problem I'm having right now looks like a connectivity problem between the carrier (telia) and my ISP (telefonica). I was trying to find out if any other people is having similar problems, but I know that the problem is not general (fortunately)....

/jdegre.
 
Routenverfolgung zu rp.entropiauniverse.com [217.212.240.134] üb
bschnitte:

1 20 ms 19 ms 19 ms lo-1-gigabit0.core.bi.bicos.net [

2 83 ms 231 ms 263 ms bb-gw.bicos.net [212.100.32.85]
3 36 ms 35 ms 19 ms FastEthernet3-0-0.GW1.BFE2.ALTER.
.157]
4 30 ms 37 ms 21 ms 324.ATM0-0.CR3.BFE2.ALTER.NET [14
5 20 ms 39 ms 21 ms 141.at-1-0-0.CR1.DTM1.ALTER.NET [

6 52 ms 39 ms 39 ms so-7-0-0.XR1.FFT4.ALTER.NET [149.
7 31 ms 38 ms 19 ms so-0-1-0.TR2.FFT1.ALTER.NET [146.
8 20 ms 39 ms 39 ms POS2-0.BR2.FFT1.ALTER.NET [146.18
9 47 ms 31 ms 38 ms ffm-b1-pos11-1.telia.net [146.188
10 71 ms 25 ms 43 ms ffm-bb1-pos1-1-0.telia.net [213.2
11 34 ms 39 ms 61 ms hbg-bb1-pos6-1-0.telia.net [213.2
 
Mine from singapore...

Pinging rp.entropiauniverse.com [217.212.240.133] with 32 bytes of data:

Reply from 217.212.240.133: bytes=32 time=442ms TTL=118
Reply from 217.212.240.133: bytes=32 time=435ms TTL=118
Reply from 217.212.240.133: bytes=32 time=441ms TTL=118
Reply from 217.212.240.133: bytes=32 time=439ms TTL=118

Ping statistics for 217.212.240.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 435ms, Maximum = 442ms, Average = 439ms
 
9 64 ms 65 ms 63 ms prs-bb2-pos0-2-0.telia.net [213.248.65.81]
10 698 ms 698 ms 704 ms ffm-bb2-pos6-0-0.telia.net [213.248.65.118]

Possibly over saturation on that link... Is that a constant response time for you, or one taken during a bad lag spell in the middle of UK peak usage times ?
 
Hm, I dont know if this is your case, but a 650 - 700 ms delay is typical for some sort of satellite relay i have seen long ago (10 years). Maybe they have a backup route trough a comm satellite. Of course, this will be odd, but it is my wild guess.
 
Saehk said:
Possibly over saturation on that link... Is that a constant response time for you, or one taken during a bad lag spell in the middle of UK peak usage times ?


Yes, I think that you're right and it might be an overloaded link. Ping times get lower noticeably at around 1-2am MA time, i.e., when most europeans are sleeping.

It seems that there is not much I (or MA) can do... :( this is really annoying, since it is impossible for me to play with 700 ms ping times.

What I'm wondering is if there is no other people having this problem... hmmm.... strange.

Rony: your idea seems very logical too. Maybe the traffic is only routed that way when certain throughput is exceeded in the main link... go figure...

/jdegre.
 
call your isp and they should be able to fix it.. if they cant get a new isp and yep it's as simple as that.. if an isp cant fix latency then it's time to choose a new one.

btw get winmtr to do your tracerts.. it's free and works great :D
 
Last edited:
From the Southeastern USA:


Diagnostic Result
PING 217.212.240.131 (217.212.240.131): 56 data bytes
64 bytes from 217.212.240.131: icmp_seq=0 ttl=112 time=140.0 ms
64 bytes from 217.212.240.131: icmp_seq=1 ttl=112 time=130.0 ms
64 bytes from 217.212.240.131: icmp_seq=2 ttl=112 time=140.0 ms
64 bytes from 217.212.240.131: icmp_seq=3 ttl=112 time=200.0 ms
64 bytes from 217.212.240.131: icmp_seq=4 ttl=112 time=140.0 ms

--- 217.212.240.131 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 130.0/150.0/200.0 ms
 
Code:
Pinging rp.entropiauniverse.com [217.212.240.131] with 32 bytes of data:
  
  Reply from 217.212.240.131: bytes=32 time=60ms TTL=115
  Reply from 217.212.240.131: bytes=32 time=64ms TTL=115
  Reply from 217.212.240.131: bytes=32 time=59ms TTL=115
  Reply from 217.212.240.131: bytes=32 time=64ms TTL=115
  
  Ping statistics for 217.212.240.131:
  	Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
  Approximate round trip times in milli-seconds:
  	Minimum = 59ms, Maximum = 64ms, Average = 61ms


Italy,Rome - ISP Fastweb

Seems ok to me :)
 
7ms :D messege to short...
 
Poland

From Uni server 10 Mb/s

PING 217.212.240.131 (217.212.240.131) 56(84) bytes of data.
64 bytes from 217.212.240.131: icmp_seq=1 ttl=120 time=34.7 ms
64 bytes from 217.212.240.131: icmp_seq=2 ttl=120 time=36.0 ms
64 bytes from 217.212.240.131: icmp_seq=3 ttl=120 time=35.5 ms
64 bytes from 217.212.240.131: icmp_seq=4 ttl=120 time=34.3 ms
64 bytes from 217.212.240.131: icmp_seq=5 ttl=120 time=34.2 ms
64 bytes from 217.212.240.131: icmp_seq=6 ttl=120 time=38.9 ms
64 bytes from 217.212.240.131: icmp_seq=7 ttl=120 time=39.0 ms
64 bytes from 217.212.240.131: icmp_seq=8 ttl=120 time=34.6 ms
64 bytes from 217.212.240.131: icmp_seq=9 ttl=120 time=34.9 ms

--- 217.212.240.131 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8077ms
rtt min/avg/max/mdev = 34.235/35.833/39.000/1.753 ms

From Home 2Mb/s

Odpowiedz z 217.212.240.131: bajtow=32 czas=114ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=98ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=106ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=102ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=100ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=102ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=99ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=97ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=101ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=99ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=103ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=102ms TTL=119
Odpowiedz z 217.212.240.131: bajtow=32 czas=95ms TTL=119


Cheers!
 
Legion said:
if an isp cant fix latency then it's time to choose a new one.
I doubt an isp wil order another big isp (like telia) to change a bgp only because a support case. Fastest solution is to change isp.
 
Rony said:
I doubt an isp wil order another big isp (like telia) to change a bgp only because a support case. Fastest solution is to change isp.

they will as all isp's kinda work together to beable to reach places via routers.. i had crap connections to wow for a while, called up my isp and supplied them with the tracert log and voila 2 days later problem fixed. It's just for them to pic up the phone and get it done.
 
FRANCE

Pinging rp.entropiauniverse.com with 32 bytes of data:
Reply from 217.212.240.134 bytes:32 Time:84ms TTL:119
Reply from 217.212.240.134 bytes:32 Time:79ms TTL:119
Reply from 217.212.240.134 bytes:32 Time:84ms TTL:119
Reply from 217.212.240.134 bytes:32 Time:83ms TTL:119
Reply from 217.212.240.134 bytes:32 Time:85ms TTL:119
Reply from 217.212.240.134 bytes:32 Time:79ms TTL:119
Ping statistics for rp.entropiauniverse.com :
Packets: Sent = 6, Received = 6, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 85ms, Average = 82ms
 
Netherlands:

Pingen naar rp.entropiauniverse.com [217.212.240.131] met 32 byte gegevens:

Antwoord van 217.212.240.131: bytes=32 tijd=74 ms TTL=112
Antwoord van 217.212.240.131: bytes=32 tijd=52 ms TTL=112
Antwoord van 217.212.240.131: bytes=32 tijd=52 ms TTL=112
Antwoord van 217.212.240.131: bytes=32 tijd=47 ms TTL=112
 
[br]Click to enlarge[/br]


This is the only way to realy show whats going on. I have similar problems but not near as high. Seems telia.net is overloaded and there is nothing you can do about it from the clientside. MA needs to talk to telia and ask why its so. Look at the first telia.net to the next telia.net the time increase is large, at times I have seen it actually douple its ping time. Also if I let pingplotter run pinging every second I see constant route changes back and forward.


Von
 
Dreicc said:
Another one :

Pinging rp.entropiauniverse.com [217.212.240.132] with 32 bytes of data:

Reply from 217.212.240.132: bytes=32 time=41ms TTL=113
Reply from 217.212.240.132: bytes=32 time=41ms TTL=113
Reply from 217.212.240.132: bytes=32 time=45ms TTL=113
Reply from 217.212.240.132: bytes=32 time=41ms TTL=113

Ping statistics for 217.212.240.132:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 41ms, Maximum = 45ms, Average = 42ms
 
On a ping route like yours....the issue isnt MA, you or your particular provider.

It starts at the 10th hop.....that router is bottlenecking, or misconfigured. Could also indictate some fiber issues as well, or interference somehow between 9-10. Look to be the same range of IP's so that provider should be contacted.

Can nslookup the ip to get the name or lookup the ip on the subnet database on the web...sry forgot link. (most subnet ranges...the 1st 3, some cases 1st 2 number sets, are owned as a whole by providers, but thier info is easy to get)

Once you get the company's name, which should be real easy, you can look them up and let them know.

lol ok nm here it is....looks like a range comcast leases from amsterdam: Regards 213.248.45.62

Nslookup shows: 68.87.69.146

OrgName: Comcast Cable Communications, Inc.
OrgID: CMCS
Address: 1800 Bishops Gate Blvd
City: Mt Laurel
StateProv: NJ
PostalCode: 08054
Country: US

NetRange: 68.80.0.0 - 68.87.255.255
CIDR: 68.80.0.0/13
NetName: JUMPSTART-2
NetHandle: NET-68-80-0-0-1
Parent: NET-68-0-0-0-0
NetType: Direct Allocation
NameServer: DNS.INFLOW.PA.BO.COMCAST.NET
NameServer: DNS.CMC.CO.DENVER.COMCAST.NET
Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE
RegDate: 2002-01-28
Updated: 2006-01-26

RTechHandle: IC161-ARIN
RTechName: Comcast Cable Communications Inc
RTechPhone: +1-856-317-7200
RTechEmail: CNIPEO-Ip-registration@cable.comcast.com

OrgAbuseHandle: NAPO-ARIN
OrgAbuseName: Network Abuse and Policy Observance
OrgAbusePhone: +1-856-317-7272
OrgAbuseEmail: abuse@comcast.net

OrgTechHandle: IC161-ARIN
OrgTechName: Comcast Cable Communications Inc
OrgTechPhone: +1-856-317-7200
OrgTechEmail: CNIPEO-Ip-registration@cable.comcast.com


Actual ip is:
OrgName: RIPE Network Coordination Centre
OrgID: RIPE
Address: P.O. Box 10096
City: Amsterdam
StateProv:
PostalCode: 1001EB
Country: NL

ReferralServer: whois://whois.ripe.net:43

NetRange: 213.0.0.0 - 213.255.255.255
CIDR: 213.0.0.0/8
NetName: RIPE-213
NetHandle: NET-213-0-0-0-1
Parent:
NetType: Allocated to RIPE NCC
NameServer: NS-PRI.RIPE.NET
NameServer: NS3.NIC.FR
NameServer: SUNIC.SUNET.SE
NameServer: NS-EXT.ISC.ORG
NameServer: SEC1.APNIC.NET
NameServer: SEC3.APNIC.NET
NameServer: TINNIE.ARIN.NET
Comment: These addresses have been further assigned to users in
Comment: the RIPE NCC region. Contact information can be found in
Comment: the RIPE database at http://www.ripe.net/whois
RegDate:
Updated: 2005-07-27

http://www.ripe.net/


Actually more specifically ill bet its an inflow error. Inflow is a company that provides transport and bandwidth to companies...know cause I had an interview with them a few years back in denver. Either way comcast is the company to get the service call to.

Wonder why you are goin thru comcast from spain? ;)
Even more interesting why is telia the swedish telecom using comcast. lol
 
Last edited:
My current pings (and, yes, the IP I used is the correct that I was connecting with)




Here's a little fun for everyone though .. the line of traffic between 0 and 10 is what EU uses for bandwidth ...

 
SeamusO said:
My current pings (and, yes, the IP I used is the correct that I was connecting with)




Here's a little fun for everyone though .. the line of traffic between 0 and 10 is what EU uses for bandwidth ...


as for the traffic, go up to cnd and i think it would increase due to the streaming audio :p
 
Thanks to you all for your posts.
I've filed a support case and MA seems to put the blame on Telia. Apparently their link with Telefonica Spain is either overloaded or not working properly. They said that they would contact Telia and try to gather some more info, if possible. Nice from them!.

In any case, I've contacted Telia as well, at the contact address registered at RIPE.NET; I don't know if this address (backbone@telia.net) is actually working or if there is actually somebody behind it, but if I receive a reply, I'll keep you updated.

Thanks again,
/jdegre.
 
TDC Denmark

Pinging rp.entropiauniverse.com [217.212.240.131] with 32 bytes of data:

Reply from 217.212.240.131: bytes=32 time=25ms TTL=115
Reply from 217.212.240.131: bytes=32 time=25ms TTL=115
Reply from 217.212.240.131: bytes=32 time=25ms TTL=115
Reply from 217.212.240.131: bytes=32 time=25ms TTL=115
 
Unique said:
7ms :D messege to short...


lol mallo u must be able to see the MA servers out of your window with that ping time ;)


i'm about 50-53ms from the UK
 
Tracing route to rp.entropiauniverse.com [217.212.240.133]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms ua-213-112-171-3.cust.bredbandsbolaget.se [213.112.171.3]
2 86 ms 2 ms 3 ms port-channel15.cr2.sto3.se.bredband.com [195.54.114.53]
3 1 ms 1 ms 1 ms ge3-0.cr1.sto1.se.bredband.com [195.54.114.245]
4 77 ms 2 ms 1 ms pos3-0.cr2.sto2.se.bredband.com [195.54.123.106]
5 1 ms 1 ms 1 ms pos3-0.br1.sto2.se.bredband.com[195.54.116.198]
6 1 ms 2 ms 1 ms s-b3-pos6-1.telia.net [213.248.101.49]
7 2 ms 2 ms 2 ms s-hdn-i3-link.telia.net [80.91.249.69]
8 2 ms 3 ms 2 ms s-hdn-i2-link.telia.net [80.91.249.74]
9 2 ms 2 ms 2 ms 217-212-240-133.customer.teliacarrier.com [217.212.240.133]

Trace complete.

Reply from 217.212.240.133: bytes=32 time=2ms TTL=120
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120

Ping statistics for 217.212.240.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

i cant complain :D
 
sob said:
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120
Reply from 217.212.240.133: bytes=32 time=2ms TTL=120

Ping statistics for 217.212.240.133:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 2ms, Average = 2ms

i cant complain :D

Damn i am jealous.

My UMTS connection (wireless broadband phone connection) from the Netherlands. I live in hotels during the week and play on the UMTS connection in the evenings.
Will post my ADSL one tomorow evening when i am back home.

Pinging rp.entropiauniverse.com [217.212.240.131] with 32 bytes of data:

Reply from 217.212.240.131: bytes=32 time=240ms TTL=111
Reply from 217.212.240.131: bytes=32 time=268ms TTL=111
Reply from 217.212.240.131: bytes=32 time=237ms TTL=111
Reply from 217.212.240.131: bytes=32 time=237ms TTL=111

Ping statistics for 217.212.240.131:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 268ms, Average = 245ms

Cheers
Richard
(ingame Siam)
 
From Latvia:

PING rp.entropiauniverse.com (217.212.240.131): 56 data bytes
64 bytes from 217.212.240.131: icmp_seq=0 ttl=121 time=11.600 ms
64 bytes from 217.212.240.131: icmp_seq=1 ttl=121 time=12.832 ms
64 bytes from 217.212.240.131: icmp_seq=2 ttl=121 time=11.889 ms
64 bytes from 217.212.240.131: icmp_seq=3 ttl=121 time=13.066 ms
64 bytes from 217.212.240.131: icmp_seq=4 ttl=121 time=11.906 ms

--- rp.entropiauniverse.com ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 11.600/12.259/13.066/0.579 ms

From my point of view Entropia works pretty good after VU 8.6.

http://latviantelecoms.blogspot.com/ said:
Lattelekom, which owns a majority share in a Baltic subsea optical cable (the minority owner is Sweden's Tele2) has just pumped up the bandwidth on this pipe to 10Gbps from an earlier 622Mbps. The company installed a repeaterless Siemens solution on the ca. 300 kilometer long link from Ventspils in Latvia to Nynäshamn in Sweden. The jazzed up fiber is expected to go commercial very soon, with Lattelekom convinced it will fill enough of the pipe to pay off some EUR 1 million spent on the upgrade.
 
jdegre said:
It seems that problems start when packets go through the telia routers, before even reaching the EU servers.
Am I the only one experiencing this??? Any hint would be really appreciated.

Cheers,
/jdegre.
"You are not alone"

I'm 23 ms to the telia servers then it jumps to 68 then 95 then 186 and keeps going.
 
Back
Top