VulnPulse

最新のセキュリティ情報

10月22日(木)今日

  • 解決済み01:12障害・メンテナンスSupabaseSupabase Status

    Project lifecycle operations such as project creation, pausing, and restoration, in all regions

    Status: Resolved The issue affecting project lifecycle operations, including project creation, pausing, and restoration, has been resolved. We have observed a reduction in project lifecycle job failures following the fix and confirmed that operations have returned to normal. Affected components ap-southeast-2 (Operational) eu-central-2 (Operational) us-east-2 (Operational) ap-southeast-1 (Operational) ca-central-1 (Operational) ap-southeast-2 (Operational) us-west-2 (Operational) ap-northeast-1 (Operational) ap-northeast-2 (Operational) eu-west-3 (Operational) sa-east-1 (Operational) eu-centr…

10月21日(水)昨日

10月20日(火)

  • 解決済み03:13障害・メンテナンスSupabaseSupabase Status

    Support Form Errors

    Status: Resolved Ticket creation has remained normal. We re resolving this incident. Affected components Dashboard (Operational)

10月17日(土)

  • 解決済み16:49障害・メンテナンスSupabaseSupabase Status

    Project creation errors ap-ne1

    Status: Resolved Service is fully restored and project creation and unpausing has been re-enabled in the ap-northeast-1 region. Affected components ap-northeast-1 (Operational) ap-northeast-1 (Operational)

10月15日(木)

  • 解決済み05:25障害・メンテナンスSupabaseSupabase Status

    Realtime latency

    Status: Resolved Realtime has fully recovered. Affected components Realtime (Operational)

10月14日(水)

  • 解決済み03:24障害・メンテナンスSupabaseSupabase Status

    Edge Function Degradation

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

10月13日(火)

  • 解決済み10:30障害・メンテナンスSupabaseSupabase Status

    Log ingestion impaired

    Status: Resolved 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

    Status: Resolved 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月8日(木)

  • メンテナンス中02:03障害・メンテナンスSupabaseSupabase Status

    Maintenance: Statuspage Migration

    Status: Complete The statuspage migration is now complete. If you were previously subscribed via email, no action is needed, you were automatically resubscribed. If you were previously subscribed via any other method (SMS, Slack, webhook, RSS, etc.), you can now resubscribe.

10月7日(水)

  • 解決済み03:18障害・メンテナンスSupabaseSupabase Status

    Upgrade Issues

    Status: Resolved We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

10月6日(火)

9月30日(水)

  • 解決済み03:46障害・メンテナンスSupabaseSupabase Status

    401 errors due to JWT rejections

    Status: Resolved 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日(火)

  • 解決済み21:48障害・メンテナンスSupabaseSupabase Status

    Network access issues affecting a limited number of users in Myanmar

    Status: Resolved We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved. We recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks

9月12日(土)

9月9日(水)

  • 解決済み17:47障害・メンテナンスSupabaseSupabase Status

    Brief connection disruptions in us-east-1 (N. Virginia)

    Status: Resolved Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster. We apologize for any disruption caused.

9月4日(金)

9月1日(火)

8月29日(土)

  • 解決済み01:18障害・メンテナンスSupabaseSupabase Status

    Projects failing to load Supautils in multiple regions

    Status: Resolved PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts. This disrupted database access in multiple regions. Rollback is now complete and we are seeing access restored to projects in the affected regions.

8月28日(金)

8月25日(火)

8月24日(月)

8月21日(金)

8月20日(木)

8月17日(月)

8月14日(金)

8月12日(水)

8月6日(木)

8月5日(水)

7月31日(金)

  • 解決済み22:26障害・メンテナンスSupabaseSupabase Status

    DNS creation delays

    Status: Resolved The incident has been resolved.

  • 解決済み22:20障害・メンテナンスSupabaseSupabase Status

    Issues with Edge Function Deployment

    Status: Resolved A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected. As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident. All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation.