| Posted by JodoHost, 10-18-2004, 11:13 AM | |
has anyone been experiencing erratic issues connecting to networks within the US, especially those served by Level3?
we've had alot of erratic network issues this morning and we are trying to sort out whats been happening
|
| Posted by ElrondTwg, 10-18-2004, 11:20 AM | |
Seems like we've been down at ThePlanet for over an hour now. The server can't trace past so-1-2-0.bbr2.Dallas1.Level3.net. Anyone else having problems like this?
|
| Posted by Jchristophe, 10-18-2004, 11:26 AM | |
Hello,
Since this morning there are a tons of issue with level3. Someone has some news. I post here some traceroute.
From France
2,80.10.181.164,50ms,GE5-588.ncidf304.NeuillySurMarne.francetelecom.net,----
3,193.252.99.81,53ms,pos6-0.nrsta304.Paris.francetelecom.net,----
4,193.251.126.50,68ms,None,----
5,193.251.129.61,58ms,P9-0.PASCR1.Pastourelle.opentransit.net,----
6,193.251.240.214,57ms,Level3.GW.opentransit.net,----
7,212.73.240.65,53ms,ae-0-15.mp1.Paris1.Level3.net,----
8,212.187.128.46,60ms,ae-1-0.bbr1.London2.Level3.net,----
9,4.68.128.102,129ms,as-0-0.bbr2.Washington1.Level3.net,----
10,209.247.9.81,181ms,so-2-0-0.mp2.Denver1.Level3.net,----
11,----,Timeout,n/a,----
12,4.68.124.10,183ms,so-6-0-0.gar1.Tampa1.Level3.net,----
13,----,Timeout,n/a,----
14,----,Timeout,n/a,----
From New york
traceroute to sagonet.com (66.118.128.5), 30 hops max, 38 byte packets
1 66.70.82.1 (66.70.82.1) 0.519 ms 0.428 ms 0.374 ms
2 border4.ewr.datapipe.net (64.106.128.11) 0.610 ms 0.687 ms 0.627 ms
3 datapipe.yipes.com (209.120.220.1) 0.800 ms 0.642 ms 1.303 ms
4 nwrknj1wce1-gige7-0.wcg.net (64.200.60.29) 0.613 ms 0.536 ms 0.513 ms
5 hrndva1wcx3-pos12-1-oc48.wcg.net (64.200.240.149) 6.773 ms 6.880 ms 6.877 ms
6 drvlga1wcx2-pos3-0-oc192.wcg.net (64.200.210.237) 17.654 ms 17.678 ms 17.683 ms
7 hstntx1wcx2-pos11-0.wcg.net (64.200.240.77) 30.855 ms 30.718 ms 30.559 ms
8 hstntx1wcx3-pos9-0-oc48.wcg.net (65.77.93.202) 30.692 ms 30.677 ms 30.639 ms
9 dllstx1wcx3-pos14-0-oc192.wcg.net (64.200.210.65) 35.445 ms 72.429 ms 35.461 ms
10 dllstx9lcx1-pos9-0.wcg.net (64.200.232.210) 35.437 ms 35.416 ms 35.440 ms
11 so-2-2-0.edge1.Dallas1.Level3.net (4.68.127.21) 36.696 ms 36.822 ms 36.822 ms
12 * so-1-2-0.bbr1.Dallas1.Level3.net (209.244.15.161) 35.713 ms 35.743 ms
13 as-0-0.mp1.Tampa1.Level3.net (209.247.11.197) 48.200 ms 48.013 ms 48.189 ms
14 so-6-0-0.gar1.Tampa1.Level3.net (4.68.124.10) 48.137 ms 48.418 ms 48.172 ms
15 4.79.172.2 (4.79.172.2) 48.367 ms 48.389 ms *
16 gi0-49.ds03.tpa.sagonet.net (65.110.32.10) 49.862 ms 48.497 ms 48.482 ms
17 * * *
From new york
1 66.70.82.1 (66.70.82.1) 2.462 ms 221.456 ms 1.499 ms
2 core2.ewr.datapipe.net (64.106.128.18) 0.571 ms 0.620 ms 0.610 ms
3 GigabitEthernet5-0.GW1.EWR17.ALTER.NET (157.130.254.161) 0.548 ms 0.367 ms 0.344 ms
4 0.so-5-0-0.CL2.EWR6.ALTER.NET (152.63.28.89) 0.591 ms 0.703 ms 0.510 ms
5 0.so-3-1-0.XL2.NYC4.ALTER.NET (152.63.21.17) 3.056 ms 3.138 ms 3.190 ms
6 0.so-7-0-0.BR1.NYC4.ALTER.NET (152.63.21.81) 2.316 ms 2.354 ms 2.320 ms
7 so-0-0-0.gar4.NewYork1.Level3.net (209.244.160.181) 2.671 ms 2.553 ms 2.482 ms
8 ge-2-1-0.bbr2.NewYork1.Level3.net (64.159.4.149) 8.153 ms 3.757 ms 3.718 ms
9 ****
|
| Posted by DTMark, 10-18-2004, 11:28 AM | |
We've had one Customer report a problem accessing their website (port 80) but not their webmail (same server, port 8383) or their POP/SMTP email.
From here, on a Pipex broadband connection, we can't get the BTOpenworld site to load consistently (was looking for service updates/information on behalf of Customer), we can't get one of the other sites we host to load on a Freeserve dial-up (though the reported faulty one does load) and so forth.
Problems seem to be randomised across different ISPs and sites.
|
| Posted by PhMatt, 10-18-2004, 11:30 AM | |
I hope this one makes it through, DB errors have not allowed me to post:
"Currently, customers that are connecting to us through Level(3) via New York, New York or Washington D.C. are experiencing complete loss of connectivity. At this time, we are contacting Level(3) to find out the status of the problem, as well as an ETR. We will keep you updated as we receive additional information. Thank you for your patience."
Thank you,
|
| Posted by cprompt, 10-18-2004, 11:37 AM | |
Yes, one or more of Level3's routers are screwed up
|
| Posted by Jchristophe, 10-18-2004, 11:42 AM | |
Matt,
Have your an idea why some IP's are reachable and other are not from New york?
eg: 66.118.182.74 works fine
1 66.70.82.1 (66.70.82.1) 0.592 ms 0.532 ms 0.407 ms
2 core2.ewr.datapipe.net (64.106.128.18) 0.721 ms 0.560 ms 0.569 ms
3 GigabitEthernet5-0.GW1.EWR17.ALTER.NET (157.130.254.161) 0.409 ms 0.509 ms 0.392 ms
4 0.so-5-0-0.CL2.EWR6.ALTER.NET (152.63.28.89) 0.585 ms 0.638 ms 0.876 ms
5 0.so-1-2-0.XL2.NYC4.ALTER.NET (152.63.21.13) 2.443 ms 2.446 ms 2.381 ms
6 0.so-7-0-0.BR1.NYC4.ALTER.NET (152.63.21.81) 1.710 ms 1.778 ms 1.773 ms
7 so-0-0-0.gar4.NewYork1.Level3.net (209.244.160.181) 2.432 ms 1.729 ms 1.686 ms
8 ge-2-1-0.bbr2.NewYork1.Level3.net (64.159.4.149) 3.148 ms 3.210 ms 3.110 ms
9 so-2-0-0.mp1.Tampa1.Level3.net (209.247.11.201) 36.786 ms 37.118 ms 36.882 ms
10 so-6-0-0.gar1.Tampa1.Level3.net (4.68.124.10) 37.607 ms 37.598 ms 37.580 ms
11 4.79.172.2 (4.79.172.2) 37.687 ms 37.558 ms 37.759 ms
12 gi0-1.ds02.tpa.sagonet.net (65.110.32.9) 38.035 ms 38.130 ms 39.873 ms
13 66.118.182.74 (66.118.182.74) 38.047 ms 38.151 ms 38.168 ms
but 66.118.182.122 don't work.
1 66.70.82.1 (66.70.82.1) 0.561 ms 0.440 ms 0.449 ms
2 core2.ewr.datapipe.net (64.106.128.18) 0.555 ms 0.578 ms 0.545 ms
3 GigabitEthernet5-0.GW1.EWR17.ALTER.NET (157.130.254.161) 0.468 ms 0.488 ms 0.422 ms
4 0.so-5-0-0.CL2.EWR6.ALTER.NET (152.63.28.89) 0.585 ms 0.532 ms 0.523 ms
5 0.so-3-1-0.XL2.NYC4.ALTER.NET (152.63.21.17) 3.190 ms 3.174 ms 3.077 ms
6 0.so-7-0-0.BR1.NYC4.ALTER.NET (152.63.21.81) 2.439 ms 2.517 ms 2.345 ms
7 so-0-0-0.gar4.NewYork1.Level3.net (209.244.160.181) 2.376 ms 2.401 ms 2.379 ms
8 ge-2-1-0.bbr2.NewYork1.Level3.net (64.159.4.149) 3.719 ms 14.408 ms 3.706 ms
9 * * *
10 * * *
11 * * *
|
| Posted by Russ Foster, 10-18-2004, 11:44 AM | |
I'm seeing trouble over in San Diego...
Rus
|
| Posted by JodoHost, 10-18-2004, 11:46 AM | |
We are getting a continuous stream of tickets with customers reporting accessibility problems. Our VoIP services are intermittent as well.
|
| Posted by Odd Fact, 10-18-2004, 11:49 AM | |
I have seen problems most of the morning from the Dallas area as well.
|
| Posted by PhMatt, 10-18-2004, 11:50 AM | |
I've found the same thing myself, but no, as of now, I do not have the answers on that one.
|
| Posted by Reseller-Center, 10-18-2004, 11:58 AM | |
Same Here... no answers yet..
|
| Posted by Jchristophe, 10-18-2004, 12:10 PM | |
I think it works fine now.
|
| Posted by PhMatt, 10-18-2004, 12:10 PM | |
I'm pinging as well.
|
| Posted by cprompt, 10-18-2004, 12:32 PM | |
Level 3 seem to have rerouted back via New York from London and it works fine now.
/Me crosses fingers
|
| Posted by ardent, 10-18-2004, 12:43 PM | |
priceless
1. sc-mcl1-smv8-1000M.servint.net 0% 14 14 0 0 0 0
2. p2-0.br1.iad2.servint.net 0% 14 14 1 1 2 9
3. ge3-0.cr02.vna01.pccwbtn.net 0% 14 14 2 1 2 7
4. bpr1-so-7-3-0.VirginiaEquinix.savvis.net 0% 14 14 7 2 3 9
5. cpr2-pos-4-0.VirginiaEquinix.savvis.net 0% 14 14 2 2 3 7
6. ge-2-1-1.edge1.Washington1.Level3.net 0% 14 14 2 2 3 7
7. so-2-1-0.bbr2.Washington1.Level3.net 15% 12 14 3 2 4 9
8. so-2-0-0.mp2.Denver1.Level3.net 0% 14 14 46 46 46 48
9. so-6-0.hsa2.Denver1.Level3.net 0% 14 14 46 46 47 50
10. se3-0.public2.Broomfield1.Level3.net 0% 14 14 48 47 48 53
11. www.Level3.com 0% 13 13 49 47 48 51
|
| Posted by Blue Note Web, 10-18-2004, 01:50 PM | |
Now this is amusing...I called my hosting company this morning about this...they told me that they had no problem accessing my server on any port and that their associates in other parts of the country/world were also accessing my sites easily. They suggested I call my DSL provider.
After 30 minutes on hold with Verizon (we are currently experiencing high volume...) I dealt with a script monkey who told me to reset my computer, router and DSL modem despite the fact that I had done that during the 30 minutes I spent on hold. "All of our tests show green across the board!" he told me. While I was asking him increasingly technical questions to convince him to send me to someone with some knowledge, my connection magically came back to life. I told him it was working again and he said "See! Resetting your computer did the trick!" I hate it when non-technical people work in tech support...
|
| Posted by Chrysalis, 10-18-2004, 02:52 PM | |
yeah I couldnt access this forum, sagonet and also for brief periods s4y also dropped. MSN messenger also kicked me off.
|
| Posted by retep, 10-18-2004, 07:03 PM | |
Apparently Level3 lost two core routers. And about 8 hours before that they had a mishap during maintenance on a fiber circuit in the dallas area. Not a good night.
Was anyone able to find a network status page on the Level3.net site? I wasn't.
|
| Posted by whatevah, 10-18-2004, 10:00 PM | |
my Verizon seems to have connected in with Level3 again. *finally*
|
| Posted by cprompt, 10-19-2004, 04:31 AM | |
It is just sales junk as far as I can see. I guess if you buy transit from them, you have access to that information, but for us mere users, you just have to cross your fingers and wait it out
At least it is sorted now.
|
|
 Add to Favourites
 Print this Article
|
