BREAKING: Cloudflare Workers Deployment Issue for New Users [h1l9jsj2q6jc]
Cloudflare is experiencing partial disruption: New users unable to deploy Workers. Immediate workarounds for indie hackers.
π¨ BREAKING: Cloudflare Workers Deployment Issue
Status: Identified | Severity: MINOR | Impact: Partial Disruption
Last Updated: Now | ETA: Investigating
---
What's Down & Who's Affected
Cloudflare is currently experiencing issues with new user Worker deployments. Specifically:
This affects indie hackers launching their first projects on Cloudflare Workers. Existing deployments and production traffic are unaffected.
---
Immediate Workarounds (RIGHT NOW)
Option 1: Use an Existing Account (Fastest)
If you have an established Cloudflare account:Option 2: Deploy via GitHub Actions
Bypass the UI entirely: ```yaml name: Deploy Worker on: [push] jobs: deploy: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - uses: cloudflare/wrangler-action@v3 with: apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }} ``` This works around the dashboard/CLI bottleneck.Option 3: Wait for Account Activation
Cloudflare typically auto-activates new accounts within 1-2 hours. Monitor your email for confirmation.---
How to Check If Your Project Is Affected
Run this check:
```bash
Test your deployment
wrangler deployExpected error message (if affected):
"Error: Your account is not yet activated for Workers"
```Dashboard check: 1. Log into Cloudflare dashboard 2. Go to Workers & Pages 3. If you see "Activate Workers" button β you're affected 4. If you see your existing Workers β you're unaffected
Status page: Visit https://www.cloudflarestatus.com/ (check for "Workers" component)
---
Alternative Tools to Consider
If you need to ship today:
| Tool | Cold Start | Pricing | Setup Time | |------|-----------|---------|------------| | Vercel Functions | 50ms | Free tier available | 2 min | | Netlify Functions | 100ms | Free + generous limits | 2 min | | AWS Lambda | 500ms+ | Pay-per-use | 10 min | | Deno Deploy | 10ms | Free tier available | 1 min |
None of these require account activation delays.
---
Monitor Recovery
Real-time updates:
Test your deployment: ```bash
Retest every 15 minutes
wrangler deploy --name test-worker ```When successful, you'll see: β
Deployed test-worker
---
Bottom Line
This is not a security issue and won't affect your live projects. If you're blocked on new account setup:
1. Use the GitHub Actions workaround (most reliable) 2. Borrow an existing account temporarily 3. Switch to Deno Deploy or Vercel if you need immediate deployment
Cloudflare's engineering team is investigating. Expect updates within 2-4 hours.
Questions? Drop them below. We're monitoring this thread.