"Routine Cloudflare maintenance went awry this morning, knocking over the company's dashboard and API and sending sites around the world into error screens. Cloudflare was working through its scheduled servicing when things went sideways. Maintenance was in progress in its Chicago datacenter from 0700 UTC, with work due to begin in its Detroit datacenter at 0900 UTC when red lights began flashing at administrators around the world."
"The content delivery network giant admitted a problem with its service at 0856 UTC, rolled out a fix shortly after, and seemed to be back up and running by 0930 UTC. It has, however, now reported issues with Workers (the serverless functions, not the employees likely frantically trying to stop the company's systems from falling over again)."
Routine maintenance at Cloudflare's Chicago datacenter began at 0700 UTC, with Detroit work scheduled for 0900 UTC. During servicing the company's dashboard and API failed, causing many sites to display error screens. Cloudflare admitted a problem at 0856 UTC, rolled out a fix shortly after, and appeared to restore service by 0930 UTC. The company later reported issues with Workers, its serverless functions. Cloudflare protects roughly 20 percent of websites, amplifying the outage impact. High-end retailer Fortnum & Mason briefly returned a 500 Internal Server Error. Two outages in two months raise dependency concerns following November's database-permissions incident.
Read at Theregister
Unable to calculate read time
Collection
[
|
...
]