Cloudflare favicon

Cloudflare outage on 2026-10-19

cloudflarestatus.com
October 2026 19 Minor incident

Cloudflare had two separate incidents on 19 October 2026: a short DNS update delay and a much longer problem affecting Gateway and DLP enforcement for Google Gemini traffic that ran for 26h 19m. Both were faults on Cloudflare's side.

Started

11:28 UTC

Duration

Lasted 24m

Source

IsDown

Next time

Cloudflare is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: Cloudflare Sites and Services, Gateway, Data Loss Prevention (DLP), DNS Updates

What happened?

The day's first incident started at 11:28 UTC, when Cloudflare reported delays in propagation of updates to DNS records. It moved through investigating, identified and monitoring within eleven minutes and was closed out at 24 minutes total, with no further detail on what caused the propagation delay. The second incident started at 20:30 UTC and lasted 26h 19m, far longer than the first. Cloudflare identified it as an issue affecting Gateway application controls and DLP inspection, specifically for traffic to Google Gemini. The affected components listed are Cloudflare Sites and Services, DNS Updates, Data Loss Prevention (DLP) and Gateway, four components across the two incidents. Cloudflare's own updates are sparse: only two were posted for the second incident, one at the start identifying the issue and one more than three hours later saying a fix was rolling out for Gateway controls while DLP logging and enforcement were still being restored. There is no update after that point in the record, so the resolution detail beyond the stated duration is not on the record. No user reports were filed during the window for either incident. Cloudflare's status page carries the only account of what happened, and that one filing is the full extent of what's confirmed publicly about cause and scope.

Learning

Cloudflare's own probes showed 100% uptime over 24 hours and 7 days, and 99.996% over 30 days, across API control, DNS and edge data components in the EU and NA regions, and that reading is accurate for the specific endpoints being checked. It does not contradict Cloudflare's own report of a 26-hour Gateway and DLP enforcement failure, because that failure was scoped to a specific traffic path, Gateway application controls and DLP inspection for Google Gemini, not to general reachability or DNS resolution of the kind external checks measure. This is the recurring shape of these incidents: a narrow policy or inspection layer breaks while the network keeps answering requests normally, so uptime monitoring built around reachability stays green throughout. If your product relies on Cloudflare's Gateway or DLP controls for specific traffic, an external check pinging Cloudflare's edge would never have told you that enforcement was silently failing for that traffic. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.