I'm seeing a good path from LAX at this point. 5 tbr1-p013501.la2ca.ip.att.net (12.122.11.137) [AS 7018] 4 msec 0 msec 0 msec 6 tbr2-cl3.sffca.ip.att.net (12.122.10.25) [AS 7018] 12 msec 8 msec 12 msec 7 tbr1-cl1.st6wa.ip.att.net (12.122.12.114) [AS 7018] 32 msec 28 msec 32 msec You can always use the poor mans AT*T NOC, route-server.cerf.net -M< -- Martin Hannigan (c) 617-388-2663 VeriSign, Inc. (w) 703-948-7018 Network Engineer IV Operations & Infrastructure [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of > Pablo's Gmail > Sent: Wednesday, December 29, 2004 3:48 PM > To: John Fabello > Cc: [email protected] > Subject: Re: ATT issues > > > > thanks guys.. do any of you have a good link to keep taps on status of > this downage? > > > On Wed, 29 Dec 2004 12:33:00 -0800, John Fabello > <[EMAIL PROTECTED]> wrote: > > A fiber cable was cut > > > > ~John Fabello > > > > 425-456-8900 > > > > -----Original Message----- > > From: Pablo's Gmail [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, December 29, 2004 12:16 PM > > To: [email protected] > > Subject: ATT issues > > > > Is anyone else seeing major ATT issues in the pacific NW? > > > > Pablo > > >
