Cloudflare outage disrupts Bet365 and dozens of major websites
Users reported that the sports betting site bet365 and the delivery service Uber Eats were not working after a Cloudflare outage left dozens of websites and apps with errors and timeouts. Cloudflare acknowledged issues and said it was working to restore service, with outage reports peaking in the early afternoon ET.
Services and sites affected
Users flagged disruptions across a range of services. Reported impacts included the delivery app Uber Eats and the gaming platform Steam, while a separate set of reports named other large business and productivity services as affected. The event left dozens of major websites intermittently inaccessible for some users.
Bet365 and Uber Eats disruption
Customers trying to reach Bet365 experienced errors and were unable to use the betting site during the outage window. The interruption to Bet365 occurred alongside trouble accessing popular consumer services, contributing to a pattern of widespread but uneven user-facing failures during the incident.
Cloudflare updates and timeline
Cloudflare posted that it was investigating problems with its services and noted that users might encounter errors or timeouts reaching its network. An update at 2: 45pm ET said the company was continuing to work on restoring service for impacted customers. Outage reports on monitoring sites peaked around 2: 00pm ET and began to fall shortly after.
Error messages and technical impact
At one point customers were seeing an unusually high number of 403 error messages, indicating blocked access when pages attempted to load. The outage also affected the public DNS landing page for the resolver address used by many users, creating an additional visible failure point for visitors who navigated to that specific address in a browser.
Scope compared with prior outages
Friday's outage appears to have been substantially smaller in scale than a previous event in November, when disruption reports peaked at around 11, 000 on monitoring platforms. For the latest event, monitoring reports peaked at under 500. Cloudflare noted it had performed scheduled maintenance at a Portland data center earlier in the day but said it was unclear whether that work contributed to the outage.
What to watch next
Cloudflare said it was continuing restoration work and updated status information at intervals during the afternoon and evening ET. The immediate indicator to watch is whether outage reports continue to fall from the early-afternoon peak; sustained declines would suggest restoration is taking hold. If reports rise again or error counts stay elevated, further disruption to sites that depend on the web infrastructure provider could persist. Uncertainty remains over the role of the earlier maintenance activity, and the company has not confirmed that maintenance was the cause.