Cloudflare outage knocks multiple services offline; Bet365 affected, bet365 users report errors
Cloudflare acknowledged on Friday that its services were experiencing 'issues', a disruption that left users unable to reach dozens of websites and apps. The outage mattered immediately because users reported trouble accessing popular services including UberEats and bet365, and the provider issued afternoon updates while work continued to restore normal traffic.
Services and users affected
Users reported errors and timeouts when trying to use commerce and entertainment services during the outage. In addition to problems reported with UberEats and Bet365, some users said they encountered difficulties with a PC gaming service. The interruptions appeared focused on a subset of sites that depend on the provider’s infrastructure rather than a wholesale internet blackout.
Bet365 access issues and user impact
Bet365 was among the publicly flagged services where customers experienced access problems. Users attempting to place bets or load pages saw timeouts and error messages during the outage window, and the provider’s updates indicated efforts to restore service for impacted customers.
Timeline and company updates
Outage reports on a widely used monitoring website peaked at around 2: 00pm ET and began to fall shortly afterward. The provider issued an update at 2: 45pm ET saying it was continuing to work on restoring service to impacted customers. Earlier communications from the company noted that scheduled maintenance had been taking place at a Portland data center, though it remained unclear whether that maintenance contributed to the disruptions. As of 3: 30pm ET, the provider had not posted a fresh status message about the incident on its help account on a social platform.
Scale compared with prior outages
This outage appears smaller than a major event the provider experienced in November. The monitoring website recorded a peak of under 500 outage reports on Friday afternoon, compared with roughly 11, 000 reports during the larger November incident. That earlier event affected a wide range of high-traffic sites and services; by contrast, Friday’s disruption seemed limited to specific customers and services that use the same infrastructure.
- Key takeaways: company acknowledged issues, users saw errors around 2pm ET, provider issued a 2: 45pm ET update, reports were under 500 at peak.
Looking ahead, the immediate indicator to watch is whether report counts and service errors continue to decline; if they remain low, the incident may be confined to a handful of services. If maintenance at the Portland data center is confirmed as a factor, further status updates from the provider will be the primary source for a definitive cause. At this stage, some details remain not publicly confirmed.
