{
  "id": 11290563,
  "title": "My static site started returning 429 to visitors - here is what I actually measured, and the $0 fix",
  "url": "https://urgent.news/2026/10/01/my-static-site-started-returning-429-to-visitors-here-is-what-i",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-01T22:07:08.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/monkeyrun/my-static-site-started-returning-429-to-visitors-here-is-what-i-actually-measured-and-the-0-fix-1jc6"
  },
  "original_language": "en",
  "account": "The author experienced a situation where their static site, a hosted static site containing guides and a product catalog, suddenly started returning a 429 status code to visitors. This error message, \"sites_daily_pv_quota_exceeded,\" indicated a daily visit limit had been reached, not an outage or abuse block. The author realized this issue while verifying their own deploy, as a log line they believed had been live-verified was already returning a 429 status. They discovered they had incorrectly recorded a claim they had not proven, leading to the site silently refusing visitors.\n\nTo resolve the issue, the author compared the deployed bytes against the local bytes on a host that was not rate-limited. The solution proved to be moving the site to an uncapped host, specifically GitHub Pages, which is a free tier with a metered ceiling that was never stress-tested in their case. However, the author had forgotten to grant the necessary OAuth scope for Pages, resulting in a 404 error when attempting to create the site.\n\nThe fix involved pushing the site to a gh-pages branch, which enabled project Pages by itself. A minute later, the site was accessible at its new URL. The author then addressed the duplicate content issue by updating URLs across 12 files and various public repositories to point to the new host. This fixed the duplicate content problem and ensured search engines treated the new host as the canonical source.\n\nThree key lessons emerged from this experience:\n\n1. Always follow redirects when checking GitHub Pages, as the service may initially respond with a 301 status code.\n\n2. Use separate commands for assertions to avoid silent failures and ensure the intended actions are executed.\n\n3. Remember that a project page is not a host root, and settings or configurations may differ from a regular site.",
  "summary": "This is a post about a real incident on a real site, with the actual response bodies. Nothing here is a tutorial I read about; every number came from my own requests. The symptom A hosted static site of mine (guides and a small product catalog) went from \"reachable\" to returning this to every visitor: HTTP / 2 429 content-type : application/json; charset=utf-8 cache-control : no-store retry-after…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}