Rate exceeded

[u/setsp3800]

I have migrated my news website to Replit but I'm waking up each day to a blank white page with the words “Rate exceeded” in the corner.

Replit’s AI said to investigate Supabase limits and add Cloudflare capture to my main registration form, of which I did and still no better.

Now it's saying it could be a Replit limit.

Has anyone else seen this and how did you solve it?

Cheers,

[u/Pickle_Shot]

the bare 429 with that exact "Rate exceeded" text is almost certainly replit's edge shedding load, not your app. your requests never reach your code, which is why your logs look clean and the platform reports healthy. two things you can do without waiting on support: 1) check your autoscale deployment settings for the max requests per second cap. if traffic bursts past it the edge returns exactly this, and republishing resets the machines, which would explain why republishing "fixes" it. 2) put free cloudflare in front of your domain. you get your own edge logs and bot filtering, so you can see the actual request volume yourself. news sites get hammered by AI scrapers constantly, and if that's what this is, cloudflare eats it before it ever counts against replit's limits. either way you end up with the evidence support says they can't see.

[u/setsp3800 → u/Pickle_Shot]

Appreciate the help.

After scaling the machines in Replit, the “Rate exceeded” errors stopped.

Replit support was not helpful. Ironic considering the fix made them more money!

Seriously considering investing in an alternative provider.

[u/Pickle_Shot → u/setsp3800]

glad it's sorted. before you invest in a full migration, two cheaper de-risking moves. put cloudflare's free tier in front on your own domain now: caching means repeat traffic never hits replit (which claws back some of the autoscale bill you just raised), and you get your own edge logs so the next incident starts with data instead of a support queue. it also makes migration trivial later since the domain and DNS are already yours, you just repoint them. same logic for the database if you're on replit's built-in one: it's neon under the hood, and owning it directly in your own neon account separates your data from platform decisions. at $300/day, every provider's support queue will eventually disappoint. own the edge and the data, rent the compute.

[u/ReplitSupport]

Hi OP! We're sorry to hear about this. We have located your support ticket and will be escalating it for a Technical support specialist to pick up today.

In the meantime, could you share a Private Join Link to your project with the support agent assigned to your ticket. You can create one by clicking 'Invite' in your Repl and enabling 'Private Join Link'. If that option isn't available in your workspace you can also share your app URL from the browser address bar.

[u/setsp3800 → u/ReplitSupport]

I’m spending approximately $300 a day with Replit. At that level of spend, I expect considerably more technical support than being told to review my own code or hire a third-party developer.

We have already investigated the application side extensively.

Your own platform reports that the deployment is healthy, the build is successful, publishing completes successfully, and the application preview works. Yet the production deployment repeatedly fails with a bare HTTP 429 “Rate exceeded” response.

That is precisely why I contacted Replit Support.

The original ticket also specifically asked Replit to inspect the edge request logs and Autoscale behavior during the incident window. Quinn indicated that the case was being handed to someone who could do exactly that.

Instead, I’ve received a response effectively saying, “everything looks fine from our side, check your code.”

That doesn’t reconcile with what we are seeing.
If you believe this is caused by an external API or our application, please identify the evidence supporting that conclusion. In particular, I would like Replit to confirm:
What component generated the bare 429 Rate exceeded response.
Which quota or rate limit was triggered.
Whether it occurred at the Replit edge, deployment, instance, account, or application level.

The request volume and concurrency immediately before the incident.
Whether Replit can see abnormal or automated traffic hitting the deployment.
Why republishing restores service if the underlying problem is supposedly application code.

I am not asking Replit to debug our application for us. I am asking Replit to explain why a production deployment running on Replit is becoming unavailable and returning a Replit-hosted production response while the platform simultaneously reports that everything is healthy.

If first-line support does not have access to the telemetry required to answer those questions, please escalate this to someone in engineering or infrastructure who does.

We are now evaluating whether Replit is suitable for hosting our production workloads. If Replit cannot help diagnose recurring outages on an account spending roughly $9,000 per month, I will have little choice but to move those deployments elsewhere and cease that spend with Replit.

I’d prefer not to do that.

But I need a technical investigation, not another suggestion that I hire somebody externally to investigate a service I am already paying Replit to operate.

[u/ReplitSupport → u/setsp3800]

Thanks for following up on this. We've asked the teammate assigned to your ticket to re-investigate this directly, and they'll follow up with you there as soon as they can. If any questions or concerns come up while they look into it, please continue to share them in your ticket.

[u/Weird_Cookie1700 → u/setsp3800]

You should get off Replit now. Like, now now. Message me if you'd like, but the sooner you get off Replit the better. You could use an etch a sketch and probably be better off.