DNS Resolution Failures for TLD .co users
Jun 8, 03:39 UTCJun 16, 08:16 UTC
Duration
8d 4h
Impact
Informational
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
Timeline
- Resolved · Jun 16, 08:16 UTC
The top-level domain provider has fixed the underlying problem that was causing this issue. Name resolution has returned to normal.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m