Outage in Firebase
404 error for Firebase Cloud Messaging clients sending to a URL with a trailing slash
Resolved Minor
March 20, 2026 - Started 25 days ago
- Lasted about 2 hours
Incident Report
Summary AI Generated
Firebase Cloud Messaging experienced 404 errors for clients sending messages to URLs with trailing slashes due to a recent change. The issue affected the Cloud Messaging component for 1.6 hours. Google resolved the problem by rolling back the change, with clients able to immediately fix the issue by removing trailing slashes from their send URLs.
A recent change is causing 404 errors for clients who send messages to a URL which includes a trailing slash (/v1/projects/my-project/messages:send/ vs /v1/projects/my-project/messages:send). We are in the process of rolling back this change.
For clients that are impacted, removing the trailing slash from the send URL will immediately resolve the problem.
Components affected
Firebase Cloud MessagingTrusted by 1000+ teams
Need to monitor Firebase outages?
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the moment something breaks.
Ready to take control?
Start Free Trial
No credit card required
Set up in 2 minutes
14-day free trial
Latest Firebase outages
Firebase AI Logic is seeing an elevated RESOURCE_EXHASUTED error rates from both Vertex AI and Generative AI servers. - 5 days ago
Physical device tests are delayed and stuck pending - 5 days ago
Test Lab is experiencing elevated inconclusive tests - 13 days ago
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.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with
