Cloudflare outage knocks dozens of sites offline as Bet365 and Uber Eats users report problems
Cloudflare acknowledged on Friday that its services were experiencing issues that left users unable to reach sites including bet365 and Uber Eats, a disruption that unfolded across Friday afternoon and prompted a company update at 2: 45 p. m. ET.
Bet365 among services hit
Users reported problems accessing the sports betting site bet365 on Friday afternoon, and other customers flagged interruptions to Uber Eats and the Steam gaming service, with complaints peaking on outage-tracking services around 2 p. m. ET.
Cloudflare status and timeline
Cloudflare posted a message saying, “Cloudflare is investigating issues with our services and/or network, ” and issued an update at 2: 45 p. m. ET saying it was continuing to restore service to impacted customers, on its status channels.
Outage reports on DownDetector for the event peaked at less than 500 on Friday afternoon, far smaller than an earlier outage in November that saw reports top 11, 000, and Cloudflare had not posted an additional update about Friday’s outage as of 3: 30 p. m. ET.
What users saw and which sites were affected
Consumers reported a range of problems: blocked pages and error messages when trying to load sites and services such as Uber, Workday and Microsoft Outlook, with some users encountering 403 errors that indicate a site is blocking access, the status messages Cloudflare posted during the incident.
Cloudflare’s network supports many websites and apps by routing traffic and protecting sites from overload and attacks, and the company noted it had performed scheduled maintenance at a Portland data center earlier on Friday, though it said it was unclear whether that maintenance contributed to the outages.
Recovery steps and what comes next
At 2: 45 p. m. ET Cloudflare said it was continuing to restore service to affected customers and pledged further updates on its system status page as investigations continued, with DownDetector reports beginning to fall shortly after the midday peak around 2 p. m. ET.
Cloudflare previously posted messages addressing other outages on its help account; for this incident the company indicated it would update its status page to clarify scope and resolution steps, and customers were advised to refresh pages or try loading alternate pages while engineers worked.
The next confirmed milestone is the company’s promise to update its status page as the investigation continues, and Cloudflare’s 2: 45 p. m. ET update remains the most recent firm posting about restoration efforts.
