From PC Mag: Fastly today provided more details on Tuesday's outage, placing the blame on an "undiscovered software bug" that was triggered by a "valid customer configuration change."
The issue dates back to May 12 when Fastly rolled out a "software deployment that introduced a bug that could be triggered by a specific customer configuration under specific circumstances." On June 8, one of its customers made that configuration change, which "triggered the bug [and] caused 85% of our network to return errors," says Nick Rockwell, SVP of Engineering and Infrastructure.
Fastly is now deploying a bug fix and conducting a post mortem on why this happened.
"Even though there were specific conditions that triggered this outage, we should have anticipated it," Rockwell says. "We provide mission critical services, and we 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."
View: Full Article