We have reports and confirmation from other operators of an issue with Level3 primarily affecting routing from the US/Northeast. If you are affected by this issue, your trace to your site/server may look like this:
traceroute to 63.247.133.70 (63.247.133.70), 30 hops max, 40 byte packets
1 heekinlaw.com (65.18.172.2) 1.013 ms 1.224 ms 1.215 ms
2 (69.94.3.5) 0.950 ms 0.950 ms 1.182 ms
3 69.182.114.205 (69.182.114.205) 2.575 ms 2.811 ms 2.808 ms
4 bb1-g1-0-2.mrdnct.sbcglobal.net (151.164.42.54) 3.147 ms 3.387 ms 3.380 ms
5 70.245.63.207 (70.245.63.207) 9.135 ms 9.131 ms *
6 asn3356-level3.eqnwnj.sbcglobal.net (151.164.89.250) 9.116 ms 7.781 ms 7.856 ms
7 ae-31-53.ebr1.Newark1.Level3.net (4.68.99.94) 7.936 ms 20.370 ms 20.364 ms
8 ae-1-100.ebr2.Newark1.Level3.net (4.69.132.22) 7.702 ms 7.697 ms 7.689 ms
9 ae-4-4.ebr2.Washington1.Level3.net (4.69.132.101) 13.161 ms 13.156 ms 13.414 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
All servers and services are up and operational within the network. As the remote monitor is also affected by this issue, it has been shut down for now, to save unnecessary paging. Local monitoring will be utilized until Level 3 clears whatever issues they are having. Unfortunately, there is nothing we can do related to this issue. We are currently scouting for news to determine if there is any indication from them as to what the problem is and any ETA to resolution.
Update 1:20 PM: Latency report from internetpulse
There is currently an unconfirmed report of a fiber cut in Michigan.
Level 3, Detroit
Update 1:40 PM: It appears that Level3 has cleared their issue. The remote monitor has been enabled once more.