Hosting and developer platform
Cloudflare: status and incident history today
Cloudflare Status shows an open incident: Cloudflare: Incorrect geo location for some Cloudflare WARP users.
Last checked against Cloudflare Status.
Status now
Cloudflare: Incorrect geo location for some Cloudflare WARP users
Incident status: identified.
45+ incidents in the last 90 days (5 major). Most recent major: “Cloudflare Fedramp Dashboard and Access” (2026-10-16). Consider retries, timeouts and a fallback path for this dependency. Not counted: 5 notices marked no impact.
Production checklist
Cloudflare production checklist: 5 checks before launch
- Should do: Use SSL mode Full (strict)
- Should do: Turn on Always Use HTTPS
- Should do: Add rate limiting rules for login, sign-up and API routes
Alternatives
AWS CloudFront
AWS content delivery network
Strengths
- Deep AWS integration
- Lambda@Edge support
Trade-offs
- AWS vendor lock-in
- Slower cache invalidation
Fastly
Edge cloud platform with real-time purging
Strengths
- Instant cache purging
- Edge computing (Compute@Edge)
Trade-offs
- Smaller network than Cloudflare
Akamai
Enterprise CDN with largest global network
Strengths
- Largest CDN network globally (300k+ servers)
- Industry-leading reliability and performance
Trade-offs
- Complex setup and configuration
- Overkill for small to medium businesses
Bunny CDN
Cost-effective CDN with global reach
Strengths
- Good global coverage (85+ PoPs)
- Built-in storage (Bunny Storage)
Trade-offs
- Smaller network than Cloudflare/Akamai
- Newer company (less track record)
Example stacks with Cloudflare
Docs and release notes
Check Cloudflare in your own stack
This page checks Cloudflare in general. Your repo pins specific versions: the free dependency check reads your manifests and lists what to fix first. Prism Agent runs the same live checks on your whole stack and turns them into a plan your coding agent can build.