Firebase: Firebase Hosting custom domains API returning 501 errors
Affected components: Hosting
Timeline of updates
- service disruption
The engineering team is investigating elevated 501 "unimplemented" errors seen in Hosting's API when managing custom domains. It does not appear at this time that the data plane is effected.
- service disruption
We believe to have found the root cause and are working to restore this portion of our API. We are more confident now that the data plane is unaffected and that this was limited in scope to the management of Hosting custom domains.
- resolved
The fix is being rolled out. The ETA for complete resolution is July 31 at ~11:00 UTC, though some users may have restored functionality before then.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
4912eb8ab42055da…
Impact, status and times are the vendor’s own, as last archived. View on status.firebase.google.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Firebase, started 2026-07-30 21:00 UTC, resolved after 13 h, 3 update(s).
- Title
- Firebase Hosting custom domains API returning 501 errors
- Vendor
- Firebase
- Date
- URL
- https://rewindex.com/company/firebase/incidents/e1vzivqdlmv9kfgeejjr
Firebase profileRecent Firebase incidentsAll outages on July 30, 2026Firebase in July 2026MarkdownJSON