Página 1 de 2 12 ÚltimoÚltimo
Resultados 1 a 10 de 12

Tópico: ThePrimeHost

  1. #1
    Guru Junior
    Data de Ingresso
    Nov 2010
    Posts
    237

    ThePrimeHost

    Alguém já usou os dedicados deles?

    Vi que os servidores ficam na Colo@ em Atlanta.

  2. #2
    Guru Junior
    Data de Ingresso
    Nov 2010
    Posts
    237
    Acabei comprando um dedicado com eles, o preço estava muito bom em uma promoção postada no WHT-US. Até agora tudo ok, rede com 100% de uptime e ping médio aqui 105ms.

    Tive apenas um pequeno problema ao comprar, os HDs que entregaram mostravam erros no smart. Mesmo assim tudo funcionando normalmente (falaram que era normal alguns erros).

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,033
    Olho vivo na conectividade da Colo@

    Eu tive 3 experiências ruins com a banda deles: Phoenix, LA, e Atlanta, sendo essa última a pior de todas, com rotas péssimas além de packet loss. Isso dentro dos EUA. Para o Brasil, não sei.

  4. #4
    Guru Junior
    Data de Ingresso
    Nov 2010
    Posts
    237
    Como eu disse, até agora nada a reclamar. A rede está 100%.

    Rota registro.br:

    1 xe-1-0-1.50.ar1.nu.registro.br (200.160.2.1) 0.334 ms
    2 ae0-0.core1.nu.registro.br (200.160.0.253) 0.627 ms
    3 xe-0-0-0-0.gw1.nu.registro.br (200.160.0.167) 29.339 ms
    4 xe-0-2-0-537.edge-c.spo511.ctbc.com.br (187.32.53.70) 0.800 ms
    5 xe-2-2-0-0.core-b.spo511.ctbc.com.br (201.48.44.94) 0.868 ms
    6 ae1-0.core-b.ula001.ctbc.com.br (201.48.44.13) 19.932 ms
    7 et-3-0-0-0.core-a.ula001.ctbc.com.br (201.48.44.5) 20.304 ms
    8 xe-2-1-0-0.border-a.ash.ctbc.com.br (201.48.46.173) 182.700 ms
    9 10ge-equinix-ashburn.r1.ash1.us.as5580.net (206.126.236.204) 183.387 ms
    10 eth3-1.r1.atl1.us.atrato.net (78.152.34.181) 204.318 ms
    11 coloat-as46562-gw.r1.atl1.us.atrato.net (78.152.46.194) 195.571 ms
    12 xe9-4.dist-aa.atl01.coloat.com (184.170.251.250) 141.235 ms

    Rota aqui:

    1 24 ms 32 ms 26 ms embratel-F0-2-4-gacc01.mco.embratel.net.br [189.53.97.57]
    2 34 ms 30 ms 21 ms ebt-G1-0-0-dist02.mco.embratel.net.br [200.244.169.197]
    3 65 ms 29 ms 42 ms ebt-T0-0-2-0-tcore02.rce.embratel.net.br [200.244.40.190]
    4 128 ms 134 ms 117 ms ebt-T0-5-0-0-tcore01.flajn.embratel.net.br [200.230.251.234]
    5 117 ms 114 ms 110 ms ebt-P0-3-3-0-intl03.mianap.embratel.net.br [200.230.220.70]
    6 138 ms 102 ms 99 ms ae7.mia10.ip4.tinet.net [199.168.63.185]
    7 147 ms 149 ms 118 ms xe-3-0-0.atl11.ip4.tinet.net [89.149.180.202]
    8 * 115 ms 150 ms total-server-solutions-gw.ip4.tinet.net [173.241.130.54]
    9 150 ms 110 ms 124 ms ge1-2.6509-aa.34.coloat.com [206.220.173.26]
    10 114 ms 127 ms 109 ms ns1.theprimehost.com [199.116.112.10]

  5. #5
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,033
    Speedy SP

    C:\>ping -n 50 184.170.251.250

    Pinging 184.170.251.250 with 32 bytes of data:
    Request timed out.
    Reply from 184.170.251.250: bytes=32 time=187ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=201ms TTL=242
    Request timed out.
    Reply from 184.170.251.250: bytes=32 time=277ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=222ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=228ms TTL=242
    Request timed out.
    Reply from 184.170.251.250: bytes=32 time=216ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=208ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=209ms TTL=242
    Request timed out.
    Reply from 184.170.251.250: bytes=32 time=194ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=224ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=187ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=205ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=194ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=194ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=190ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=185ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=205ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=201ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=214ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=189ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=190ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=187ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=188ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=191ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=189ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=208ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=183ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=202ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=190ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=195ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=188ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=183ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=204ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=183ms TTL=242
    Request timed out.
    Reply from 184.170.251.250: bytes=32 time=195ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=187ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=195ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=203ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=201ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=184ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=199ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=188ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=205ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=204ms TTL=242
    Reply from 184.170.251.250: bytes=32 time=226ms TTL=242

    Ping statistics for 184.170.251.250:
    Packets: Sent = 50, Received = 45, Lost = 5 (10% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 183ms, Maximum = 277ms, Average = 199ms

    C:\>

    Registro.br -> GNAX

    1 xe-1-0-1.50.ar1.nu.registro.br (200.160.2.1)
    0.348 ms

    2 ae0-0.core1.nu.registro.br (200.160.0.253)
    0.631 ms

    3 xe-5-0-0-0.core1.gc.registro.br (200.160.0.163)
    0.796 ms

    4 xe-0-0-0-0.gw1.gc.registro.br (200.160.0.175)
    1.923 ms

    5 ge-2-0-1.ar4.gru1.gblx.net (159.63.48.37)
    1.406 ms

    6 ae6-90G.ar5.ATL1.gblx.net (67.16.156.138)
    120.725 ms

    7 xe-1-0-4.ar1.atl1.us.nlayer.net (69.31.135.197)
    122.174 ms

    8 as3595.xe-2-0-5-101.ar1.atl1.us.nlayer.net (69.31.135.42)
    121.022 ms

    9 atl-l3-2-g0-2.gnax.net (209.51.130.38)
    121.320 ms

    Amazon SP

    root@sp4:~# traceroute ns1.theprimehost.com
    traceroute to ns1.theprimehost.com (199.116.112.10), 30 hops max, 60 byte packets

    8 s0-1-0.hr1.gru2.gblx.net (64.214.143.97) 0.623 ms 0.624 ms Xe-6-1-6-0-grtsaosi3.red.telefonica
    -wholesale.net (84.16.9.77) 1.449 ms
    9 Xe2-0-0-0-grtmiana2.red.telefonica-wholesale.net (94.142.118.250) 117.119 ms Xe5-1-6-0-grtmiana
    3.red.telefonica-wholesale.net (94.142.119.14) 138.322 ms Xe0-1-2-0-grtmiana3.red.telefonica-wholes
    ale.net (94.142.119.10) 184.804 ms
    10 Xe2-1-1-0-grtwaseq6.red.telefonica-wholesale.net (94.142.123.186) 152.536 ms xe-1-0-4.ar1.atl1.
    us.nlayer.net (69.31.135.197) 121.667 ms Xe7-0-0-0-grtwaseq6.red.telefonica-wholesale.net (94.142.1
    21.162) 149.028 ms
    11 213.140.55.106 (213.140.55.106) 152.002 ms ae0-50g.cr1.atl1.us.nlayer.net (69.31.135.129) 120.
    303 ms 213.140.55.182 (213.140.55.182) 149.627 ms
    12 xe-7-0-0.atl11.ip4.tinet.net (141.136.108.138) 154.769 ms xe-8-0-0.atl11.ip4.tinet.net (141.136
    .108.142) 152.336 ms xe-4-3-0.atl11.ip4.tinet.net (141.136.108.134) 158.435 ms
    13 total-server-solutions-gw.ip4.tinet.net (173.241.130.54) 147.444 ms ge2-2.6509-aa.34.coloat.com
    (206.220.172.106) 120.569 ms 120.567 ms
    14 * ge1-2.6509-aa.34.coloat.com (206.220.173.26) 147.495 ms 147.230 ms
    15 * * *
    16 * * *
    17 * * *
    18 * * *^C
    root@sp4:~#
    Última edição por 5ms; 14-04-2013 às 20:29.

  6. #6
    Guru Junior
    Data de Ingresso
    Nov 2010
    Posts
    237
    ping -n 100 199.116.112.10

    Disparando 199.116.112.10 com 32 bytes de dados:
    Resposta de 199.116.112.10: bytes=32 tempo=111ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=126ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=133ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=131ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=123ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=138ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=135ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=195ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=133ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=119ms TTL=45
    Esgotado o tempo limite do pedido.
    Resposta de 199.116.112.10: bytes=32 tempo=143ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=121ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=111ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=112ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=152ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=114ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=105ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=115ms TTL=45
    Esgotado o tempo limite do pedido.
    Resposta de 199.116.112.10: bytes=32 tempo=131ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=154ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=120ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=141ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=126ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=146ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=126ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=114ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=136ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=109ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=131ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=128ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=121ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=137ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=109ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=128ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=105ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=126ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=117ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=130ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=144ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=127ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=149ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=138ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=109ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=153ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=135ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=125ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=121ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=147ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=129ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=132ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=173ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=112ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=119ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=165ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=138ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=114ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=168ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=115ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=108ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=137ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=108ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=125ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=122ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=539ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=136ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=138ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=117ms TTL=45
    Esgotado o tempo limite do pedido.
    Esgotado o tempo limite do pedido.
    Resposta de 199.116.112.10: bytes=32 tempo=167ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=170ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=131ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=169ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=156ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=136ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=145ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=119ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=145ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=169ms TTL=45
    Resposta de 199.116.112.10: bytes=32 tempo=134ms TTL=45

    Estatísticas do Ping para 199.116.112.10:
    Pacotes: Enviados = 100, Recebidos = 95, Perdidos = 5 (5% de
    perda),
    Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 105ms, Máximo = 824ms, Média = 145ms


    ping -n 100 gnax.net

    Disparando gnax.net [64.22.64.84] com 32 bytes de dados:
    Resposta de 64.22.64.84: bytes=32 tempo=147ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=109ms TTL=44
    Esgotado o tempo limite do pedido.
    Resposta de 64.22.64.84: bytes=32 tempo=127ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=128ms TTL=44
    Esgotado o tempo limite do pedido.
    Resposta de 64.22.64.84: bytes=32 tempo=111ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=128ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=133ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=145ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=136ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=133ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=132ms TTL=44
    Esgotado o tempo limite do pedido.
    Resposta de 64.22.64.84: bytes=32 tempo=132ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=147ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=140ms TTL=44
    Esgotado o tempo limite do pedido.
    Resposta de 64.22.64.84: bytes=32 tempo=125ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=152ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=123ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=133ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=121ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=145ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=145ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=115ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=104ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=123ms TTL=44
    Esgotado o tempo limite do pedido.
    Resposta de 64.22.64.84: bytes=32 tempo=119ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=159ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=115ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=129ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=140ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=130ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=138ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=106ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=120ms TTL=44
    Esgotado o tempo limite do pedido.
    Esgotado o tempo limite do pedido.
    Esgotado o tempo limite do pedido.
    Esgotado o tempo limite do pedido.
    Esgotado o tempo limite do pedido.
    Resposta de 64.22.64.84: bytes=32 tempo=283ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=110ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=145ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=134ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=686ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=119ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=1283ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=145ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=111ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=124ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=111ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=131ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=123ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=152ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=157ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=108ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=114ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=137ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=115ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=149ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=114ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=107ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=128ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=139ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=120ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=126ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=168ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=138ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=123ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=108ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=112ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=140ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=120ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=124ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=126ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=118ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=126ms TTL=44
    Resposta de 64.22.64.84: bytes=32 tempo=126ms TTL=44

    Estatísticas do Ping para 64.22.64.84:
    Pacotes: Enviados = 100, Recebidos = 89, Perdidos = 11 (11% de
    perda),
    Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 104ms, Máximo = 1283ms, Média = 148ms


    Já aqui perdeu mais pacotes na gnax, testei com um servidor em Miami e deu 15ms para colo@ e 28ms para gnax.

    OBS: retirei uma parte das respostas de ping pq ultrapassou o limite de caracteres da postagem.

  7. #7
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,033
    Não seja por isso

    root@ny11:~# traceroute GNAX | Cloud Computing Companies - Cloud Computing Providers - Cloud Hosting Providers - Cloud Hosting Services | GNAX
    traceroute to GNAX | Cloud Computing Companies - Cloud Computing Providers - Cloud Hosting Providers - Cloud Hosting Services | GNAX (64.22.64.84), 30 hops max, 60 byte packets

    3 ae-31-51.ebr1.Newark1.Level3.net (4.69.156.30) 1.473 ms te4-3.ccr01.jfk08.atlas.cogentco.com (3
    8.122.106.1) 107.830 ms 107.860 ms
    4 te0-6-0-7.ccr21.jfk02.atlas.cogentco.com (154.54.27.213) 1.195 ms ae-2-2.ebr1.NewYork1.Level3.n
    et (4.69.132.97) 1.434 ms 1.508 ms
    5 te0-3-0-6.ccr21.dca01.atlas.cogentco.com (154.54.41.5) 7.724 ms te0-0-0-2.ccr21.dca01.atlas.cog
    entco.com (154.54.25.238) 7.821 ms ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) 1.724 ms
    6 te0-0-0-3.ccr21.atl01.atlas.cogentco.com (154.54.28.202) 18.663 ms te0-1-0-7.ccr21.atl01.atlas.
    cogentco.com (154.54.24.154) 18.633 ms te0-3-0-7.ccr21.atl01.atlas.cogentco.com (154.54.42.194) 18
    .733 ms
    7 te2-1.ccr01.atl07.atlas.cogentco.com (154.54.26.49) 19.115 ms 19.099 ms 19.015 ms
    8 xe-1-0-4.ar1.atl1.us.nlayer.net (69.31.135.197) 20.040 ms 38.122.130.10 (38.122.130.10) 18.928
    ms 18.842 ms
    9 atl-core-h-p2.gnax.net (207.210.95.253) 18.972 ms as3595.xe-2-0-5-101.ar1.atl1.us.nlayer.net (6
    9.31.135.42) 19.959 ms atl-core-h-p2.gnax.net (207.210.95.253) 18.952 ms
    10 atl-l3-2-g0-2.gnax.net (209.51.130.38) 22.513 ms atl-core-g-g5-1.gnax.net (209.51.130.245) 19.
    726 ms 19.684 ms
    11 * * l3-atl-2-g0-1.gnax.net (63.247.85.1) 21.666 ms
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    16 * *^C
    root@ny11:~# traceroute Cpanel VPS | Managed VPS | Reseller Hosting with WHMCS End User Support | ThePrimeHost.com
    traceroute to Cpanel VPS | Managed VPS | Reseller Hosting with WHMCS End User Support | ThePrimeHost.com (199.116.112.10), 30 hops max, 60 byte packets

    3 ae-31-51.ebr1.Newark1.Level3.net (4.69.156.30) 1.458 ms 1.421 ms te4-3.ccr01.jfk08.atlas.cogen
    tco.com (38.122.106.1) 1.244 ms
    4 ae-2-2.ebr1.NewYork1.Level3.net (4.69.132.97) 1.421 ms te0-6-0-7.ccr22.jfk02.atlas.cogentco.com
    (154.54.27.217) 1.026 ms ae-2-2.ebr1.NewYork1.Level3.net (4.69.132.97) 1.494 ms
    5 ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 1.613 ms te0-6-0-6.ccr21.jfk07.atlas.cogentco.c
    om (154.54.80.178) 1.198 ms te0-5-0-3.ccr21.jfk07.atlas.cogentco.com (154.54.87.210) 1.224 ms
    6 ae-3-80.edge4.NewYork1.Level3.net (4.69.155.146) 1.414 ms tiscali.jfk07.atlas.cogentco.com (154
    .54.10.90) 1.219 ms ae-1-60.edge4.NewYork1.Level3.net (4.69.155.20) 1.458 ms
    7 64.215.195.213 (64.215.195.213) 1.542 ms 64.215.195.229 (64.215.195.229) 1.638 ms xe-7-0-0.atl
    11.ip4.tinet.net (141.136.108.138) 34.404 ms
    8 total-server-solutions-gw.ip4.tinet.net (173.241.130.54) 34.187 ms xe-1-0-4.ar1.atl1.us.nlayer.
    net (69.31.135.197) 22.835 ms 22.640 ms
    9 ge1-2.6509-aa.34.coloat.com (206.220.173.26) 21.276 ms 21.221 ms 20.992 ms
    10 abte2-1.10g.coloat.cust.atl01.mzima.net (67.199.136.182) 42.953 ms * 42.727 ms
    11 * ge2-2.6509-aa.34.coloat.com (206.220.172.106) 32.404 ms 33.537 ms
    12 * * *
    13 * * *
    14 * * *
    15 * * *
    16 * *^C
    root@ny11:~#

  8. #8
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,033
    root@ny11:~# ping -c 50 www.theprimehost.com
    PING theprimehost.com (199.116.112.10) 56(84) bytes of data.
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=1 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=2 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=3 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=4 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=5 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=6 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=7 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=8 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=9 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=10 ttl=51 time=21.4 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=11 ttl=51 time=21.3 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=12 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=13 ttl=51 time=20.9 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=14 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=15 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=16 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=17 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=18 ttl=51 time=21.3 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=19 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=20 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=21 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=22 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=23 ttl=51 time=21.5 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=24 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=25 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=26 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=27 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=28 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=29 ttl=51 time=21.3 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=30 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=31 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=32 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=33 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=34 ttl=51 time=21.4 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=35 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=36 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=37 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=38 ttl=51 time=21.0 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=39 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=40 ttl=51 time=21.3 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=41 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=42 ttl=51 time=21.5 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=43 ttl=51 time=22.8 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=44 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=45 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=46 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=47 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=48 ttl=51 time=21.1 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=49 ttl=51 time=21.2 ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=50 ttl=51 time=21.2 ms
    --- theprimehost.com ping statistics ---
    50 packets transmitted, 50 received, 0% packet loss, time 49075ms
    rtt min/avg/max/mdev = 20.980/21.242/22.895/0.275 ms
    root@ny11:~#
    root@ny11:~#
    root@ny11:~# ping -c 50 www.gnax.com
    PING www.gnax.net (64.22.64.84) 56(84) bytes of data.
    64 bytes from 64.22.64.84: icmp_req=1 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=2 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=3 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=4 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=5 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=6 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=7 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=8 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=9 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=10 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=11 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=12 ttl=52 time=21.8 ms
    64 bytes from 64.22.64.84: icmp_req=13 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=14 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=15 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=16 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=17 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=18 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=19 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=20 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=21 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=22 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=23 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=24 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=25 ttl=52 time=23.1 ms
    64 bytes from 64.22.64.84: icmp_req=26 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=27 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=28 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=29 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=30 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=31 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=32 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=33 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=34 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=35 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=36 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=37 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=38 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=39 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=40 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=41 ttl=52 time=21.3 ms
    64 bytes from 64.22.64.84: icmp_req=42 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=43 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=44 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=45 ttl=52 time=21.2 ms
    64 bytes from 64.22.64.84: icmp_req=46 ttl=52 time=21.3 ms
    64 bytes from 64.22.64.84: icmp_req=47 ttl=52 time=23.1 ms
    64 bytes from 64.22.64.84: icmp_req=48 ttl=52 time=21.1 ms
    64 bytes from 64.22.64.84: icmp_req=49 ttl=52 time=21.0 ms
    64 bytes from 64.22.64.84: icmp_req=50 ttl=52 time=21.0 ms
    --- www.gnax.net ping statistics ---
    50 packets transmitted, 50 received, 0% packet loss, time 49079ms
    rtt min/avg/max/mdev = 21.022/21.216/23.185/0.451 ms
    root@ny11:~#

  9. #9
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,033
    Citação Postado originalmente por alvaro Ver Post
    Estatísticas do Ping para 199.116.112.10:
    Pacotes: Enviados = 100, Recebidos = 95, Perdidos = 5 (5% de perda),
    Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 105ms, Máximo = 824ms, Média = 145ms

    Estatísticas do Ping para 64.22.64.84:
    Pacotes: Enviados = 100, Recebidos = 89, Perdidos = 11 (11% de perda),
    Aproximar um número redondo de vezes em milissegundos:
    Mínimo = 104ms, Máximo = 1283ms, Média = 148ms
    Estranho !
    Última edição por 5ms; 14-04-2013 às 21:05.

  10. #10
    Guru Junior
    Data de Ingresso
    Nov 2010
    Posts
    237
    Miami:

    C:\Users\Administrator>ping gnax.net

    Disparando gnax.net [64.22.64.84] com 32 bytes de dados:
    Resposta de 64.22.64.84: bytes=32 tempo=29ms TTL=50
    Resposta de 64.22.64.84: bytes=32 tempo=28ms TTL=50
    Resposta de 64.22.64.84: bytes=32 tempo=28ms TTL=50
    Resposta de 64.22.64.84: bytes=32 tempo=28ms TTL=50

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

    C:\Users\Administrator>ping theprimehost.com

    Disparando theprimehost.com [199.116.112.10] com 32 bytes de dados:
    Resposta de 199.116.112.10: bytes=32 tempo=15ms TTL=57
    Resposta de 199.116.112.10: bytes=32 tempo=15ms TTL=57
    Resposta de 199.116.112.10: bytes=32 tempo=15ms TTL=57
    Resposta de 199.116.112.10: bytes=32 tempo=15ms TTL=57

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

    Los Angeles:

    ping -c 4 gnax.net
    PING gnax.net (64.22.64.84) 56(84) bytes of data.
    64 bytes from 64.22.64.84: icmp_seq=1 ttl=53 time=55.2 ms
    64 bytes from 64.22.64.84: icmp_seq=2 ttl=53 time=55.0 ms
    64 bytes from 64.22.64.84: icmp_seq=3 ttl=53 time=55.2 ms
    64 bytes from 64.22.64.84: icmp_seq=4 ttl=53 time=55.2 ms

    --- gnax.net ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3059ms
    rtt min/avg/max/mdev = 55.073/55.175/55.224/0.176 ms

    ping -c 4 theprimehost.com
    PING theprimehost.com (199.116.112.10) 56(84) bytes of data.
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=1 ttl=57 time=51.0
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=2 ttl=57 time=50.7
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=3 ttl=57 time=50.7
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=4 ttl=57 time=50.8
    ms

    --- theprimehost.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3056ms
    rtt min/avg/max/mdev = 50.719/50.850/51.079/0.263 ms

    Orlando:

    ping -c 4 gnax.net
    PING gnax.net (64.22.64.84) 56(84) bytes of data.
    64 bytes from 64.22.64.84: icmp_seq=1 ttl=49 time=29.6 ms
    64 bytes from 64.22.64.84: icmp_seq=2 ttl=49 time=29.5 ms
    64 bytes from 64.22.64.84: icmp_seq=3 ttl=49 time=29.4 ms
    64 bytes from 64.22.64.84: icmp_seq=4 ttl=49 time=29.5 ms

    --- gnax.net ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3012ms
    rtt min/avg/max/mdev = 29.433/29.540/29.686/0.152 ms

    ping -c 4 theprimehost.com
    PING theprimehost.com (199.116.112.10) 56(84) bytes of data.
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=1 ttl=56 time=22.3
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=2 ttl=56 time=22.0
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=3 ttl=56 time=22.2
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=4 ttl=56 time=22.2
    ms

    --- theprimehost.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3014ms
    rtt min/avg/max/mdev = 22.052/22.219/22.337/0.181 ms

    Las Vegas:

    ping -c 4 gnax.net
    PING gnax.net (64.22.64.84) 56(84) bytes of data.
    64 bytes from 64.22.64.84: icmp_seq=1 ttl=53 time=63.1 ms
    64 bytes from 64.22.64.84: icmp_seq=2 ttl=53 time=64.1 ms
    64 bytes from 64.22.64.84: icmp_seq=3 ttl=53 time=62.9 ms
    64 bytes from 64.22.64.84: icmp_seq=4 ttl=53 time=63.1 ms

    --- gnax.net ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 62.910/63.352/64.139/0.530 ms

    ping -c 4 theprimehost.com
    PING theprimehost.com (199.116.112.10) 56(84) bytes of data.
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=1 ttl=53 time=62.3
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=2 ttl=53 time=60.6
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=3 ttl=53 time=61.0
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=4 ttl=53 time=61.3
    ms

    --- theprimehost.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 60.610/61.350/62.397/0.701 ms

    Kansas City:

    ping -c 4 gnax.net
    PING gnax.net (64.22.64.84) 56(84) bytes of data.
    64 bytes from 64.22.64.84: icmp_req=1 ttl=55 time=31.2 ms
    64 bytes from 64.22.64.84: icmp_req=2 ttl=55 time=31.2 ms
    64 bytes from 64.22.64.84: icmp_req=3 ttl=55 time=30.8 ms
    64 bytes from 64.22.64.84: icmp_req=4 ttl=55 time=31.1 ms

    --- gnax.net ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3005ms
    rtt min/avg/max/mdev = 30.839/31.110/31.247/0.161 ms

    ping -c 4 theprimehost.com
    PING theprimehost.com (199.116.112.10) 56(84) bytes of data.
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=1 ttl=56 time=28.4
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=2 ttl=56 time=29.5
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=3 ttl=56 time=29.1
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_req=4 ttl=56 time=28.6
    ms

    --- theprimehost.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3004ms
    rtt min/avg/max/mdev = 28.451/28.945/29.501/0.404 ms

    Canada:

    ping -c 4 gnax.net
    PING gnax.net (64.22.64.84) 56(84) bytes of data.
    64 bytes from 64.22.64.84: icmp_seq=1 ttl=51 time=32.2 ms
    64 bytes from 64.22.64.84: icmp_seq=2 ttl=51 time=32.2 ms
    64 bytes from 64.22.64.84: icmp_seq=3 ttl=51 time=32.5 ms
    64 bytes from 64.22.64.84: icmp_seq=4 ttl=51 time=32.0 ms

    --- gnax.net ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 32.033/32.274/32.576/0.266 ms

    ping -c 4 theprimehost.com
    PING theprimehost.com (199.116.112.10) 56(84) bytes of data.
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=1 ttl=54 time=32.5
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=2 ttl=54 time=32.5
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=3 ttl=54 time=32.4
    ms
    64 bytes from ns1.theprimehost.com (199.116.112.10): icmp_seq=4 ttl=54 time=32.4
    ms

    --- theprimehost.com ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3003ms
    rtt min/avg/max/mdev = 32.422/32.468/32.502/0.132 ms

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens
  •