Is Cloudflare Workers Down Right Now?
Updated May 2026 · Live Cloudflare status →
📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
How to Check Cloudflare Workers Status Right Now
- 1. Visit cloudflarestatus.com (official) — look for Workers, KV, Durable Objects, R2 components
- 2. Check APIStatusCheck.com/down/cloudflare for independent monitoring
- 3. Check r/CloudFlare and @CloudflareStatus on X
- 4. In your Cloudflare dashboard: Workers & Pages → Real-time Logs to see live errors
Cloudflare Workers Error Codes Explained
| Error | Meaning | Fix |
|---|---|---|
| 1101 | Worker threw a runtime exception | Check Worker logs in dashboard |
| 1102 | CPU time limit exceeded | Optimize code or upgrade to Workers Unbound |
| 1015 | Rate limited by Cloudflare | Reduce request rate or use Workers rate limiting API |
| 1033 | Ably service (KV write) failure | Retry with exponential backoff; check cloudflarestatus.com |
| 10001 | Script too large (>1MB) | Optimize bundle or upgrade to paid plan (3MB limit) |
Cloudflare Workers Platform: Service Breakdown
When Cloudflare Workers has issues, it's rarely the entire platform at once. Each primitive has its own status:
Workers Runtime
Core edge function execution across 300+ locations
Workers KV
Eventually consistent key-value storage (up to 60s propagation)
Durable Objects
Strongly consistent stateful storage — each DO is a single instance
R2 Storage
S3-compatible object storage — separate from Workers but often used together
D1 Database
SQLite at the edge — currently in GA, occasional write latency spikes
Cloudflare Pages
Full-stack hosting with Pages Functions (Workers under the hood)
Monitor your Cloudflare Workers endpoints 24/7
Get alerted within 60 seconds when your Workers routes return errors or go dark. Better Stack monitors from 10+ global regions.
Try Better Stack Free →Troubleshooting Cloudflare Workers Issues
Check the Cloudflare status page first
Visit cloudflarestatus.com and expand the "Compute" section. Workers incidents affect specific regions — check if your users' region is affected.
Use wrangler tail for real-time logs
Run wrangler tail --format pretty in your terminal to stream live request logs from your Worker. This shows exceptions, CPU time, and response codes as requests come in.
Test in the Cloudflare Playground
Use the Workers Playground to isolate whether the issue is your code or the deployed Worker. If the same code runs fine in the playground, the issue is deployment or configuration.
Check binding configuration in wrangler.toml
Most KV, D1, and R2 failures stem from misconfigured bindings. Verify your wrangler.toml has the correct namespace IDs and binding names, and that the bindings exist in your Cloudflare account.
Add external monitoring for your Worker routes
Workers incidents can affect specific PoPs (points of presence) without triggering the global status page. Use Better Stack to monitor your Worker URL from multiple regions so you catch regional outages the status page misses.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time Cloudflare Workers goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for Cloudflare Workers + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
Related Developer Guides
Frequently Asked Questions
Is Cloudflare Workers down right now?
To check if Cloudflare Workers is down, visit the official Cloudflare status page at cloudflarestatus.com. Look for "Cloudflare Workers" under the Compute section. You can also check APIStatusCheck.com for third-party monitoring. Cloudflare posts incident updates in real time, including affected regions and Worker services (KV, Durable Objects, R2, D1).
Why is my Cloudflare Worker returning a 1101 or 1102 error?
Cloudflare Workers-specific error codes: 1101 = Worker threw a JavaScript exception (check your Worker logs in the Cloudflare dashboard), 1102 = Worker exceeded CPU time limit (50ms on free plan, 30 seconds on paid), 1015 = Rate limited (too many requests from your IP), 1033 = KV write failed — usually a transient service issue, 522/523 = Connection timed out or origin unreachable. Check cloudflarestatus.com first. If the status page shows operational, the issue is in your Worker code or configuration.
Why is my Cloudflare Pages deployment failing?
Cloudflare Pages deployment failures are typically caused by: (1) Build command error — check build logs in the dashboard for npm/yarn errors, (2) Pages Functions error — a function in /functions/ directory has a syntax error, (3) Bundle size exceeded — Pages Workers have a 1MB script limit (3MB with paid plan), (4) Environment variable missing — check that all required env vars are set in Pages settings, (5) Cloudflare Pages service outage — check cloudflarestatus.com. Most deployment failures are build errors, not outages.
How do I check if Cloudflare KV is down?
Cloudflare KV status is reported under the "Workers KV" component on cloudflarestatus.com. KV-specific issues to look for: KV reads returning stale data (KV is eventually consistent with up to 60 seconds propagation), KV writes failing with 500 errors (service issue — check status page), KV namespace not found errors (misconfigured binding in wrangler.toml). For production apps, implement fallback behavior when KV reads fail rather than assuming KV is always available.
What is the Cloudflare Workers CPU time limit?
Cloudflare Workers CPU time limits: Free plan = 10ms CPU time per request (not wall time — actual compute only), Paid/Bundled ($5/month) = 50ms CPU time per request, Workers Unbound (usage-based) = 30,000ms (30 seconds) CPU time. If your Worker hits the CPU limit, it returns a 1102 error. Solutions: optimize your Worker code, use Workers Unbound for heavy computation, or offload processing to a Worker Queue.