Pings Needed from South American Players updated

suavyyyyyyyy · July 2011

São Paulo, Carapicuiba, Brazil

Disparando 200.145.1.9 com 32 bytes de dados:
Resposta de 200.145.1.9: bytes=32 tempo=39ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=39ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=40ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=40ms TTL=54

Estatísticas do Ping para 200.145.1.9:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de
perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 39ms, Máximo = 40ms, Média = 39ms

Disparando 129.171.32.100 com 32 bytes de dados:
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.
Esgotado o tempo limite do pedido.

Estatísticas do Ping para 129.171.32.100:
Pacotes: Enviados = 4, Recebidos = 0, Perdidos = 4 (100% de
perda),

TechziNN · July 2011

Rio de Janeiro, Rio de Janeiro, Brasil.
Reply from 200.145.1.9: bytes=32 time=21ms TTL=56
Reply from 200.145.1.9: bytes=32 time=22ms TTL=56
Reply from 200.145.1.9: bytes=32 time=21ms TTL=56
Reply from 200.145.1.9: bytes=32 time=37ms TTL=56

ronaldinha23 · July 2011

Rio de Janeiro, Rio de janeiro Brazil

Disparando 200.145.1.9 com 32 bytes de dados:
Resposta de 200.145.1.9: bytes=32 tempo=61ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=27ms TTL=53
Resposta de 200.145.1.9: bytes=32 tempo=28ms TTL=53
Resposta de 200.145.1.9: bytes=32 tempo=24ms TTL=53

Gustavo88888 · July 2011

Rio de Janeiro, Brazil
Resposta de 200.145.1.9:Bytes=32 Tempo=50ms TTL=54
Resposta de 200.145.1.9:Bytes=32 Tempo=43ms TTL=55
Resposta de 200.145.1.9:Bytes=32 Tempo=45ms TTL=56
Resposta de 200.145.1.9:Bytes=32 Tempo=43ms TTL=54

Mínimo; 43ms Máximo; 50ms Média; 45ms

FoxKing00 · July 2011

Brazil~São paulo~Itu
Disparando 200.145.1.9 com 32 bytes de dados:
Resposta de 200.145.1.9: bytes=32 tempo=43ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=43ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=42ms TTL=54
Resposta de 200.145.1.9: bytes=32 tempo=42ms TTL=54

Aproximar um número redondo de vezes em milissegundos:
Mínimo = 42ms, Máximo = 43ms, Média = 42ms
__________________________________________________

Disparando 64.209.90.71 com 32 bytes de dados:
Resposta de 64.209.90.71: bytes=32 tempo=219ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=209ms TTL=119
Resposta de 64.209.90.71: bytes=32 tempo=206ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=204ms TTL=118

Aproximar um número redondo de vezes em milissegundos:
Mínimo = 204ms, Máximo = 219ms, Média = 209ms

kawazaki3 · July 2011

Ping

Carlópolis , Paraná , Brazil

Reply from 200.145.1.9: bytes=32 time=82 TTL=52
Reply from 200.145.1.9: bytes=32 time=57 TTL=52
Reply from 200.145.1.9: bytes=32 time=54 TTL=52
Reply from 200.145.1.9: bytes=32 time=52 TTL=52

and

Reply from 64.209.90.71: bytes=32 time=249 TTL=116
Reply from 64.209.90.71: bytes=32 time=261 TTL=116
Reply from 64.209.90.71: bytes=32 time=249 TTL=116
Reply from 64.209.90.71: bytes=32 time=291 TTL=116

FoxKing00 · July 2011

