rewindex

CompaniesFirebaseIncidents

Firebase: 404 error for Firebase Cloud Messaging clients sending to a URL with a trailing slash

MinorStatus: resolvedStarted Resolved (7.2 h)2 updatesstatus.firebase.google.com (opens in new tab)

Affected components: Cloud Messaging

Timeline of updates

  1. service disruption

    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.

  2. resolved

    The rollback is complete - service is fully restored.

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.

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-03-17 07:00 UTC, resolved after 7.2 h, 2 update(s).

Title
404 error for Firebase Cloud Messaging clients sending to a URL with a trailing slash
Vendor
Firebase
Date
URL
https://rewindex.com/company/firebase/incidents/vh7vsady1p6il4k9d8py

Firebase profileRecent Firebase incidentsAll outages on March 17, 2026Firebase in March 2026MarkdownJSON