[outages] Fwd: Qwest/CenturyLink Issues

[Dino Panagiotopoulos]

It appears to have resolved now but we have not received an RFO from
CenturyLink. There was a global ticket opened with them.

Dino

On Sat, Jun 11, 2016 at 4:18 PM, trey valenta <t at trey.net> wrote:

> I too am experiencing the same issue. There's limited connectivity
> from that datacenter because some NTP packets are getting routed. But I
> haven't any more details and haven't gotten any expanation as to where
> things are broken.
>
> Trey
>
> On Sat, Jun 11, 2016 at 04:00:47PM -0400, Dino Panagiotopoulos via Outages
> wrote:
> > Hi Folks,
> >
> > We are experiencing a large outage right now with Qwest/CenturyLink which
> > they claim is isolated to one of our datacenters in the Bay Area but I
> have
> > a feeling that it is much larger than they are claiming. All of my
> > traceroutes to our datacenter fail once it enters the Centurylink/Qwest
> > network through any IX.
> >
> > Is anyone else seeing issues via CenturyLink/Qwest?
> >
> > traceroute
> > Protocol [ip]: ip
> > Target IP address: 66.35.XXX.XX
> > Source address:
> > Numeric display [n]: n
> > Timeout in seconds [3]: 1
> > Probe count [3]: 2
> > Minimum Time to Live [1]: 1
> > Maximum Time to Live [30]: 30
> > Port Number [33434]:
> > Loose, Strict, Record, Timestamp, Verbose[none]:
> > Type escape sequence to abort.
> > Tracing the route to 66.35.XXX.XX
> > VRF info: (vrf in name/id, vrf out name/id)
> >   1 ae8-40G.ar5.JFK1.gblx.net.ae8-40G.ar5.JFK1.gblx.net (67.17.92.226)
> > 76 msec 80 msec
> >   2 jfk-brdr-04.inet.qwest.net (63.235.40.57) 120 msec 112 msec
> >   3  *  *
> >   4  *  *
> >   5  *  *
> >   6  *  *
> >   7  *  *
> >   8  *  *
>
> > _______________________________________________
> > Outages mailing list
> > Outages at outages.org
> > https://puck.nether.net/mailman/listinfo/outages
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20160611/3bd3afb7/attachment.htm>