AT&T to Level 3 routing issue?

Hi,

Does anyone using AT&T seeing the routing issue to Level3? We saw some
issue with the end users using AT&T as a service provider having issue to
our upstream provider. Thanks

           Tracing route to 74.220.121.100
           over a maximum of 30 hops:
                                                                                                                                                      
           1 1 ms 1 ms 1 ms 9.126.177.132
           2 5 ms 5 ms 3 ms 9.182.248.14
           3 4 ms 3 ms 4 ms 9.182.229.20
           4 6 ms 3 ms 3 ms 9.64.194.210
           5 9 ms 11 ms 14 ms 9.64.194.253
           6 38 ms 34 ms 40 ms 9.64.193.214
           7 40 ms 35 ms 32 ms 9.64.193.179
           8 32 ms 32 ms 32 ms 9.182.211.22
           9 34 ms 33 ms 35 ms 9.124.118.4
           10 33 ms 32 ms 33 ms 122.248.182.2
           11 241 ms 169 ms 252 ms 122.248.176.50
           12 32.114.248.9 reports: Destination host unreachable.
                                                                                                                                                      
NetRange: 32.0.0.0 - 32.255.255.255
CIDR: 32.0.0.0/8
OriginAS:
NetName: ATT-32-0-0-0-A
NetHandle: NET-32-0-0-0-1
Parent:
NetType: Direct Allocation
NameServer: NS.DE.PRSERV.NET
NameServer: NS.UK.PRSERV.NET
NameServer: NS.NL.PRSERV.NET
RegDate: 1990-05-30
Updated: 2009-06-19
Ref: http://whois.arin.net/rest/net/NET-32-0-0-0-1

OrgName: AT&T Global Network Services, LLC
OrgId: ATGS
Address: 3200 Lake Emma Road
City: Lake Mary
StateProv: FL
PostalCode: 32746
Country: US
RegDate:
Updated: 2009-05-04
Ref: http://whois.arin.net/rest/org/ATGS

We saw issues with at&t last night as well. We called into Level3, but they "weren't aware of any issues". Not accepting that explanation for things, we eventually looked at Internet Health Report and saw a latency of 115ms and packet loss at 33% between at&t Chicago and Level 3 Detroit. So if anyone has more information, I'd appreciate it. thanks,

-James