Re: Operational: Wiltel Peering with MCI problems around D.C
Would this be affecting MIT, too? I've been noticing some very odd connectivity issues between here (Austin) and the CSAIL at MIT.... - ferg -- Rich Emmings <rich@nic.umass.edu> wrote: Anyone else (Wiltel customers especially) running into an operational issue around D.C. with partial connectivity It would seem MCI and Wiltel around D.C. have a 'informal' peering relationship and it's been errored right now for about 39 hours with a half-duplex route announcement. This has been effecting us with some loss of connectivity that's not there when we test same sites from other ISP clouds. Since it's informal, the help desk system at one or both ands may be having problem entering a ticket w/o an account number for the circuit. The usual channels are not producting results, and we're starting to get engineers on the lower end of the evoluationary food chain and finger pointing between wgc & mci that's not helping. Tried a pch, haven't heard yet. ... 5 nycmny2wcx2-pos0-0-oc192.wcg.net (64.200.68.157) 5.786 ms 6.510 ms 6.114 ms 6 hrndva1wcx2-pos1-0-oc192.wcg.net (64.200.210.178) 12.029 ms 11.883 ms 11.582 ms 7 washdc5lcx1-pos5-0.wcg.net (64.200.240.194) 12.840 ms 12.559 ms 12.887 ms ...traffic dies.... -- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg@netzero.net or fergdawg@sbcglobal.net ferg's tech blog: http://fergdawg.blogspot.com/
On Thu, 18 Aug 2005, Fergie (Paul Ferguson) wrote:
Would this be affecting MIT, too?
I've been noticing some very odd connectivity issues between here (Austin) and the CSAIL at MIT....
I sent rick a note earlier ( 3 mins earlier) but... 3 0.so-5-3-3.XL2.DCA6.ALTER.NET (152.63.36.178) 34.345 ms 96.145 ms 6.727 ms 4 0.so-6-0-0.XL2.IAD8.ALTER.NET (152.63.38.141) 23.129 ms 9.528 ms 9.173 ms 5 POS7-0.GW4.IAD8.ALTER.NET (152.63.41.33) 9.033 ms 8.954 ms 8.963 ms 6 wcgGigE-gw2.customer.alter.net (157.130.30.246) 9.289 ms 8.973 ms 8.927 ms 7 hrndva1wcx2-pos6-0.wcg.net (64.200.240.193) 10.315 ms 9.967 ms 9.945 ms 8 nycmny2wcx2-pos1-0-oc192.wcg.net (64.200.210.177) 15.496 ms 15.398 ms 15.807 ms 9 nycmny2wcx3-pos11-3.wcg.net (64.200.68.98) 16.146 ms 16.202 ms 16.210 ms 10 spfdma1wce1-pos4-0.wcg.net (64.200.240.246) 20.835 ms 19.919 ms 30.491 ms11 65.77.95.162 (65.77.95.162) 21.480 ms 21.228 ms 21.296 ms 12 lgrc-rt-106-8.gw.umass.edu (128.119.2.193) 21.315 ms 21.032 ms 21.074 ms 13 troy.oit.umass.edu (128.119.175.37) 22.137 ms 21.580 ms 21.235 ms traceroute to his MX host... if he replies I'd be happy to help, if there ARE MIT issues as well, I'd offer to take a peek at that as well, provided someone from MIT has some time to troubleshoot and details of the 'problem'.
- ferg
-- Rich Emmings <rich@nic.umass.edu> wrote:
Anyone else (Wiltel customers especially) running into an operational issue around D.C. with partial connectivity
It would seem MCI and Wiltel around D.C. have a 'informal' peering relationship and it's been errored right now for about 39 hours with a half-duplex route announcement. This has been effecting us with some loss of connectivity that's not there when we test same sites from other ISP clouds. Since it's informal, the help desk system at one or both ands may be having problem entering a ticket w/o an account number for the circuit.
The usual channels are not producting results, and we're starting to get engineers on the lower end of the evoluationary food chain and finger pointing between wgc & mci that's not helping. Tried a pch, haven't heard yet.
... 5 nycmny2wcx2-pos0-0-oc192.wcg.net (64.200.68.157) 5.786 ms 6.510 ms 6.114 ms 6 hrndva1wcx2-pos1-0-oc192.wcg.net (64.200.210.178) 12.029 ms 11.883 ms 11.582 ms 7 washdc5lcx1-pos5-0.wcg.net (64.200.240.194) 12.840 ms 12.559 ms 12.887 ms ...traffic dies....
-- "Fergie", a.k.a. Paul Ferguson Engineering Architecture for the Internet fergdawg@netzero.net or fergdawg@sbcglobal.net ferg's tech blog: http://fergdawg.blogspot.com/
participants (2)
-
Christopher L. Morrow -
Fergie (Paul Ferguson)