HeavyHost

Informações desta rede

Localização do Servidor: Ashburn, USA

Teste via IPv4: 172.106.11.155

Arquivos de teste: 100MB 1000MB

Seu endereço IP: 100.24.46.10

Testes de rede
Histórico de Testes
-------------------------------------------------------------------

Tracing route to WIN-ETGQQT9LA10 [172.106.11.155]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  WIN-ETGQQT9LA10 [172.106.11.155]

Trace complete.
-------------------------------------------------------------------

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging ddos-protected-by.heavyhost.net [172.106.11.136] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 172.106.11.136:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

Ping statistics for 172.106.11.155:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
-------------------------------------------------------------------
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    ddos-protected-by.heavyhost.net
Address:  172.106.11.155

-------------------------------------------------------------------
-------------------------------------------------------------------
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    ddos-protected-by.heavyhost.net
Address:  172.106.11.155

-------------------------------------------------------------------

Tracing route to WIN-ETGQQT9LA10 [172.106.11.155]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  WIN-ETGQQT9LA10 [172.106.11.155]

Trace complete.
-------------------------------------------------------------------

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging ddos-protected-by.heavyhost.net [172.106.11.129] with 32 bytes of data:
Reply from 172.106.11.129: bytes=32 time=1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging 179.179.15.40.dynamic.adsl.gvt.net.br [179.179.15.40] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 179.179.15.40:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    179.179.15.40.dynamic.adsl.gvt.net.br
Address:  179.179.15.40

-------------------------------------------------------------------

Pinging 179.179.15.40.dynamic.adsl.gvt.net.br [179.179.15.40] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 179.179.15.40:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Pinging 143.202.36.71 with 32 bytes of data:
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=210ms TTL=122

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

Pinging 143.202.36.71 with 32 bytes of data:
Reply from 143.202.36.71: bytes=32 time=209ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122

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

Pinging 143.202.36.71 with 32 bytes of data:
Reply from 143.202.36.71: bytes=32 time=209ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122
Reply from 143.202.36.71: bytes=32 time=208ms TTL=122

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging 30.77.22.177.strnet.com.br [177.22.77.30] with 32 bytes of data:
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50

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

Pinging 30.77.22.177.strnet.com.br [177.22.77.30] with 32 bytes of data:
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50
Reply from 177.22.77.30: bytes=32 time=144ms TTL=50

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

Pinging utorrentfilmes.net [104.28.24.3] with 32 bytes of data:
Reply from 104.28.24.3: bytes=32 time=1ms TTL=58
Reply from 104.28.24.3: bytes=32 time=1ms TTL=58
Reply from 104.28.24.3: bytes=32 time=1ms TTL=58
Reply from 104.28.24.3: bytes=32 time=1ms TTL=58

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging 187-126-64-254.user.veloxzone.com.br [187.126.64.254] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 187.126.64.254:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Pinging 196.32.198.35.bc.googleusercontent.com [35.198.32.196] with 32 bytes of data:
Reply from 35.198.32.196: bytes=32 time=133ms TTL=125
Reply from 35.198.32.196: bytes=32 time=132ms TTL=125
Reply from 35.198.32.196: bytes=32 time=132ms TTL=125
Reply from 35.198.32.196: bytes=32 time=132ms TTL=125

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

Pinging 201-9-23-1.user.veloxzone.com.br [201.9.23.1] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 201.9.23.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging 186-194-237-216.cabonnet.com.br [186.194.237.216] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 186.194.237.216:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Pinging 186-231-40-50.ded.intelignet.com.br [186.231.40.50] with 32 bytes of data:
Reply from 186.231.40.50: bytes=32 time=147ms TTL=243
Reply from 186.231.40.50: bytes=32 time=147ms TTL=243
Reply from 186.231.40.50: bytes=32 time=148ms TTL=243
Reply from 186.231.40.50: bytes=32 time=153ms TTL=243

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

Pinging ddos-protected-by.heavyhost.net [172.106.11.129] with 32 bytes of data:
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255

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

Pinging ddos-protected-by.heavyhost.net [172.106.11.129] with 32 bytes of data:
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255
Reply from 172.106.11.129: bytes=32 time<1ms TTL=255

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

