SoylentNews is people
SoylentNews
Websites begin to work again after major breakage:
A major outage has affected a number of major websites including Amazon, Reddit and Twitch.
The UK government website - gov.uk - was also down as were the Financial Times, the Guardian and the New York Times.
Cloud computing provider Fastly, which underpins a lot of major websites, said it was behind the problems.
The firm said there were issues with its global content delivery network (CDN) and was implementing a fix.
In a statement, it said: "We identified a service configuration that triggered disruption across our POPs (points of presence) globally and have disabled that configuration.
"Our global network is coming back online."
[...] Fastly runs what is known as an "edge cloud", which is designed to speed up loading times for websites, as well as protect them from denial-of-service attacks and help them when traffic is peaking.
It currently looks as if the problems were localised, meaning specific locations across Europe and the US were affected.
Also at c|net
(Score: 2) by looorg on Wednesday June 09 2021, @11:01AM (2 children)
Apparently Fastly are now throwing some unnamed (or unknown) customer under the bus as the one responsible for the outage.
https://www.fastly.com/blog/summary-of-june-8-outage [fastly.com]
(Score: 0) by Anonymous Coward on Wednesday June 09 2021, @01:15PM (1 child)
They describe it as a software bug they themselves introduced, which was triggered by a valid configuration change by a customer. Perhaps they changed the text since you read it, but right now they are clearly not blaming the customer.
(Score: 2) by looorg on Wednesday June 09 2021, @02:33PM
Fine. I think they might have changed it a bit then cause when I read it this morning (CET) it was more or less that while it was a software bug somehow a user managed to push their configuration onto the entire network and that made a lot of the other customers sites unreachable. They didn't want to name that customer. Not that I believe that it was malicious intent on the part of the user/customer but they still at that time assigned blame there instead of taking responsibility for their own software bugs. That said it took a long time before it happened, they pushed their "bug" out to the customers in may and it didn't trigger until yesterday. So if it was a known software bug one wonders why they didn't bother fixing it for almost an entire month.