Gah.. I hate these kind of vague problems. I have multiple users complaining about "the internet is slow"; specifically to sites such as aol, cnn, amazon. Our support folks are also having trouble getting to postini's admin pages. Things are excruciatingly slow. I don't see any indications on router load, link utilization, bouncing routes, etc. that jump up as obvious problems. I tried using the lookingglass at algx.net, but I'm getting null responses for all requests (ping, traceroute and BGP). I'm not, however, seeing any issues with traceroute servers getting to us. Anybody know of anything broken anywhere? I don't think the problem is us, but if somebody would like to respond off-list with any oddities you may see with AS6423, and/or traceroutes to 206.103.37.166, I'd appreciate it. Thanks, Rick
From C&W in Houston
[root@filter root]# traceroute 206.103.37.166 traceroute to 206.103.37.166 (206.103.37.166), 30 hops max, 38 byte packets 1 GB-border1 (208.128.33.1) 0.433 ms 0.295 ms 0.229 ms 2 63-137-112-213 (63.137.112.213) 1.301 ms 1.166 ms 1.363 ms 3 bar2-serial4-0-0-8.Houston.cw.net (208.172.200.117) 98.757 ms 202.862 ms 203.653 ms 4 acr2.Houston.cw.net (208.172.194.62) 6.050 ms 4.564 ms 6.578 ms 5 agr3-loopback.Dallas.cw.net (208.172.130.103) 14.505 ms 10.107 ms 9.940 ms 6 acr1-loopback.Dallas.cw.net (208.172.130.61) 9.424 ms 9.314 ms 10.209 ms 7 52.ATM1-0.BR4.DFW9.ALTER.NET (204.255.168.81) 9.738 ms 21.496 ms 9.489 ms 8 138.at-2-0-0.XR1.DFW9.ALTER.NET (152.63.100.218) 9.443 ms 9.419 ms 13.375 ms 9 0.so-2-0-0.XL1.DFW9.ALTER.NET (152.63.101.253) 9.537 ms 14.405 ms 10.138 ms 10 0.so-0-0-0.TL1.DFW9.ALTER.NET (152.63.0.193) 13.668 ms 10.088 ms 9.624 ms 11 0.so-6-0-0.TL1.POR3.ALTER.NET (152.63.1.137) 61.879 ms 59.523 ms 58.675 ms 12 0.so-0-0-0.XL1.POR3.ALTER.NET (152.63.107.146) 59.082 ms 61.015 ms 61.778 ms 13 0.so-7-0-0.XR1.POR3.ALTER.NET (152.63.107.105) 64.647 ms 59.436 ms 61.815 ms 14 195.ATM7-0.GW3.POR2.ALTER.NET (152.63.105.161) 59.698 ms 59.655 ms 64.967 ms 15 easystreet-gw.customer.ALTER.NET (157.130.176.146) 62.390 ms 62.442 ms 65.129 ms 16 fe1-0-0.cis004cor01.bea1.easy.easystreet.com (209.162.220.35) 63.834 ms 62.496 ms 63.760 ms 17 * * * 18 206.103.37.166 (206.103.37.166) 64.942 ms 62.271 ms 63.900 ms ----- Original Message ----- From: "Rick Ernst" <ernst@easystreet.com> To: "NANOG" <nanog@merit.edu> Sent: Thursday, July 31, 2003 12:58 PM Subject: "The internet is slow"
Gah.. I hate these kind of vague problems.
I have multiple users complaining about "the internet is slow";
to sites such as aol, cnn, amazon. Our support folks are also having
specifically trouble
getting to postini's admin pages. Things are excruciatingly slow.
I don't see any indications on router load, link utilization, bouncing routes, etc. that jump up as obvious problems.
I tried using the lookingglass at algx.net, but I'm getting null responses for all requests (ping, traceroute and BGP). I'm not, however, seeing any issues with traceroute servers getting to us.
Anybody know of anything broken anywhere? I don't think the problem is us, but if somebody would like to respond off-list with any oddities you may see with AS6423, and/or traceroutes to 206.103.37.166, I'd appreciate it.
Thanks, Rick
On Thu, 31 Jul 2003, Rick Ernst wrote: :> :> :>Gah.. I hate these kind of vague problems. :> :>I have multiple users complaining about "the internet is slow"; specifically :>to sites such as aol, cnn, amazon. Our support folks are also having trouble :>getting to postini's admin pages. Things are excruciatingly slow. I got quite a few responses in a very short period of time. a) DNS resolve problems - already checked, looks OK b) traceroutes - Multiple reports of packet loss through UUNET, but some look fine. Ticket opened with UUNET. c) overloaded routers - CPU load looks fine. One report of high latency on one of our cour routers appears to be an anomaly. FWIW, mtr output was the most useful for me in this case. Thanks for the responses.
Packet loss within UUNET, apparently localized to the Portland (OR) area. I've turned down our peer with them and things are looking much better. Thanks for all the help/responses. Rick
On Thu, Jul 31, 2003 at 12:02:32PM -0700, Rick Ernst wrote:
Packet loss within UUNET, apparently localized to the Portland (OR) area. I've turned down our peer with them and things are looking much better.
Thanks for all the help/responses.
Shhhhhhh, next thing you know some reporter is going to be writing a story about how the NANOG mailing list fixed that darn "the internet is slow" problem everyone has been complaining about. -- Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
On Thu, Jul 31, 2003 at 10:58:37AM -0700, Rick Ernst wrote:
Gah.. I hate these kind of vague problems.
Here's a helpful script: http://cgi.cs.wisc.edu/scripts/ballard/bofhserver.pl --Adam
participants (6)
-
Adam McKenna -
neil＠DOMINO.ORG -
Richard A Steenbergen -
Rick Ernst -
Rick Ernst -
William Devine, II