fast.ly has announced that "The issue has been identified and a fix has been applied. Customers may experience increased origin load as global services return."
That's code for "we had to dump everything and ask all our subscriber websites to refill the entire cache."
fast.ly also reported the affected areas... that would be pretty-well everyone:
As we write, services are slowly returning to normal, but things probably won't be stable for some time.
Of course, what we really want to know... was it phat phingers, or a physical phailure?
More information as it comes to hand.