Operational: Wiltel Peering with MCI problems around D.C

Mailman List Mirror (Read Only)
1

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....

2

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

Informal peering relationship with a half duplex route announcement? Is
this some really obscure way of saying someone is leaking routes? Trust
me, there is no such thing as an "informal" peering relationship with MCI.

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.

I don't think so. Whether it is a peer or a transit relationship, nothing
that big between those parties is informal, undocumented, or unticketable.
Besides, in this case, WCG buys transit from MCI:

GigabitEthernet5-0.GW4.IAD8.ALTER.NET (157.130.30.245)

Name: wcgGigE-gw2.customer.alter.net
Address: 157.130.30.246

I will take your word tht something is broken though, as the traceroute
from Washington DC to www.mci.com via http://lookingglass.wcg.net is:

Tracing the route to global.mci.com (164.109.35.20)

1 so-0-0-0.edge2.Washington1.Level3.net (4.68.127.25) [AS 3356] 0 msec 0 msec 0 msec
2 * * *
3 * * *
...

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.

Are you actually a customer of either one? If so, you ring them up and
stay on the phone until they address the problem. If not, take a stab at
it that WCG is the most interested party in getting it fixed, and try
nagging them some more. :slight_smile:

3

This issue is resolved.

Thanks to all who responsed on and off list.