Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Fastly, the CDN provider, is having a massive outage, resulting in Twitch, Pinterest, Reddit, The Guardian, and the FT returning 503 errors. https://status.fastly.com/
Update from Fastly's status page: Identified - The issue has been identified and a fix is being implemented. Jun 8, 10:44 UTC What's possible now is a bunch of sites will suffer from a second outage due to lack of caching as their application servers have to suddenly catch up.
Looks like the issue is resolved. Fastly run a lot of POPs (points of presence) around the world, and it may take a while to hit them all, but we're on the road to recovery.
All the sites in the first tweet are back up (from London at least). Great work @fastly SREs *hug ops*
Fastly have confirmed on their status page.
Monitoring - The issue has been identified and a fix has been applied. Customers may experience increased origin load as global services return. Jun 8, 10:57 UTC
That "origin load" is what I was warning about 
Fastly have just published an analysis on what happened when the internet fell over yesterday. Turns out a bug in Fastly's CDN had existed since May 12th that got triggered by a customer's configuration change yesterday taking down 85% of their network.https://www.fastly.com/blog/summary-of-june-8-outage …
Are you confident it's a Fastly issue? The errors I've been seeing mainly reference Varnish Cache implementations (Disclaimer: not my area of expertise, so maybe this is part of Fastly's infrastructure)
Fastly rely extensively on Varnish :)
BBC and NYT too.
Ironically they use their own system so it gave me an error 503 lol
GitHub too
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
