Hi,
Below is a chat with Netlify AI.
My domain keeps getting locked out locally if I use too many addresses or something. I use netlify for my domains and builds. I have gospelgo.org, bubbleshooter.gospelgo.org (
bubbleshooter-gospelgo-org), word.gospelgo.org (word-gospelgo-org)
It recovers after several minutes usually. I test a lot after builds. I hard-refresh (Shift/Ctrl+R) to see the new build which seems to trigger it.
I even notice that some netlify sites are unreachable during these outages (e.g., Netlify Community · Terms of Service );
I can reach others sites when this happens. I use Clean Browsing DNS servers on my main PC but not on my Router. I have a linux box that also experiences this outage on my ISP’s DNS servers.
Once I was at a friends house showing him all the software and that triggered it at his house / network. Also, maybe it happens more with the domains hosting webgl games? those download lots more data. Word and bubbleshooter are webgl games.
Based on your new details — recovering after a few minutes, triggered by rapid refreshing, happening across different networks, and possibly related to heavy WebGL game downloads — this sounds much less like an SSL rate limit issue and more like Netlify’s built-in rate limiting or DDoS protection being triggered by high request rates.
What’s Likely Happening
Netlify’s rate limiting counts requests per domain and IP address over a 60-second window by default. When the limit is exceeded, requests are blocked and return an HTTP 429 status
This fits your symptoms:
- Recovers after a few minutes — consistent with a short time window resetting
- Triggered at your friend’s house — the rate limit is per IP, so his network’s IP triggered it independently
- Rapid refreshing after builds — each refresh generates multiple requests, especially for WebGL games with large asset downloads
Why WebGL Games Make It Worse
WebGL games download significantly more data and likely make many parallel requests for assets (textures, scripts, audio, etc.). This dramatically increases your request count in a short window, making it much easier to hit rate limits compared to a simple webpage.
What You Can Do
The knowledge sources don’t contain enough detail about adjusting default rate limit thresholds on non-Enterprise plans. However, a few things worth noting:
- Full rate limiting customization (beyond basic functionality) is only available on Enterprise plans with High-Performance Edge. [Rate limiting docs]
- On all plans, you can configure code-based rate limiting rules targeting specific paths.
- If this is significantly impacting your workflow, it would be worth contacting Netlify Support to clarify the exact limits applying to your plan and whether any adjustments are possible.
I’d recommend opening a support thread with details about which specific domains/games trigger it most, as that will help Netlify diagnose whether it’s rate limiting, DDoS protection, or something else entirely.
Let me know how to proceed?
To recreate, visit word gospelgo org or bubbleshooter gospelgo org and hard refresh 2 or 3 times in a row. The reason I have done this is some minor detail that I just updated seems to be aggressively cached and I have to refresh more than once to see the change even though my versioning number changed to the latest.