3

I'm having issues with most of the SE sites if they use sstatic.com to server their static files (Like Area51).

Files are just not being downloaded. I tried on 2 different connections (3G and DSL) and 2 different devices (Mobile and Ubuntu (Firefox & Chrome)).

I don't see anything on the twitter account nor on http://stackstatus.net/ so it might be a regional/localized issue.

According to firebug, sstatic.net is resolving to 190.93.246.58 if that helps.

closed as off-topic by ᔕᖺᘎᕊ, Infinite Recursion, Shadow Wizard, Werner, Monica Cellio Jun 12 '15 at 23:07

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "The problem described here can no longer be reproduced. Changes to the system or to the circumstances affecting the asker have rendered it obsolete. If you encounter a similar problem, please post a new question." – ᔕᖺᘎᕊ, Infinite Recursion, Shadow Wizard, Werner, Monica Cellio
If this question can be reworded to fit the rules in the help center, please edit the question.

5

We are seeing a combination of two issues.

Issue #1: DNS was down for several edge endpoints around the world heavily affected sstatic's DNS resolution. This has been resolved.

Issue #2 (possibly related): On the CloudFlare side, a route leak in Asia affecting that IP you resolve to (and thousands of others).

In the next few minutes, if the route leak is not resolved I will be turning off CloudFlare and directly serving all static assets out of our New York data center (unfortunately, we powered down Oregon yesterday). This in itself is not without risk as it's potentially a tremendous amount of bandwidth.

We'll provide updates on @StackStatus as they're available.

  • 1
    Thanks for the update! Everything is working normally now. (btw, I'm in Lebanon, so I might have been affected by the route leak). – Dan Jun 12 '15 at 12:22

Not the answer you're looking for? Browse other questions tagged .