dslreports logo
 
    All Forums Hot Topics Gallery
spc
uniqs
30
TexasRebel
join:2011-05-29
Edgewood, TX

TexasRebel to dbirdman

Member

to dbirdman

Re: Gen4/Changes Coming After Jan 1

no, it's definitely a bandwidth issue or a software issue on the ground. here's a tracert I did earlier this morning around 6:30am.

I understand about some routers not responding to iCMP pings. But these packet losses are happening during peak times, which it seems for HNG4 it's 9AM-2AM, a 16 hour window.

much different outcome at around 6:30AM.

C:\Windows\system32>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms DD-WRT [192.168.1.251]
2 1 ms 1 ms 1 ms 100.75.0.201
3 650 ms 1539 ms 689 ms dpc6935160130.direcpc.com [69.35.160.130]
4 613 ms 649 ms 618 ms dpc6935164017.direcpc.com [69.35.164.17]
5 661 ms 649 ms 649 ms tuk-edge-11.inet.qwest.net [63.235.80.137]
6 1094 ms 770 ms 748 ms sea-edge-12.inet.qwest.net [67.14.41.62]
7 622 ms 679 ms 649 ms 67.131.14.218
8 701 ms 661 ms 659 ms 66.249.94.214
9 1696 ms 859 ms 639 ms 66.249.94.197
10 1288 ms 629 ms 689 ms 216.239.46.200
11 619 ms 644 ms 654 ms 216.239.48.165
12 * * * Request timed out.
13 655 ms 659 ms 639 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

dbirdman
MVM
join:2003-07-07
usa

dbirdman

MVM

OK, since the missing hops are mostly outside the Hughes network it probably just is a true timeout. Have your tried opening up the tracert timeout window?