A new blog post published by the firm offers few specifics, but does explain that the offending bug surfaced as a result of a “valid customer configuration change”. Fastly apologized to its customers for failing to anticipate the conditions that triggered the outage.
“We provide mission critical services and treat any action that can cause service issues with the utmost sensitivity and priority. We apologize to our customers and those who rely on them for the outage and sincerely thank the community for its support,” wrote the firm.
Fastly is one of the world’s leading CDN providers, used predominantly by high-traffic websites to improve speed and reliability. When fully functioning, Fastly caches website content in its global network of servers, minimizing the distance information needs to travel to reach website visitors.
However, because CDNs form the backbone of the internet, an outage among one of the top providers can have serious and far-reaching consequences.
According to Fastly, the outage first began to take hold at 10:47 BST/05:47 ET, causing 85% of the company’s network to return errors. The websites and services affected included Amazon, eBay, PayPal, Reddit, Twitch and, indeed, TechRadar.
Some websites were able to restore services faster than others by switching to failover systems, but Fastly’s service began to recover within roughly 50 minutes.
“Once the immediate effects were mitigated, we turned our attention to fixing the bug and communicating with our customers. We created a permanent fix for the bug and began deploying it at 18:25 BST/13:25 BST,” said the firm.
In the aftermath, questions have been asked about the overreliance of some services on CDN networks, which could be vulnerable to cyberattacks as well as software issues, and why redundancies were unable to prevent a catastrophic crash.
Fastly has promised to conduct a “complete post mortem of processes and practices” and look into how it might be able to improve remediation times in the future.