Developer finds 111-day unresolved 429 error hiding as transient failure in pipeline

A developer running a daily sitemap submission pipeline to IndexNow discovered that a 429 'too many requests' error had persisted continuously for 111 days without clearing, despite the pipeline making only one request per day. The unbroken streak of 429 responses began on June 10, 2026, following two extra pushes made that afternoon, after which the endpoint never returned a success response again. A parallel submission to Bing's direct endpoint continued returning 200s, ruling out issues with the URLs, host verification, or key configuration. The developer suspects the block may be tied to a shared Cloudflare Worker egress IP rather than their specific key or domain, though a recurring timeout on the quota-lookup call makes it impossible to confirm. The broader takeaway is that a soft error like a 429, typically treated as temporary and retryable, can quietly become a permanent failure while automated monitoring continues to report all systems green.