Hm, laut Sapience liegt es wohl nicht an Pando:
Right off the bat, no this was in no way related to Pando. I know some were trying to tie the two together but pando is unrelated to this issue and their announcement has had 0 impact on us in any way.
Übersetzung: Es gibt keine Anhaltspunkte, das es mit Pando zusammenhängt. Sie haben geschaut, ob es da eine Korrelation gibt, aber die Ankündigung von Pando hat wohl nix mit den Problemen hier zu tun.
This issue is one we've seen before with a slight twist. This was again a routing issue with a very large internet backbone provider and how it routes traffic in and out of our data center provider (so you're talking 2 layers removed from our direct ability to 'fix it'). The issue also created a cascade issue when the routes were reset that didn't play well with some of the switches and routing hardware in the data center. This is why we've been working through the night with our vendors (provider, hardware, consultants, and others) to make sure each step of the connection from our service through various vendors services and products was checked, doubled checked, and confirmed to be either working correctly or needed to be addressed. We continue to do so, though we believe we are much closer to a resolution than at any point in the past several hours and we feel we are very close to restoring services.
Es hat wohl irgendwas mit dem Internet-Provider und der Routing-Verbindung zu tun, das wohl in abgewandelter Form schon früher mal vorgekommen ist. Denke da gerade an die Downtime im Februar zurück...
Gruß
Nunebdui