Firebase Hosting and App Hosting returning unexpected 431 errors on some POST requests
ResolvedMinor
January 06, 2026 - Started 27 days ago
- Lasted about 1 hour
Incident Report
POST requests against Firebase Hosting Sites with rewrites to Cloud Run or Firebase Fuctions and App Hosting Backends can occasionally return unexpected 431 errors. The issue is related to necessary networking headers the products add before routing requests to Cloud Run and Firebase Functions, and only occurs if the receiving Service/Function has strictly enforced header size limits. To mitigate, increase header size limits by at least 42 bytes.
Need to monitor Firebase outages?
Monitor all your external dependencies in one place
Get instant alerts when outages are detected
Be the first to know if service is down
Show real-time status on private or public status page
The Status Page Aggregator with Early Outage Detection
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.