Pinging Google.com.br [172.217.7.131] with 32 bytes of data:
Reply from 172.217.7.131: bytes=32 time=1ms TTL=55
Reply from 172.217.7.131: bytes=32 time<1ms TTL=55
Reply from 172.217.7.131: bytes=32 time=1ms TTL=55
Reply from 172.217.7.131: bytes=32 time<1ms TTL=55

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

Pinging 170-238-101-22.infonetpe.com.br [170.238.101.22] with 32 bytes of data:
Reply from 170.238.101.22: bytes=32 time=90ms TTL=50
Reply from 170.238.101.22: bytes=32 time=90ms TTL=50
Reply from 170.238.101.22: bytes=32 time=90ms TTL=50
Reply from 170.238.101.22: bytes=32 time=90ms TTL=50

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

Pinging WIN-ETGQQT9LA10 [172.106.11.155] with 32 bytes of data:
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128
Reply from 172.106.11.155: bytes=32 time<1ms TTL=128

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

Pinging 201-3-63-40.bsace704.dsl.brasiltelecom.net.br [201.3.63.40] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 201.3.63.40:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Pinging 201-3-63-40.bsace704.dsl.brasiltelecom.net.br [201.3.63.40] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 201.3.63.40:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
-------------------------------------------------------------------

Tracing route to 179-197-40-100.user.veloxzone.com.br [179.197.40.100]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  ddos-protected-by.heavyhost.net [172.106.11.129]
 2    <1 ms    <1 ms    <1 ms  dist-13873-r1.as40676.net [172.106.5.65]
 3    <1 ms    <1 ms    <1 ms  rest-b1-link.telia.net [213.248.89.74]
 4     7 ms     7 ms     7 ms  ash-bb4-link.telia.net [62.115.121.217]
 5     7 ms     7 ms     7 ms  nyk-bb4-link.telia.net [62.115.136.200]
 6     6 ms     6 ms     6 ms  nyk-b5-link.telia.net [80.91.254.14]
 7   100 ms    21 ms     6 ms  ldtelecom-ic-315503-nyk-b5.c.telia.net [80.239.195.158]
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10   118 ms   118 ms   118 ms  100.122.18.116
11   122 ms   123 ms     *     100.122.48.40
12   138 ms   136 ms   136 ms  200164013090.user.veloxzone.com.br [200.164.13.90]
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
-- Traceroute timed out --
-------------------------------------------------------------------

Tracing route to 179-197-40-100.user.veloxzone.com.br [179.197.40.100]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  ddos-protected-by.heavyhost.net [172.106.11.129]
 2    <1 ms    <1 ms    <1 ms  dist-13873-r1.as40676.net [172.106.5.65]
 3    <1 ms    <1 ms    <1 ms  rest-b1-link.telia.net [213.248.89.74]
 4     7 ms     7 ms     7 ms  ash-bb4-link.telia.net [62.115.121.217]
 5     7 ms     7 ms     7 ms  nyk-bb4-link.telia.net [62.115.136.200]
 6     6 ms     6 ms     6 ms  nyk-b5-link.telia.net [80.91.254.14]
 7     6 ms     6 ms     6 ms  ldtelecom-ic-315503-nyk-b5.c.telia.net [80.239.195.158]
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10   119 ms   118 ms   118 ms  100.122.18.116
11   121 ms     *      120 ms  100.122.48.40
12   136 ms     *      136 ms  200164013090.user.veloxzone.com.br [200.164.13.90]
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
-- Traceroute timed out --
-------------------------------------------------------------------

Tracing route to 179-197-40-1.user.veloxzone.com.br [179.197.40.1]
over a maximum of 30 hops:

 1    <1 ms    <1 ms    <1 ms  ddos-protected-by.heavyhost.net [172.106.11.129]
 2    <1 ms    <1 ms    <1 ms  dist-13873-r1.as40676.net [172.106.5.65]
 3    <1 ms    <1 ms    <1 ms  rest-b1-link.telia.net [213.248.89.74]
 4     7 ms     7 ms     7 ms  ash-bb4-link.telia.net [62.115.121.217]
 5     7 ms     7 ms     7 ms  nyk-bb4-link.telia.net [62.115.136.200]
 6     6 ms     6 ms     6 ms  nyk-b5-link.telia.net [80.91.254.14]
 7     6 ms     6 ms     6 ms  ldtelecom-ic-315503-nyk-b5.c.telia.net [80.239.195.158]
 8     *