VulnPulse

Supabase Status의 정보

10월 23일 (금)어제

  • 해결됨03:03장애·점검SupabaseSupabase Status

    Log Drain Issues

    This issue is now resolved. Affected components Logging & Observability (Operational)

  • 대응 중02:01장애·점검SupabaseSupabase Status

    Elevated Mgmt API Error Rates in Multiple Regions

    We have additional mitigations we will be deploying to reinforce the Management API. Updates will be forthcoming if anything changes that could impact customers. Affected components eu-west-3 (Operational) eu-west-2 (Operational) ap-southeast-1 (Operational) us-west-1 (Operational) us-east-2 (Operational) eu-west-1 (Operational) ap-east-1 (Operational) us-west-2 (Operational) ap-southeast-1 (Operational) eu-central-2 (Operational) us-east-1 (Operational) us-east-2 (Operational) eu-west-1 (Operational) eu-central-1 (Operational) eu-west-2 (Operational) eu-west-3 (Operational…

10월 22일 (목)

10월 21일 (수)

10월 20일 (화)

10월 17일 (토)

10월 15일 (목)

10월 14일 (수)

  • 해결됨03:24장애·점검SupabaseSupabase Status

    Edge Function Degradation

    Edge function deployments have remained stable. We are closing the incident. Affected components ap-northeast-2 (Operational) eu-west-1 (Operational) eu-central-2 (Operational) us-west-1 (Operational) ap-east-1 (Operational) eu-central-1 (Operational) ap-southeast-2 (Operational) eu-north-1 (Operational) us-east-1 (Operational) ca-central-1 (Operational) ap-southeast-1 (Operational) eu-west-3 (Operational) sa-east-1 (Operational) eu-west-2 (Operational) ap-northeast-1 (Operational) us-east-2 (Operational) ap-south-1 (Operational) us-west-2 (Operational)

10월 13일 (화)

  • 해결됨10:30장애·점검SupabaseSupabase Status

    Log ingestion impaired

    We have resolved the log ingestion issue. During the time of this incident, logs may have been delayed or unavailable. Log ingestion has now returned to normal operation. Affected components Logging & Observability (Operational)

10월 10일 (토)

  • 해결됨11:10장애·점검SupabaseSupabase Status

    Intermittent connection errors via the connection pooler in us-east-1

    Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.

10월 7일 (수)

10월 6일 (화)

9월 30일 (수)

  • 해결됨03:46장애·점검SupabaseSupabase Status

    401 errors due to JWT rejections

    The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information: https://supabase.com/docs/guides/platform/upgrading Thank you again for your patience while we worked on resolving this issue.

9월 28일 (월)

9월 25일 (금)

9월 24일 (목)

9월 23일 (수)

9월 22일 (화)

9월 20일 (일)

9월 17일 (목)

9월 16일 (수)

9월 15일 (화)

9월 12일 (토)

9월 9일 (수)

9월 4일 (금)

9월 1일 (화)

8월 29일 (토)

8월 28일 (금)

8월 25일 (화)

8월 24일 (월)

8월 21일 (금)

8월 20일 (목)

8월 17일 (월)

8월 14일 (금)

8월 12일 (수)

8월 6일 (목)

8월 5일 (수)