TEMPO.CO, Jakarta - Cloudflare has ensured that technical issues disrupting global access to applications and websites have been resolved. Several hours after the incident, the infrastructure provider and content delivery network (CDN) stated that all services were operating normally after experiencing outages.
"A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal," according to the latest official statement from the company, as cited by The Economic Times on late Tuesday, November 18, 2025.
Users of applications and visitors to websites in various countries had previously reported difficulties in accessing many platforms. From 06:00 Eastern Time (ET) onwards, various digital services, including X and ChatGPT, were inaccessible.
Cloudflare has long supported the traffic of many large-scale applications. "Any outage at Cloudflare has wide-reaching implications," as stated in a review by 9to5Mac, shortly after complaints from netizens about the disruption surfaced.
Without delay, Cloudflare immediately began investigating the issue that caused the error code 500 - a sign of internal server errors. The company also confirmed that the disruption had affected many customers.
Some users saw a page that read “Please unblock challenges.cloudflare.com to proceed”. Others see the more standard error code 500 messages.
Similar to Amazon Web Service Outage Experience
In mid-October 2025, a similar incident occurred with Amazon Web Services (AWS). The disruption affected the performance of Amazon Alexa, Snapchat, ChatGPT, and several other services. The global disruption to Amazon's cloud services affected a number of popular applications, including Roblox.
In a still-functional X, many netizens complained about not being able to play Roblox, edit in Canva, and had difficulty accessing Duolingo, which displayed a 'maintenance' message. Amazon explained that the issue originated from an error in the internal EC2 network, affecting DynamoDB, SQS, Amazon Connect, and other AWS services.
"The root cause is an underlying internal subsystem responsible for monitoring the health of our network load balancers," as stated in AWS's official statement. During the repair process, AWS limited new customer activity requests to expedite service recovery.