Starting at 8am Central Time, we're seeing issues with Level3 in Chicago. I don't have access to the far end to do a traceroute from the far side. Traceroute with our Level3 peering up: Tracing the route to tcsmonitor.trendcs.com (198.17.225.17) 1 vlan372.car2.StLouis1.Level3.net (4.53.162.241) [AS 3356] 160 msec 8 msec 4 msec 2 4.69.201.1 [AS 3356] [MPLS: Label 1173 Exp 0] 16 msec 8 msec 16 msec 3 ae-1-100.ebr2.Chicago2.Level3.net (4.69.132.114) [AS 3356] [MPLS: Label 1233 Exp 0] 8 msec ae-6-6.ebr1.Chicago1.Level3.net (4.69.140.189) [AS 3356] [MPLS: Label 1096 Exp 0] 12 msec ae-1-100.ebr2.Chicago2.Level3.net (4.69.132.114) [AS 3356] [MPLS: Label 1233 Exp 0] 8 msec 4 * * * 5 * * * 6 * * * Traceroute with it down, traffic moved to Sprint: Tracing the route to tcsmonitor.trendcs.com (198.17.225.17) 1 qncy-pc-cat-0001.adams.net (66.226.125.198) 4 msec 0 msec 0 msec 2 sl-st20-chi-9-0-1.sprintlink.net (144.223.60.49) [AS 1239] 8 msec 4 msec 8 msec 3 144.232.8.114 [AS 1239] 8 msec 4 msec 4 msec 4 vlan52.ebr2.Chicago2.Level3.net (4.69.138.190) [AS 3356] [MPLS: Label 1233 Exp 0] 8 msec 16 msec 4 msec 5 * * * 6 ae-1-9.bar2.Cleveland1.Level3.net (4.69.136.193) [AS 3356] [MPLS: Label 299776 Exp 0] 24 msec 64 msec 52 msec 7 ae-0-11.bar1.Cleveland1.Level3.net (4.69.136.185) [AS 3356] 24 msec 24 msec 24 msec 8 FIDELITY-AC.bar1.Cleveland1.Level3.net (4.53.196.30) [AS 3356] 136 msec 212 msec 212 msec 9 ge-1-0-1.ar2.kth.cle.oh.fidelityaccess.net (66.94.64.7) [AS 22958] 16 msec 16 msec 16 msec 10 net-207-58-250-91.arpa.fidelityaccess.net (207.58.250.91) [AS 22958] 16 msec 20 msec 16 msec We've opened a ticket with Level3, just wondering if anyone else has noticed problems this morning.