Incidents, maintenance, and status

Public status

The status page reports component health, active incidents, incident history, and scheduled maintenance. Subscribe with an operations mailbox so outages are not dependent on one person noticing the console.

During an incident

1. 1Check the public status page and console notifications.
2. 2Identify affected project, database, region, and timeline.
3. 3Avoid repeated destructive retries.
4. 4Collect safe error messages and request IDs.
5. 5Open a support request if your resource is affected but no incident is listed.

Scheduled maintenance

Review the stated window, expected impact, and required customer actions. Test reconnect behavior before the window and avoid unrelated schema or infrastructure changes at the same time.