20 Nov
2014
20 Nov
'14
2:42 a.m.
On 11/19/2014 07:29 PM, David Hubbard wrote:
Appears to have been resolved after seven hours. My ticket just says:
"We isolated the routing issue and resolved it. The issue was due to a misconfiguration on one our core routers."
Now that the issue is corrected, interestingly enough, my trace goes from Tampa to Chicago instead of Dallas.
our issue was resolved around the same time but is apparently now occurring again, since 0638 utc -- routing issue affecting (for us) traffic on level3 between chicago, illinois, and cincinnati, ohio. i imagine it's affecting other locations as well. /chl