Error 1027 — Worker exceeded free tier daily request limit
Cloudflare Error 1027 means your Worker on the Free plan has exceeded the 100,000 requests/day limit. The limit resets at 00:00 UTC. Once you hit it, Cloudflare returns a 1027 error page to every visitor until midnight UTC — even if your domain is on a paid plan, because Workers limits are separate from zone plan limits.
Common causes
- ▸Traffic spike: a viral post, Product Hunt launch, or sudden scraper/bot attention pushed you past 100k requests in 24 hours
- ▸Retry storms: a buggy client or upstream API retrying failed requests generates 5-10x normal traffic
- ▸Hot-path Worker: routing static assets (images, CSS, JS) through a Worker instead of serving them directly burns a request per asset
- ▸Misconfigured Pages Functions: each Function invocation counts as a Worker request on the Free plan
- ▸Cron Triggers running frequently: a Worker running every minute burns 1,440 invocations/day even with zero user traffic
- ▸Infinite redirect loops or fetch recursion inside the Worker itself
Symptoms
- •Every visitor sees the same Cloudflare 'Error 1027' page around the same time of day
- •The site was working fine, then suddenly returns 1027 for everyone
- •Errors start at a consistent time and stop at 00:00 UTC (midnight UTC) when the limit resets
- •Cloudflare dashboard shows the Worker on the Free plan and a daily request counter near or at 100,000
- •You're on a paid Cloudflare zone (Pro/Business) but still hitting 1027 — because the Worker itself is on the Free plan
How to fix it
- ✓Upgrade to Workers Paid ($5/month): includes 10 million requests/month with no daily cap, plus higher CPU/memory limits
- ✓Configure fail-open vs fail-closed behavior in wrangler.jsonc — fail-open serves the request without the Worker when you're over limit, fail-closed returns 1027 to the user
- ✓Route static assets around the Worker: serve images/CSS/JS directly from Pages, R2, or the Cache API instead of passing them through your Worker's fetch handler
- ✓Throttle Cron Triggers: if you have a Worker running every minute, change it to every 5 or 15 minutes to cut cron-related invocations by 80-95%
- ✓Add bot/scraper protection with Cloudflare Bot Fight Mode or a WAF rule that blocks obvious scrapers before they reach the Worker
- ✓Monitor your daily request burn in real time — Cloudflare's dashboard lags, so by the time you see 1027 errors you've already been failing for hours
How FlareLog helps
Cloudflare's request counter in the dashboard lags by 15-60 minutes — by the time you see you're near the limit, users are already seeing 1027. FlareLog counts every Worker invocation in real time via the Tail Worker and alerts you at 70%, 90%, and 100% of your daily Free-tier cap. You get a Slack/Discord/email alert hours before you hit the wall, with enough time to upgrade or throttle traffic. FlareLog also breaks down requests by route, so you can see exactly which endpoint is burning your quota.
Catch Error 1027 with FlareLog →FAQ
Why am I getting Error 1027 on a paid Cloudflare plan?
Cloudflare zone plans (Pro, Business, Enterprise) and Workers plans (Free, Paid) are billed separately. A Pro zone does NOT include Workers Paid — you can have a $20/month Pro zone and still be on the Workers Free plan with the 100k/day limit. To remove the daily limit, upgrade specifically to Workers Paid ($5/month) in the Workers & Pages section of the dashboard, not the zone plan section.
What time does the Cloudflare Workers daily request limit reset?
The 100,000 requests/day limit resets at 00:00 UTC (midnight UTC) every day. If your traffic is concentrated in a single timezone, the reset will feel random — for example, 00:00 UTC is 19:00 (7pm) in New York (EST) or 16:00 (4pm) in Los Angeles (PST). Plan around this: if you launch on Product Hunt, do it after the UTC reset so you have the full 100k window.
Does Error 1027 cost me money?
No — 1027 is a hard stop, not a billable event. Cloudflare simply refuses to invoke your Worker and serves a static error page. You don't pay for the blocked requests. However, the business cost (lost revenue, churned users, damaged reputation) can be significant if 1027 persists for hours. Workers Paid ($5/mo) removes the limit entirely.
How can I see how many requests I have left today?
Cloudflare's dashboard shows a daily request counter under Workers & Pages → your Worker → Metrics, but it lags 15-60 minutes behind real traffic. For real-time visibility, deploy a Tail Worker (like FlareLog) that counts every invocation as it happens and alerts you before you hit the limit. This is the only reliable way to catch a spike before it becomes 1027 errors.
What's the difference between Error 1027 and Error 1102?
Error 1027 means you hit the Free plan's 100,000 requests/day limit — a quota/plan issue, not a per-request failure. Error 1102 means an individual request exceeded the CPU time or memory limit — a per-request resource failure. 1027 affects every request until midnight UTC; 1102 only affects the specific request that exceeded resources. Upgrade to Workers Paid to fix both.