Whats your ping and where do you live?

Estadísticas de ping para 64.125.26.73:
Paquetes: enviados = 100, recibidos = 100, perdidos = 0
(0% perdidos),
Tiempos aproximados de ida y vuelta en milisegundos:
Mínimo = 206ms, Máximo = 498ms, Media = 224ms

224ms average... you lucky Europeans. :(

I live in Caracas, Venezuela.
 
Germany, Hannover

Ping wird ausgeführt für 64.125.26.73 mit 32 Bytes Daten:

Antwort von 64.125.26.73: Bytes=32 Zeit=60ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=10ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=10ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=83ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=10ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=10ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=10ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=29ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=10ms TTL=53
Antwort von 64.125.26.73: Bytes=32 Zeit=9ms TTL=53

Ping-Statistik für 64.125.26.73:
Pakete: Gesendet = 39, Empfangen = 39, Verloren = 0 (0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 9ms, Maximum = 83ms, Mittelwert = 12ms
 
Minimum = 171ms, Maximum = 242ms, Average = 182ms

I'm from Lima capital of Perú
 
About 20 km away from servers, Holland

Microsoft Windows [versie 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.

C:\Users\SuperKanjo>ping 64.125.26.73

Pingen naar 64.125.26.73 met 32 bytes aan gegevens:
Antwoord van 64.125.26.73: bytes=32 tijd=9 ms TTL=57
Antwoord van 64.125.26.73: bytes=32 tijd=8 ms TTL=57
Antwoord van 64.125.26.73: bytes=32 tijd=11 ms TTL=57
Antwoord van 64.125.26.73: bytes=32 tijd=10 ms TTL=57

Ping-statistieken voor 64.125.26.73:
Pakketten: verzonden = 4, ontvangen = 4, verloren = 0
(0% verlies).

De gemiddelde tijd voor het uitvoeren van één bewerking in milliseconden:
Minimum = 8ms, Maximum = 11ms, Gemiddelde = 9ms
 
Here a live feed from the Netherlands

66320_167891473227043_100000185754991_614816_3921823_n.jpg
 
Vancouver, Canada (West-coast)

Reply from 64.125.26.73: bytes=32 time=168ms TTL=47
Reply from 64.125.26.73: bytes=32 time=250ms TTL=47
Reply from 64.125.26.73: bytes=32 time=177ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=168ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=166ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47
Reply from 64.125.26.73: bytes=32 time=169ms TTL=47
Reply from 64.125.26.73: bytes=32 time=165ms TTL=47

so, 170 shell we say..


some
 
Moscow, Russia

Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Minimum = 78ms, Maximum = 110ms, Average = 80ms
 
My latency is about 30-35ms and I actually have a rather bad connection in every aspect. speed is crappy, router is crappy, multiple users and stuff, so although I live in Denmark, which is rather close to MA, I'm rather surprised by this result.

edit:
Should be noted, to those with high ping, that it's not too important. What really matters is stability, i.e. packet loss. Of course if you're doing a lot of PVP'in, you want a low ping and also, in any case, you probably don't want to get much higher than 250ms and if you approach 500ms, you're pretty screwed ;)
 
Edinburgh, Scotland, UK


C:\>ping 64.125.26.73

Pinging 64.125.26.73 with 32 bytes of data:
Reply from 64.125.26.73: bytes=32 time=36ms TTL=54
Reply from 64.125.26.73: bytes=32 time=36ms TTL=54
Reply from 64.125.26.73: bytes=32 time=35ms TTL=54
Reply from 64.125.26.73: bytes=32 time=36ms TTL=54

Ping statistics for 64.125.26.73:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 35ms, Maximum = 36ms, Average = 35ms
 
East Coast, USA (Maine)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Rick>ping 64.125.26.73 /t
Pinging 64.125.26.73 with 32 bytes of data:
Reply from 64.125.26.73: bytes=32 time=102ms TTL=50
Reply from 64.125.26.73: bytes=32 time=100ms TTL=50
Reply from 64.125.26.73: bytes=32 time=99ms TTL=50
Reply from 64.125.26.73: bytes=32 time=100ms TTL=50
Reply from 64.125.26.73: bytes=32 time=100ms TTL=50
Reply from 64.125.26.73: bytes=32 time=109ms TTL=50
Reply from 64.125.26.73: bytes=32 time=103ms TTL=50
Reply from 64.125.26.73: bytes=32 time=99ms TTL=50
Reply from 64.125.26.73: bytes=32 time=118ms TTL=50
Reply from 64.125.26.73: bytes=32 time=102ms TTL=50
Reply from 64.125.26.73: bytes=32 time=101ms TTL=50
Reply from 64.125.26.73: bytes=32 time=108ms TTL=50
Reply from 64.125.26.73: bytes=32 time=102ms TTL=50
Reply from 64.125.26.73: bytes=32 time=101ms TTL=50
Reply from 64.125.26.73: bytes=32 time=105ms TTL=50
Reply from 64.125.26.73: bytes=32 time=99ms TTL=50
Reply from 64.125.26.73: bytes=32 time=101ms TTL=50
Reply from 64.125.26.73: bytes=32 time=103ms TTL=50
Reply from 64.125.26.73: bytes=32 time=116ms TTL=50
Reply from 64.125.26.73: bytes=32 time=102ms TTL=50
Reply from 64.125.26.73: bytes=32 time=107ms TTL=50
 
average 138-148, Missouri.
 
East Coast North America, Montreal Canada

average 107 ms
 
your all doing it wrong!!

why have such a small packet size?
go big :)
ping 64.125.26.73 -t -l 65500

simulate a heavy game stream of data!

I got some interesting results from Ny USA
 
383
But interesting variations :(
Western Australia
 
~ 130 for me.

Ontario...
 
Sooo everyone is posting in here...are we gonna get to know why here any time soon? and what you needed all this for?
 
Average 149 near Tampa, Florida
 
Is that ip address still good? (64.125.26.73)
I am not able to ping it.
 
same here :( ( to short?)
 
Last edited:
Back
Top