Independent monitoring
Cloudflare status
Partial outageMerlonix has monitored Cloudflare around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations and any incidents Cloudflare reported.
Snapshot as observed by Merlonix at Oct 8, 2026, 08:31 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.
30-day observation timeline
Each cell is one UTC day, coloured by the most severe status we observed that day. A “degraded” day reflects Cloudflare’s own published component-level status and may mean a single component was affected while the overall service was fine.
Observations recorded
406
distinct status changes over 30 days we have data for
Most recent change
Oct 8, 2026
last time the observed status changed
Days by observed status
- Degraded26d
- Partial outage4d
What Merlonix monitors for Cloudflare
Merlonix polls Cloudflare's published status source around the clock and records every change we observe — overall status, component-level incidents, and their start/resolve times. The timeline and incidents below are Merlonix's own observations, sampled independently of Cloudflare.
Recent incidents Cloudflare reported
Cloudflare One Clients are incorrectly challenged on some sites
minorScope: Cloudflare One Client
Incorrect geo location for some Cloudflare WARP users
minorScope: WARP
SYD (Sydney) on 2026-10-08
maintenanceScope: Sydney, NSW, Australia - (SYD)
ICN (Seoul) on 2026-10-08
maintenanceScope: Seoul, South Korea - (ICN)
SIN (Singapore) on 2026-10-08
maintenanceScope: Singapore, Singapore - (SIN)
Get alerted the moment Cloudflare has a bad day.
Merlonix watches Cloudflare and your other upstreams around the clock and suppresses the false alerts they would otherwise trigger on your own sites — so you only get paged when the problem is actually yours.
Other vendors we monitor