Every incident we've posted, newest first.
The fix is in place and Google sign-in works again.
We identified the issue and are applying a fix.
This incident was recorded retrospectively. Some users could not sign in with Google OAuth2. Other sign-in methods continued to work.
Realtime publishing recovered and the associated API errors stopped. We are investigating the event publishing stall and measures to prevent recurrence.
This incident was recorded retrospectively. Realtime event delivery was delayed in the New York region. A small number of API requests, including authentication and database transaction requests, returned server errors. Most API requests continued to receive successful responses.
We have implemented a mitigation that disables npm audit requests by default during Functions and Sites builds.
This prevents npm installations from waiting on the currently degraded npm audit service and should restore normal dependency installation and build times.
We are currently observing degraded performance from the npm audit service due to an ongoing npmjs incident:
https://status.npmjs.org/incidents/l4f53bbr9200
As a result, users deploying Functions and Sites that use npm may experience significantly increased dependency installation and build times.
As a temporary workaround, npm users can disable audit checks using the --no-audit flag. Alternatively, switching to Bun or pnpm can avoid the affected npm audit service.
We are monitoring the situation and will provide updates as npmjs service performance recovers.
We have rolled back an infrastructure change that caused the incident.
We are investigating reports of downtime in Singapore region
We’ve identified the issue and resolved it fully. Services have returned to normal, and our team will continue the investigation to prevent root cause in the future.
We’ve noticed an increased rate of database errors affecting a small number of projects in the FRA region. We’re investigating the issue.
We have identified the root cause of the DNS resolution errors affecting custom domains and have deployed a patch that restores service. Custom domains are now operating normally.
Our team will continue to monitor the platform closely while we work on a permanent fix to fully address the underlying issue and prevent it from recurring.
Thank you for your patience while we resolved this incident.
We have detected an increase in DNS resolution errors affecting custom domains. Our team is actively investigating the issue and working to identify the root cause. During this time, some requests to custom domains may fail to resolve or experience intermittent connectivity issues.
We will provide another update as soon as we have more information. Thank you for your patience.
