Around noon on 18 November 2025, errors such as “Internal Server Error”, “Error code 500” and “Cloudflare Error” messages appeared en masse. Many visitors saw blank pages, error codes or websites that wouldn't load, and the question arose: what was behind it?
The problem didn't come from the websites, the hosting providers or the browsers. The error was caused by a provider called Cloudflare, which handles the traffic of millions of websites worldwide.
Outlets such as AndroidAuthority, The Independent, WindowsCentral or the New York Times also reported that Cloudflare's service collapsed in several regions at once. The affected areas included Budapest, where the system showed “Cloudflare: Error” while the browser and the website's server (“Host: Working”) were working fine.
What do “Internal Server Error” and “Error code 500” mean in the case of Cloudflare?
Normally these errors would point to the website's server, but this time something else happened.
Cloudflare's own error page also showed:
- You / Browser: Working
- Budapest / Cloudflare: Error
- Host: Working
This clearly means that the connection between the browser and the website's server broke in the Cloudflare layer.
In other words, the website itself wasn't faulty; Cloudflare simply couldn't serve the request.
That's why these errors, typical of common search terms, could appear:
- “Internal server error Cloudflare”
- “Error 500 Cloudflare”
- “Error code 500”
- “Cloudflare down”
- “Cloudflare Budapest error”
What caused the Cloudflare outage?
Cloudflare hasn't yet published a detailed technical explanation, but several sources have reached a similar conclusion:
- an internal infrastructure fault,
- possibly a faulty update,
- a routing or network disruption,
- or a planned maintenance may also have been behind it.
It's important to stress that, based on the information available, it was not a hacker attack, not a data breach and not a security incident.
Why did it affect so many websites?
Cloudflare is one of the world's largest traffic distribution and security systems. Millions of websites use it for speed, protection or DNS services. If an error occurs in a region, users may see entire pages with an “Internal Server Error” or “Error code 500” message, even if the website's server is actually working perfectly.
That's how completely different sites, news sites, webshops and services, could all “go down” at the same time.
What can users do in a case like this?
- Wait until Cloudflare fixes the problem.
- It's worth reloading the page every few minutes.
- If you use a VPN, switching to another country may make the site work, because the problem depended on the region.
- You can check the problem by searching for terms such as “Cloudflare down” or “Cloudflare status”, or on Downdetector.
Website owners have nothing to do in this case: as soon as Cloudflare fixes the error, everything recovers automatically.
Summary
Today's outages were caused by a large-scale Cloudflare failure. The “500 Internal Server Error”, “Error code 500” and “Cloudflare Error” messages don't actually indicate a fault with the website, but a central infrastructure problem.
There's no reason to worry: there was no hacker attack, no data was damaged, and the websites didn't break. Once the fault was fixed, all services came back or are gradually coming back.
