said by telcodad:Well, you're on AT&T's U-verse. Even though that report says AT&T is one of the ISPs affected, your part of it must not be then.
EDIT: OK, from »Cannot Access Website Through U-verse Connection , I see you were affected earlier today. I guess AT&T's routes have been fixed now.
Things may still be in a state of flux. Earlier today, both my Comcast and U-verse connections had changed from using Comcast's Ibone for a gateway to LiquidWeb, to using Level3. As of just a few minutes ago, both of the connections have now reverted to using the Comcast Ibone. However, I now see a Comcast Ibone hop that rDNS implies is from Los Angeles:
6 30 ms 30 ms 29 ms he-2-11-0-0-cr01.chicago.il.ibone.comcast.net [68.86.89.5]
7 29 ms 31 ms 31 ms be-10406-cr01.350ecermak.il.ibone.comcast.net [68.86.84.210]
8 29 ms 29 ms 29 ms he-1-11-0-0-cr01.losangeles.ca.ibone.comcast.net [68.86.86.10]
9 29 ms 29 ms 123 ms 50.242.150.126
10 39 ms 40 ms 40 ms lw-dc2-core3-te9-1.rtr.liquidweb.com [209.59.157.224]
However, the transit times don't jive with a trip to LA; so that might imply that Comcast has replaced a router, but hasn't (yet) changed its rDNS to match the current location.