Is it just me or is DU lagging and cutting out right now.

[maveric]

Pages wont load all the way and it froze up on me 3 times allready.

[Vektor]

1. Same here...

Traffic might be real high right now.

[Reverend_Smitty]

2. working fine for me

maybe it's a problem with your ISP

[FreedomAngel82]

4. It comes and goes with me

I've been having trouble with my internet connection all evening. :shrug: Everything seems to be okay with me.

[maveric]

10. Nope. Its only DU doing it. Every other site I tried loaded fine.

[hippiepunk]

3. Its workin for me.

Is it just this site?

[yvr girl]

5. It's fine for me, but earlier today it was terrible.

[Fridays Child]

6. Comcast took a nationwide dump this evening, something about...

...a DNS server. If you're on Comcast, you've probably noticed problems.

[demnan]

8. At such high prices

they shouldn't be allowed such a big shit.

[Fridays Child]

13. I hear that. If customers call to complain, though...

...Comcast is pretty good about giving credit in half-day and whole-day increments, depending on the amount of time they were down.

[Up2Late]

12. My Comcast Cable Modem was out from about 7:00pm till 11:00pm

I got most of the local web back about an hour before that.

When I called about it, the recording said that the nation wide network had gone down, and it would be spotty as it recovered.

[Webster Green]

7. I think its the internets in general....

I was having trouble getting to any sites. I called ComCast and was told that there were nationwide problems with the internet.

I don't know if its just ComCast, or wider spread.

[eaglenetsupport]

9. This isn't a comcast issue per-say, it's

the backbone flowing through a router at NETSRV about thirteen hops away from me. This should effect any ISP that's using NETSRV as a bandwidth provider or any that are handing off there packets through NETSRV routers. Here is a trace route that will show the broken router. This is ridiculous that it has gone down this long. When a router goes down in the backbone (just means large bandwidth haulers well down the line from your ISP) bells and whistles go off all over the place. For comcast to tell people that it's a DNS problem is their tech support folks needing a different profession. Phone support folks don't understand this stuff or they wouldn't be stuck answering tech support phones for 10 Bucks an hour. It's a five second procedure to diagnose networking problems. Somebody at NETSRV doesn't want to call someone in and thinks that it is best to wait till morning, probably a time and a half excuse.

milliseconds per packet are smooth and consistent times for each of the three packets sent in the test, indicating not a data collision problem which is usually what you would see when a problem is actually an Internet wide problem.

# traceroute comcast.com
traceroute to comcast.com (164.109.28.3), 30 hops max, 38 byte packets
1 router (206.168.38.62) 0.557 ms 0.364 ms 0.319 ms
2 165.236.232.13 (165.236.232.13) 1.746 ms 1.582 ms 1.631 ms
3 170.147.161.94 (170.147.161.94) 1.799 ms 1.761 ms 1.794 ms
4 dvr-edge-09.inet.qwest.net (65.121.56.105) 1.632 ms 1.721 ms 1.634 ms
5 dia-core-01.inet.qwest.net (205.171.10.37) 1.957 ms 1.736 ms 1.797 ms
6 dal-core-02.inet.qwest.net (205.171.8.141) 23.585 ms 23.351 ms 23.248 ms
7 dap-brdr-01.inet.qwest.net (205.171.225.53) 23.569 ms 23.355 ms 24.593 ms
8 POS1-1.BR2.LAX9.ALTER.NET (204.255.168.37) 34.385 ms 34.369 ms 33.857 ms
9 0.so-3-3-0.XL2.DFW9.ALTER.NET (152.63.103.77) 33.396 ms 35.971 ms 36.002 ms
10 0.so-6-0-0.XL2.DCA6.ALTER.NET (152.63.38.74) 55.019 ms 58.945 ms 54.799 ms
11 0.so-7-0-0.GW6.DCA6.ALTER.NET (152.63.41.225) 54.532 ms 58.246 ms 55.683 ms
12 digex-gw.customer.alter.net (157.130.214.102) 58.180 ms 56.441 ms 59.127 ms
13 vlan39.dca2a-fdisa-sw1-msfc1.netsrv.digex.net (164.109.3.149) 57.527 ms 59.903 ms 61.
751 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

[demnan]

11. Sounds like they could use you over there.

[eaglenetsupport]

18. I can assure you

they got better people then me over there. I think they don't want to spend the over time to call them in. I don't know what else would keep them from replacing the errant machine other than it's night time. Even little guys like me got back up machines and routers, pre-configured, ready to go online at a moments notice. These are big guys, no pathetic excuses please, I say.

[indigo]

14. Well, it was a DNS issue here

I have Comcast as well as another network for which I supply my own dns server (BIND/Solaris). When Comcast went down, I used my DNS server instead of theirs and everything was fine.

