Hiitz.

8:42 e os DC ainda não pararam Microsoft Windows [Version 6.2.9200]© 2012 Microsoft Corporation. All rights reserved. ping -n 20 200.229.49.41 Pinging 200.229.49.41 with 32 bytes of data:Reply from 200.229.49.41: bytes=32 time=42ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=35ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=35ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=35ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=35ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54Reply from 200.229.49.41: bytes=32 time=35ms TTL=54Reply from 200.229.49.41: bytes=32 time=37ms TTL=54Reply from 200.229.49.41: bytes=32 time=37ms TTL=54Reply from 200.229.49.41: bytes=32 time=36ms TTL=54 Ping statistics for 200.229.49.41: Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 35ms, Maximum = 42ms, Average = 36ms tracert 200.229.49.41 Tracing route to 200.229.49.41 over a maximum of 30 hops 1 3 ms 1 ms 1 ms 192.168.25.1 2 7 ms 7 ms 8 ms gvt-l0.b8.vta.gvt.net.br [187.115.224.1] 3 7 ms 7 ms 7 ms corporativo.host.gvt.net.br [189.115.192.2] 4 26 ms 22 ms 21 ms 187.115.216.201.static.host.gvt.net.br [187.115.216.201] 5 45 ms 46 ms 47 ms 189.59.243.117.static.host.gvt.net.br [189.59.243.117] 6 43 ms 45 ms 44 ms 187.115.213.110.static.host.gvt.net.br [187.115.213.110] 7 35 ms 34 ms 36 ms 200.136.34.27 8 32 ms 31 ms 32 ms h200-215-189-140.ipb.diveo.net.br [200.215.189.140] 9 35 ms 34 ms 34 ms 200.229.49.41 10 35 ms 34 ms 34 ms 200.229.49.41 Trace complete. tracert 200.229.49.41 Tracing route to 200.229.49.41 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.25.1 2 7 ms 8 ms 7 ms gvt-l0.b8.vta.gvt.net.br [187.115.224.1] 3 7 ms 8 ms 7 ms corporativo.host.gvt.net.br [189.115.192.2] 4 20 ms 22 ms 21 ms 187.115.216.201.static.host.gvt.net.br [187.115.216.201] 5 40 ms 44 ms 45 ms 189.59.243.117.static.host.gvt.net.br [189.59.243.117] 6 41 ms 46 ms 43 ms 187.115.213.110.static.host.gvt.net.br [187.115.213.110] 7 35 ms 34 ms 34 ms 200.136.34.27 8 33 ms 32 ms 32 ms h200-215-189-140.ipb.diveo.net.br [200.215.189.140] 9 * * * Request timed out. 10 35 ms 34 ms 34 ms 200.229.49.41 Trace complete. C:\Users\Hitzc>

semana passada eu tive o msm problema, acho que durou uns 4 dias, mais não lembro de ter visto gente reclamando.

Dados Para Comparação GVT-Espirito Santo Microsoft Windows [Version 6.2.9200]© 2012 Microsoft Corporation. All rights reserved. ping -n 20 200.229.49.41 Pinging 200.229.49.41 with 32 bytes of data:Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Reply from 200.229.49.41: bytes=32 time=31ms TTL=55Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Request timed out.Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=29ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=30ms TTL=55Reply from 200.229.49.41: bytes=32 time=46ms TTL=55Request timed out. Ping statistics for 200.229.49.41: Packets: Sent = 20, Received = 18, Lost = 2 (10% loss),Approximate round trip times in milli-seconds: Minimum = 29ms, Maximum = 46ms, Average = 30ms tracert 200.229.49.41 Tracing route to 200.229.49.41 over a maximum of 30 hops 1 2 ms 1 ms 1 ms 192.168.25.1 2 8 ms 8 ms 9 ms gvt-l0.b8.vta.gvt.net.br [187.115.224.1] 3 10 ms * 9 ms corporativo.host.gvt.net.br [189.115.192.1] 4 22 ms 22 ms 23 ms 187.115.217.209.static.host.gvt.net.br [187.115.217.209] 5 34 ms 34 ms 34 ms 189.59.243.113.static.host.gvt.net.br [189.59.243.113] 6 44 ms 34 ms 34 ms gvt-te-0-0-0-9-rt02.spo.gvt.net.br [187.115.214.202] 7 30 ms 30 ms 31 ms 200.136.34.27 8 32 ms 30 ms 29 ms h200-215-189-140.ipb.diveo.net.br [200.215.189.140] 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * 28 ms 28 ms 200.229.49.41 Trace complete.

Tendo o mesmo problema aqui, Duas contas em 2 PC diferente, DC na mesma hora, outra pessoa no TS tb ta tendo dc na exata mesma hora que eu.Todos usuarios da GVT.vs tb?