Settings changes by one Fastly customer caused global internet outage

Settings changes by one Fastly customer caused global internet outage
By Toby Sterling, Reuters
Share
Font Size
Save
Comment
Synopsis

Fastly says the global internet outage—which knocked out high-traffic sites like Amazon and Reddit—was caused by a bug in its software that was triggered when one of its customers changed their settings.

Reuters
Fastly says a software bug was trigerred after an unidentified customer carried out settings changes, "which caused 85% of our networks to return errors".
Amsterdam: Fastly Inc. said the major global internet outage on Tuesday was caused by a bug in its software that was triggered when one of its customers changed their settings.

Tuesday's outage raised questions about the reliance of the internet on a few infrastructure companies.

Fastly's issue knocked out high traffic sites including, news providers such as The Guardian and The New York Times, as well as British government sites, Reddit and Amazon.com.

"This outage was broad and severe, and we're truly sorry for the impact to our customers and everyone who relies on them," the company said in a blog post authored by Nick Rockwell, its senior engineering and infrastructure executive.

He said the problem should have been anticipated.

Fastly operates a group of servers strategically placed around the world to help customers move and store content close to their end users quickly and safely.

The company post gave a timeline of events and promised to examine and explain why Fastly had failed to detect the software bug during its own testing process.

Fastly said the bug was in a software update shipped to customers on May 12 but was not triggered until one unidentified customer carried out settings changes that triggered the problem "which caused 85% of our network to return errors".

Fastly noticed the outage within a minute it occurring at 0947 GMT, and engineers worked out the cause at 1027 GMT. Once they disabled the settings that triggered the problem, most of the company's network quickly recovered. "Within 49 minutes, 95% of our network was operating as normal," the company said. Its networks were fully recovered at 1235 GMT and it began rolling out a permanent software fix at 1725 GMT.

Read More News on

Stay on top of technology and startup news that matters. Subscribe to our daily newsletter for the latest and must-read tech news, delivered straight to your inbox.
New on
Get In-depth Reports on 4,000+ Stocks, updated daily
Make Investment decisions
with proprietary stock scores on earnings, fundamentals, relative valuation, risk and price momentum
Find new Trading ideas
with weekly updated scores and analysts forecasts on key data points
In-Depth analysis
of company and its peers through independent research, ratings, and market data