Now, an appropriate test to look for a router down between you and a Comcast dns server would involve *comcast.net*

[eaglenetsupport]

15. Ahh... a .net and not .com in any event

I still see a router puking at hop #17:

I suspect your DNS server used another route to get to the same place and may have gone around the problem router. I don't understand why subsequent routes, after failure, wouldn't blaze a new trail around the problem machine and continue to use the same failed route???


# traceroute comcast.net
traceroute: Warning: comcast.net has multiple addresses; using 63.240.76.72
traceroute to comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 router (206.168.38.62) 0.554 ms 0.356 ms 0.362 ms
2 165.236.232.13 (165.236.232.13) 1.585 ms 1.589 ms 1.512 ms
3 170.147.161.94 (170.147.161.94) 1.751 ms 1.718 ms 1.673 ms
4 dvr-edge-09.inet.qwest.net (65.121.56.105) 1.633 ms 1.682 ms 1.794 ms
5 dia-core-01.inet.qwest.net (205.171.10.37) 1.795 ms 8.779 ms 1.793 ms
6 dal-core-02.inet.qwest.net (205.171.8.141) 23.134 ms 23.349 ms 23.122 ms
7 dap-brdr-01.inet.qwest.net (205.171.225.53) 24.840 ms 38.421 ms 208.714 ms
8 qwest-gw.dlstx.ip.att.net (192.205.32.145) 53.065 ms 112.602 ms 75.451 ms
9 tbr2-p014001.dlstx.ip.att.net (12.123.17.86) 27.342 ms 26.267 ms 25.500 ms
10 tbr2-cl6.sl9mo.ip.att.net (12.122.10.89) 39.508 ms 40.673 ms 40.405 ms
11 tbr2-cl7.cgcil.ip.att.net (12.122.10.45) 35.861 ms 34.300 ms 35.822 ms
12 tbr1-cl2.cgcil.ip.att.net (12.122.9.133) 36.022 ms 35.103 ms 34.389 ms
13 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 54.868 ms 55.871 ms 54.269 ms
14 gbr2-p10.n54ny.ip.att.net (12.122.11.6) 53.118 ms 52.930 ms 52.854 ms
15 gar1-p370.n54ny.ip.att.net (12.123.1.133) 52.936 ms 52.800 ms 54.409 ms
16 mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162) 53.340 ms 53.710 ms 53.555 ms
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *


also how about this trace using IP and not domain name, same thing. That doesn't look like DNS to me.

# traceroute 63.240.76.72
traceroute to 63.240.76.72 (63.240.76.72), 30 hops max, 38 byte packets
1 router (206.168.38.62) 0.554 ms 0.407 ms 0.310 ms
2 165.236.232.13 (165.236.232.13) 1.617 ms 1.632 ms 1.559 ms
3 170.147.161.94 (170.147.161.94) 1.787 ms 1.752 ms 10.023 ms
4 dvr-edge-09.inet.qwest.net (65.121.56.105) 1.895 ms 1.708 ms 1.623 ms
5 dia-core-01.inet.qwest.net (205.171.10.37) 1.784 ms 1.722 ms 2.119 ms
6 dal-core-02.inet.qwest.net (205.171.8.141) 23.122 ms 23.144 ms 23.087 ms
7 dap-brdr-01.inet.qwest.net (205.171.225.53) 207.276 ms 42.341 ms 202.859 ms
8 qwest-gw.dlstx.ip.att.net (192.205.32.145) 71.904 ms 162.934 ms 31.277 ms
9 tbr2-p014001.dlstx.ip.att.net (12.123.17.86) 27.017 ms 25.577 ms 49.971 ms
10 tbr2-cl6.sl9mo.ip.att.net (12.122.10.89) 57.909 ms 39.245 ms 40.312 ms
11 tbr2-cl7.cgcil.ip.att.net (12.122.10.45) 34.715 ms 34.778 ms 35.899 ms
12 tbr1-cl2.cgcil.ip.att.net (12.122.9.133) 37.124 ms 69.132 ms 34.838 ms
13 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 54.752 ms 58.149 ms 53.464 ms
14 gbr2-p10.n54ny.ip.att.net (12.122.11.6) 52.987 ms 53.568 ms 52.974 ms
15 gar1-p370.n54ny.ip.att.net (12.123.1.133) 53.048 ms 53.070 ms 53.337 ms
16 mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162) 54.748 ms 53.646 ms 55.102 ms
17 * * *
18 * *

[RBHam]

16. you have a virus

spring cleaning time

[eaglenetsupport]

17. This is not a virus issue

Don't anybody go to "fixing" anything. This problem is not on your machines.