(#666) /\

ronaldinha23 · July 2011

Rio de Janeiro, Rio de janeiro Brazil

Disparando 64.209.90.71 com 32 bytes de dados:
Resposta de 64.209.90.71: bytes=32 tempo=997ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=389ms TTL=119
Resposta de 64.209.90.71: bytes=32 tempo=601ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=580ms TTL=119

FineExD · July 2011

Reply from 200.145.1.9: bytes=32 time=48 TTL=52
Reply from 200.145.1.9: bytes=32 time=48 TTL=52
Reply from 200.145.1.9: bytes=32 time=49 TTL=52
Reply from 200.145.1.9: bytes=32 time=50 TTL=52

gsdgsdgdgsgd · July 2011

edit:sorry i didnt read the title i was from Ireland

nuLLLLL · July 2011

São paulo, São Paulo, Brasil.

Ping 200.145.1.9

Reply from 200.145.1.9: bytes=22 time=79 TTL=55
Reply from 200.145.1.9: bytes=23 time=79 TTL=55
Reply from 200.145.1.9: bytes=22 time=79 TTL=55
Reply from 200.145.1.9: bytes=26 time=79 TTL=55

Ping 64.209.90.71

Reply from 64.209.90.71: bytes=32 time=198 TTL=120
Reply from 64.209.90.71: bytes=32 time=264 TTL=120
Reply from 64.209.90.71: bytes=32 time=198 TTL=120
Reply from 64.209.90.71: bytes=32 time=198 TTL=120

KahMytos · July 2011

C:\Users\User>ping 200.145.9.1

Disparando 200.145.9.1 com 32 bytes de dados:
Resposta de 200.145.9.1: bytes=32 tempo=40ms TTL=55
Resposta de 200.145.9.1: bytes=32 tempo=45ms TTL=55
Resposta de 200.145.9.1: bytes=32 tempo=34ms TTL=55
Resposta de 200.145.9.1: bytes=32 tempo=20ms TTL=55

Country: Brazil
State: São Paulo
City: Sorocaba

9GeGe3 · July 2011

City: Diadema

State:São Paulo

Country:Brazil

Reply from 64.209.90.71: bytes=32 time=215ms TTL=119
Reply from 64.209.90.71: bytes=32 time=224ms TTL=118
Reply from 64.209.90.71: bytes=32 time=228ms TTL=118
Reply from 64.209.90.71: bytes=32 time=222 ms TTL=118

Minimo = 215ms , Maximo = 228ms , Media =222ms

RickCastle · July 2011

My CMD Results !

~ Ping 1 ~

Fortaleza, Ceará, Brasil.
Reply from 200.145.1.9: bytes=32 time=50ms TTL=55
Reply from 200.145.1.9: bytes=32 time=50ms TTL=55
Reply from 200.145.1.9: bytes=32 time=50ms TTL=55
Reply from 200.145.1.9: bytes=32 time=49ms TTL=55

~ Ping 2 ~

Fortaleza, Ceará, Brasil.
Reply from 64.209.90.71: bytes=32 time=73ms TTL=121
Reply from 64.209.90.71: bytes=32 time=74ms TTL=121
Reply from 64.209.90.71: bytes=32 time=73ms TTL=121
Reply from 64.209.90.71: bytes=32 time=73ms TTL=121

du92i · July 2011

Reply from 200.145.1.9: bytes=32 time=291ms TTL=43
Reply from 200.145.1.9: bytes=32 time=290ms TTL=43
Reply from 200.145.1.9: bytes=32 time=304ms TTL=43

Ping statistics for 200.145.1.9:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 290ms, Maximum = 304ms, Average = 295ms

du92i · July 2011

Reply from 64.209.90.71: bytes=32 time=180ms TTL=116
Reply from 64.209.90.71: bytes=32 time=181ms TTL=116
Reply from 64.209.90.71: bytes=32 time=180ms TTL=116
Reply from 64.209.90.71: bytes=32 time=183ms TTL=116

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

paulosimples · July 2011

Rio de janeiro, Rio de janeiro, Brasil

Reply from 200.145.1.9: bytes=32 time=23ms TTL=55
Reply from 200.145.1.9: bytes=32 time=20ms TTL=55
Reply from 200.145.1.9: bytes=32 time=30ms TTL=55
Reply from 200.145.1.9: bytes=32 time=19ms TTL=55

..........................................

Reply from 64.209.90.71: bytes=32 tempo=180ms TTL=122
Reply from 64.209.90.71: bytes=32 tempo=180ms TTL=122
Reply from 64.209.90.71: bytes=32 tempo=180ms TTL=122
Reply from 64.209.90.71: bytes=32 tempo=180ms TTL=122

FineExD · July 2011

Resposta de 200.145.1.9: bytes=32 time=51ms TTL=52
Resposta de 200.145.1.9: bytes=32 time=50ms TTL=52
Resposta de 200.145.1.9: bytes=32 time=51ms TTL=52
Resposta de 200.145.1.9: bytes=32 time=48ms TTL=52

----

Resposta de 64.209.90.71: bytes=32 tempo=219ms TTL=117
Resposta de 64.209.90.71: bytes=32 tempo=215ms TTL=118
Resposta de 64.209.90.71: bytes=32 tempo=230ms TTL=117
Resposta de 64.209.90.71: bytes=32 tempo=215ms TTL=118

Interior de São Paulo.

wHat6587 · July 2011

Bento Gonçalves, Rio Grande do Sul, Brazil

Reply from 64.209.90.71: bytes=32 time=144ms TTL=55
Reply from 64.209.90.71: bytes=32 time=146ms TTL=55
Reply from 64.209.90.71: bytes=32 time=141ms TTL=55
Reply from 64.209.90.71: bytes=32 time=143ms TTL=55

It looks bad, the old was better \/

Reply 200.145.1.9: bytes=32 time=27ms TTL=55
Reply 200.145.1.9: bytes=32 time=27ms TTL=55
Reply 200.145.1.9: bytes=32 time=30ms TTL=55
Reply 200.145.1.9: bytes=32 time=27ms TTL=55

MundoKnc · July 2011

São Paulo, Carapicuiba, Brasil
Resposta de 200.145.1.9: byte=32 tempo=27ms TTL=53
Resposta de 200.145.1.9: byte=32 tempo=30ms TTL=53
Resposta de 200.145.1.9: byte=32 tempo=26ms TTL=53
Resposta de 200.145.1.9: byte=32 tempo=26ms TTL=53

Resposta de 64.209.90.71: byte=32 tempo=192ms TTL=119
Resposta de 64.209.90.71: byte=32 tempo=189ms TTL=118
Resposta de 64.209.90.71: byte=32 tempo=207ms TTL=119
Resposta de 64.209.90.71: byte=32 tempo=194ms TTL=119

m2638621 · July 2011

Rio de Janeiro, Rio de Janeiro

Resposta de 200.145.1.9: byte=32 tempo=21ms TTL=55
Resposta de 200.145.1.9: byte=32 tempo=20ms TTL=55
Resposta de 200.145.1.9: byte=32 tempo=20ms TTL=55
Resposta de 200.145.1.9: byte=32 tempo=21ms TTL=55

LokosSG · July 2011

Disparando 200.145.1.9 com 32 bytes de dados:
Resposta de 200.145.1.9: bytes=32 tempo=21ms TTL=52
Resposta de 200.145.1.9: bytes=32 tempo=21ms TTL=52
Resposta de 200.145.1.9: bytes=32 tempo=22ms TTL=52
Resposta de 200.145.1.9: bytes=32 tempo=22ms TTL=52

Estatísticas do Ping para 200.145.1.9:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 21ms, Máximo = 22ms, Média = 21ms

Hortolândia / São paulo / Brazil

sihxD · July 2011

Ping 64.209.90.71

Reply from 64.209.90.71: bytes=32 time=161 TTL=117
Reply from 64.209.90.71: bytes=32 time=146 TTL=117
Reply from 64.209.90.71: bytes=32 time=169 TTL=117
Reply from 64.209.90.71: bytes=32 time=149 TTL=117

caiomacho · July 2011

hello,

Campinas, São Paulo , Brasil

Ping 200.145.1.9:

reply from 200.145.1.9: bytes=32 time=41ms TTL=52
reply from 200.145.1.9: bytes=32 time=44ms TTL=52
reply from 200.145.1.9: bytes=32 time=45ms TTL=52
reply from 200.145.1.9: bytes=32 time=44ms TTL=52

Ping 64.209.90.71:

reply from 64.209.90.71: bytes=32 time=225ms TTL=118
reply from 64.209.90.71: bytes=32 time=216ms TTL=118
reply from 64.209.90.71: bytes=32 time=218ms TTL=118
reply from 64.209.90.71: bytes=32 time=229ms TTL=118

--//--

Caio Barbosa

asdplLS · July 2011

Disparando 200.145.1.9 com 32 bytes de dados:
Resposta de 200.145.1.9: bytes=32 tempo=21ms TTL=52
Resposta de 200.145.1.9: bytes=32 tempo=21ms TTL=52
Resposta de 200.145.1.9: bytes=32 tempo=22ms TTL=52
Resposta de 200.145.1.9: bytes=32 tempo=22ms TTL=52

Estatísticas do Ping para 200.145.1.9:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 21ms, Máximo = 22ms, Média = 21ms

Hortolândia / São paulo / Brazil

015Avon · July 2011

Praia Grande, São Paulo, Brazil

Reply from 200.145.1.9: bytes=34 time=10ms TTL=53
Reply from 200.145.1.9: bytes=34 time=10ms TTL=53
Reply from 200.145.1.9: bytes=32 time=10ms TTL=53
Reply from 200.145.1.9: bytes=36 time=11ms TTL=53

rodolfo3142 · July 2011

Ping

ping 7~13

State: Sao Paulo
City : Campinas

luanapiovana · July 2011

Crossfire Brasil

Country: Brazil
State: Rio De Janeiro
City: Rio de Janeiro
Age: 15 years
Reply from 200.145.1.9: bytes = 32 time = 134ms TTL = 55
Reply from 200.145.1.9: bytes = 32 time = 33ms TTL = 54
Reply from 200.145.1.9: bytes = 32 time = 33ms TTL = 54
Reply from 200.145.1.9: bytes = 32 time = 31ms TTL = 54

TiagoShot · July 2011

Lavínia, São Paulo, Brazil.

Resposta de 200.145.1.9: bytes=32 tempo=24ms TTL=55
Resposta de 200.145.1.9: bytes=32 tempo=25ms TTL=55
Resposta de 200.145.1.9: bytes=32 tempo=46ms TTL=55
Resposta de 200.145.1.9: bytes=32 tempo=59ms TTL=55

Estatísticas do Ping para 200.145.1.9:
Pacotes: Enviados = 4, Recebidos = 4, Perdidos = 0 (0% de perda),
Aproximar um número redondo de vezes em milissegundos:
Mínimo = 24ms, Máximo = 59ms, Média = 38ms

brunomarcal · July 2011

Resposta de 64.209.90.71: bytes=32 tempo=118ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=118ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=118ms TTL=120
Resposta de 64.209.90.71: bytes=32 tempo=118ms TTL=120

curitiba paraná Brazil

Pings Needed from South American Players updated

Comments

Categories

Pings Needed from South American Players *updated*

Comments

Categories

Pings Needed from South American Players updated