Outage in Firebase
404 error for Firebase Cloud Messaging clients sending to a URL with a trailing slash
Resolved Minor
March 20, 2026 - Started 5 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 MessagingNeed 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
- Keep your team informed
Latest Firebase outages
Firebase Studio App Hosting deployment disruption - 14 days ago
We are currently experiencing high error rates on the Firebase console. Investigations are ongoing. - 15 days ago
Deploys from GitHub are failing in us-east5 - 20 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 · 6020 services available
Integrations with
