How often does Supabase have outages?

Supabase has had 50 reported incidents recently. Visit apistatuscheck.com/incidents/supabase for the complete outage history with timelines and resolution details.

What was the last Supabase outage?

The most recent Supabase incident was "Supavisor connectivity in eu-central-1" on May 3, 2026. It was classified as minor impact and is currently resolved.

Supabase Outage History

50 incidents reported. Data sourced from the official Supabase status page.

Total Incidents

Major/Critical

Minor

Resolved

May 2026

Supavisor connectivity in eu-central-1

minor

May 3, 10:30 PM→May 3, 10:30 PMresolved

May 4, 04:58 PM

resolved — From 15:30 to 7:00 UTC, for projects in eu-central-1, a Supavisor node experienced connectivity issues and was not able to connect to customer databases, causing checkout timeouts and auth query faile...

April 2026

403 errors for PostgREST requests

major

Apr 28, 09:26 PM→Apr 28, 11:31 PMresolved

Apr 28, 11:31 PM

resolved — This is now resolved. Thank you for your patience while we worked to resolve this issue.

Apr 28, 11:03 PM

monitoring — The exceptions fix has been rolled out, and we are monitoring for continued stability.

Apr 28, 10:24 PM

identified — We are continuing to work on a fix. We’ll share further updates as progress is made.

+3 more updates

Some Projects Unreachable following Project Restart

major

Apr 27, 10:54 AM→Apr 27, 08:05 PMresolved

Apr 27, 08:05 PM

resolved — All projects are patched and this is now resolved. Thank you for your patience while we ensured all projects were updated.

Apr 27, 05:31 PM

monitoring — The fix has been rolled out, and we are monitoring for continued stability. Any remaining impacted projects are being manually patched.

Apr 27, 04:05 PM

identified — The permanent fix has now been rolled out across the fleet. We are continuing to manually patch any remaining impacted projects to restore service.

+5 more updates

Some projects unavailable across multiple regions

major

Apr 27, 12:39 PM→Apr 27, 07:04 PMresolved

Apr 27, 07:04 PM

resolved — This incident has been resolved.

Apr 27, 06:34 PM

monitoring — We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new is...

Apr 27, 04:22 PM

identified — The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all ...

+4 more updates

Inadvertently disabled pg_graphql for some projects

none

Apr 26, 05:52 PM→Apr 26, 05:52 PMresolved

Apr 29, 05:52 PM

resolved — A modification to existing projects was deployed due to the recently communicated Data API and pg_graphql changes. https://github.com/orgs/supabase/discussions/45329 This modification was supposed to...

Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1

major

Apr 25, 04:16 AM→Apr 25, 05:47 AMresolved

Apr 25, 05:47 AM

resolved — This issue has now been resolved and projects have returned to normal.

Apr 25, 05:14 AM

monitoring — Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability.

Apr 25, 04:38 AM

identified — Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event...

+2 more updates

Newly created projects may be unreachable

major

Apr 24, 11:21 AM→Apr 24, 02:36 PMresolved

Apr 24, 02:36 PM

resolved — The issue has been resolved and DNS resolution is now operating normally.

Apr 24, 12:43 PM

monitoring — A fix has been implemented, and we are seeing improvements in DNS resolution. We’re closely monitoring to ensure the issue is fully resolved and services remain stable.

Apr 24, 11:56 AM

identified — We are currently experiencing an issue propagating new DNS records for our zone. We are working closely with our upstream network providers technical team to implement a fix and will share updates as ...

+1 more updates

Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code

none

Apr 24, 10:00 AM→Apr 24, 10:00 AMresolved

Apr 28, 08:34 PM

resolved — Incident Summary A health check designed to prevent Out-of-Memory (OOM) conditions began closing some incoming connections, which led to 503 errors for a subset of users. These errors were initially s...

Increased Errors on HTTP Endpoints

major

Apr 17, 01:02 PM→Apr 18, 02:01 AMresolved

Apr 18, 02:01 AM

resolved — All metrics have been nominal and stable for several hours now, and our upstream provider has resolved their incident.

Apr 18, 12:37 AM

monitoring — We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a ...

Apr 17, 11:08 PM

identified — We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the...

+15 more updates

Transactional Email Delivery Delays

none

Apr 16, 07:05 PM→Apr 17, 05:00 PMresolved

Apr 17, 05:00 PM

resolved — Email queues have returned to normal.

Apr 16, 08:51 PM

monitoring — Customers will continue to see these delayed transactional emails while we clear the backlog. We will provide another update once these queued emails are sent.

Apr 16, 07:37 PM

monitoring — We have made progress investigating the specific causes of the email spike and are determining appropriate next steps to improve clearance of the backlog.

+1 more updates

Project creation failures in some APAC regions

major

Apr 12, 03:51 PM→Apr 12, 05:03 PMresolved

Apr 12, 05:03 PM

resolved — Capacity has been fully restored in the impacted APAC regions, and project creation is operating normally.

Apr 12, 04:19 PM

monitoring — We are recovering capacity in the impacted APAC regions and are seeing improvements in project creation success rates. We will continue to monitor to ensure stability.

Apr 12, 03:51 PM

investigating — We are currently investigating an issue affecting project creation in some APAC regions. Users may experience failures when attempting to create new projects in impacted regions. Existing projects ar...

Logs currently inaccessible via the Dashboard and Log Drains

critical

Apr 8, 07:10 PM→Apr 8, 08:05 PMresolved

Apr 8, 08:05 PM

resolved — This incident has been resolved.

Apr 8, 07:41 PM

monitoring — All log sources have been restored and logs should be available to users again now. We are keeping an eye on things to ensure ongoing stability.

Apr 8, 07:24 PM

identified — The underlying logging platform has stabilized, and some log sources have been restored and are successfully ingesting logs. The team is working to restore the rest of the log sources now.

+1 more updates

Increased error rates for plan upgrades

major

Apr 2, 08:28 AM→Apr 2, 09:24 AMresolved

Apr 2, 09:24 AM

resolved — The issue causing increased error rates during plan upgrades has been resolved. All systems are operating normally.

Apr 2, 09:05 AM

monitoring — A fix has been applied, and we are monitoring to ensure stability.

Apr 2, 08:40 AM

identified — We have identified the cause of increased error rates affecting plan upgrades and are working on a fix. We will provide further updates as progress is made.

+1 more updates

Degraded logs ingestion

major

Apr 1, 12:13 AM→Apr 1, 01:11 AMresolved

Apr 1, 01:11 AM

resolved — Log ingestion has recovered and the incident is considered resolved. Some log data was lost during the incident between around 11pm to 11:45pm ETC on March 31.

Apr 1, 12:47 AM

monitoring — We have identified the issue and a fix is in place. We will continue to monitor to ensure stability.

Apr 1, 12:13 AM

investigating — We are seeing degradation of logs and are currently investigating the cause of this issue.

March 2026

Supabase dashboard experiencing intermittent errors in Europe region

minor

Mar 27, 05:58 PM→Mar 27, 06:43 PMresolved

Mar 27, 06:43 PM

resolved — We have confirmed that project creation has returned to normal.

Mar 27, 06:18 PM

monitoring — Project creation has returned to normal. We continue to actively monitor and operate our platform for stability and consistency.

Mar 27, 05:58 PM

identified — We have experienced problems with project creation, the issue has been identified and mitigation steps have been implemented.

Degraded Log Ingestion

minor

Mar 27, 03:13 PM→Mar 27, 05:03 PMresolved

Mar 27, 05:03 PM

resolved — Log ingestion has returned to normal

Mar 27, 04:17 PM

monitoring — Our capacity mitigations have taken effect and ingestion has returned to normal. Customers should see logs returning to normal.

Mar 27, 04:12 PM

identified — We continue to increase capacity in targeted areas to mitigate log ingestion degradation. It will take some time for the ingestion backlog to be eliminated.

+3 more updates

Realtime services unavailable

major

Mar 26, 11:41 PM→Mar 27, 02:58 AMresolved

Mar 27, 02:58 AM

resolved — The issue has been resolved and Realtime services have returned to normal.

Mar 27, 02:48 AM

monitoring — The fix has been implemented and we’re monitoring to ensure stability.

Mar 27, 01:44 AM

identified — We appreciate your patience as we continue to work on a fix. We will provide updates as they become available.

+4 more updates

Branching access issues

minor

Mar 24, 03:13 PM→Mar 24, 03:56 PMresolved

Mar 24, 03:56 PM

resolved — Branching access has returned to normal, this issue is resolved.

Mar 24, 03:27 PM

monitoring — The fix has been implemented and branching access has returned to normal.

Mar 24, 03:13 PM

identified — We are aware of an issue affecting users creating/updating branches. A permission error in our branching workflow is causing failures for all branches. We have identified the root cause and a fix is b...

Degraded Logging Ingestion impacting all regions

minor

Mar 23, 04:28 PM→Mar 23, 06:56 PMresolved

Mar 23, 06:56 PM

resolved — This issue is now resolved. All logging ingestion has resumed in all regions.

Mar 23, 05:05 PM

monitoring — A fix has been implemented. The system is now operating normally, and we will continue to monitor.

Mar 23, 04:38 PM

identified — The cause of the issue has been identified. Our engineering team is working on a fix.

+1 more updates

Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

minor

Mar 23, 02:16 PM→Mar 23, 03:42 PMresolved

Mar 23, 03:42 PM

resolved — Error rates have returned to normal. This incident has been resolved.

Mar 23, 02:32 PM

monitoring — We carried out a controlled redeployment of the affected services to restore stability. The system is now operating normally, and we will continue to monitor.

Mar 23, 02:16 PM

investigating — We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

Project creation failures across multiple regions

major

Mar 19, 08:55 PM→Mar 19, 10:00 PMresolved

Mar 19, 10:00 PM

resolved — Project creation in all regions are now successful.

Mar 19, 09:21 PM

monitoring — A fix has been implemented and we are monitoring the results.

Mar 19, 09:08 PM

identified — We have identified the issue and a fix is underway.

+1 more updates

Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region

minor

Mar 18, 04:27 PM→Mar 18, 06:21 PMresolved

Mar 18, 06:21 PM

resolved — The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services.

Mar 18, 05:53 PM

identified — The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.

Mar 18, 05:30 PM

investigating — We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region. While we are still observing a higher-than-normal level of errors, initial findin...

+2 more updates

Issues propagating Postgres configuration updates

minor

Mar 17, 04:50 AM→Mar 17, 07:41 AMresolved

Mar 17, 07:41 AM

resolved — This incident has been resolved.

Mar 17, 07:07 AM

monitoring — A fix has been implemented and we are monitoring.

Mar 17, 05:11 AM

identified — We have identified the root cause and are currently working on a fix.

+1 more updates

Increased error rate related to Connection Pooler in ap-northeast-2 (South Korea)

minor

Mar 13, 08:54 AM→Mar 13, 10:19 AMresolved

Mar 13, 10:19 AM

resolved — Error rates have returned to normal, and connectivity has stabilised.

Mar 13, 09:40 AM

monitoring — A fix has been implemented and error rates have reduced. Our team is actively monitoring the system to ensure stability.

Mar 13, 09:25 AM

investigating — We continue to investigate increased error rates relating to the connection pooler in ap-northeast-2 (South Korea) We will provide further updates as information becomes available.

+1 more updates

Degraded Logging Ingestion impacting all regions

minor

Mar 12, 12:51 PM→Mar 12, 01:53 PMresolved

Mar 12, 01:53 PM

resolved — The issue affecting Supabase Log ingestion has been fully resolved. Log ingestion across all services has returned to normal operation.

Mar 12, 12:54 PM

monitoring — A fix has been implemented and log ingestion is now stabilising. We are seeing recovery across the affected services. Our team is actively monitoring the system to ensure ingestion fully returns to n...

Mar 12, 12:51 PM

investigating — We are currently investigating an issue affecting Supabase Logs that is causing partial log ingestion for some services. Users may experience delays or errors when accessing logs related to Realtime,...

Projects failing to be created

major

Mar 11, 06:08 PM→Mar 11, 07:09 PMresolved

Mar 11, 07:09 PM

resolved — Project creation recovery has been confirmed across all regions. Regional dashboards show error rates returned to normal, and previously failing project creation operations are succeeding again.

Mar 11, 06:47 PM

monitoring — A fix has been implemented and we are seeing project creation recovery across regions. We're moving the incident to monitoring while we confirm full stability.

Mar 11, 06:25 PM

identified — We have identified the root cause and are currently working on a fix.

+1 more updates

Storage errors in EU-Central-2

minor

Mar 7, 08:12 PM→Mar 7, 09:56 PMresolved

Mar 7, 09:56 PM

resolved — All storage operations have returned to normal.

Mar 7, 09:16 PM

monitoring — The upstream incident has been resolved and we have not observed any additional errors. We will continue to monitor our storage infrastructure for continued stable operations.

Mar 7, 08:44 PM

identified — We are observing storage error rates returning to normal.

+2 more updates

Elevated Management API error rates across all regions

major

Mar 7, 02:48 PM→Mar 7, 04:46 PMresolved

Mar 7, 04:46 PM

resolved — Error rates have returned to baseline and all regions are operating as expected.

Mar 7, 04:16 PM

monitoring — We've seen error rates return to normal levels, and all regions are now holding steady. We will continue to monitor to make sure things remain stable.

Mar 7, 03:51 PM

identified — We are continuing to see some periodic spikes in error rates; however, total rate of errors are decreasing across most regions. We're continuing efforts to get all systems back to green. When error r...

+4 more updates

Subscription Plan changes currently unavailable

minor

Mar 7, 12:10 PM→Mar 7, 01:58 PMresolved

Mar 7, 01:58 PM

resolved — This incident has been resolved.

Mar 7, 01:23 PM

monitoring — A fix has been applied by our upstream provider and we have re-enabled subscription plan upgrades and paid organization creation. We are monitoring to confirm full recovery.

Mar 7, 12:45 PM

investigating — We have temporarily disabled subscription plan upgrades and paid organization creation while we work with our upstream billing provider to resolve the issue. We’ll provide an update as soon as we have...

+1 more updates

Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2

major

Mar 6, 02:26 PM→Mar 6, 07:36 PMresolved

Mar 6, 07:36 PM

resolved — Both regions are now working as usual.

Mar 6, 03:56 PM

monitoring — Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised. We will continue to monitor the systems closely to ensure stability.

Mar 6, 03:46 PM

identified — Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts. We are currently rolling out the fix to the ap-northeast-2 (Seoul) region. Further updates will be pro...

+3 more updates

Supabase Dashboard and Management API inaccessible

critical

Mar 4, 10:16 AM→Mar 4, 01:00 PMresolved

Mar 4, 01:00 PM

resolved — This incident has been resolved.

Mar 4, 10:36 AM

monitoring — Service has been fully recovered and we're continuing to monitor.

Mar 4, 10:30 AM

identified — We've identified and reverted the change that is causing the issue, and are in the process of recovering the systems affected. Existing projects are unaffected.

+1 more updates

Database issues in us-east-2

minor

Mar 3, 02:10 AM→Mar 3, 06:31 AMresolved

Mar 3, 06:31 AM

resolved — Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners.

Mar 3, 04:08 AM

monitoring — We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment.

Mar 3, 03:14 AM

identified — We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and cli...

+2 more updates

February 2026

Users Experiencing Network Connectivity Problems (India Region)

none

Feb 24, 02:46 PM→Mar 4, 09:02 PMpostmortem

Mar 31, 10:05 PM

postmortem — Read more about incident and similar incidents in our new blog post about [Navigating Regional Network Blocks](https://supabase.com/blog/navigating-regional-network-blocks).

Mar 4, 09:02 PM

resolved — We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Informat...

Mar 3, 07:12 PM

monitoring — We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Informat...

+13 more updates

Increased Edge Function Errors across multiple regions

major

Feb 28, 01:03 PM→Feb 28, 02:29 PMresolved

Feb 28, 02:29 PM

resolved — The issue affecting Edge Functions has now been fully resolved, and users have reported Edge Functions operating as expected. The root cause was a denial-of-service event that led to elevated error ra...

Feb 28, 02:09 PM

monitoring — The fix has been implemented and early indicators suggest it has resolved the 504 errors affecting Edge Functions. We are continuing to monitor system performance closely to ensure stability and confi...

Feb 28, 02:04 PM

identified — We believe we have identified the underlying cause of the 504 errors affecting Edge Functions across multiple regions. The team are currently implementing corrective measures to address the issue and ...

+2 more updates

Delays in pausing projects and making read replica configuration changes in EU-West-1

minor

Feb 25, 11:58 PM→Feb 26, 02:23 AMresolved

Feb 26, 02:23 AM

resolved — Things have remained stable, and all systems looking good. This issue has been resolved.

Feb 26, 01:53 AM

monitoring — Project Pause requests and Replica configuration changes are back to normal. We're monitoring to ensure stability.

Feb 26, 01:28 AM

identified — The job queue is continuing to decrease. The team is making further changes to help it complete faster. Note: The impact of this remains project pause and read replica configuration change delays. Al...

+3 more updates

Some Users Experiencing Connectivity issues via Supavisor in EU-Central-1

major

Feb 26, 12:12 AM→Feb 26, 01:14 AMresolved

Feb 26, 01:14 AM

resolved — Systems have remained stable, and we are confident the issue has been resolved.

Feb 26, 12:47 AM

monitoring — Connection and query times are back to normal levels. We will continue monitoring to ensure stability.

Feb 26, 12:12 AM

investigating — The team is investigating connectivity issues via Supavisor in EU-Central-1. Data API, direct connections, and connections via the dedicated pooler are unaffected. You can read more on the dedicated...

Resource Metrics Collection Delays in US-West-2

major

Feb 23, 01:36 AM→Feb 23, 08:11 AMresolved

Feb 23, 08:11 AM

resolved — Metrics collection continues to operate normally in US-West-2, and full metrics collection has been fully restored with no blips in stability.

Feb 23, 06:26 AM

monitoring — The team has deployed additional capacity and has restored metrics collection operations. All metrics collection in region is fully operational and the team is actively monitoring the fixes deployed.

Feb 23, 04:04 AM

identified — The team has deployed a fix and is actively monitoring recovery of partially degraded metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing ...

+3 more updates

Errors across logs and observability services

critical

Feb 20, 08:37 PM→Feb 20, 11:56 PMresolved

Feb 20, 11:56 PM

resolved — Things have remained stable, and we are confident that things are now resolved. The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on ...

Feb 20, 11:30 PM

monitoring — The configuration update has brought error rates and stability back to normal, all logging and observability data should now be accessible. The impact of this event was limited to log visibility and ...

Feb 20, 11:16 PM

identified — The team is currently pushing a configuration change we hope will finish stabilizing the analytics services. We will continue to update as we have more information. Projects and services are up and r...

+7 more updates

Degraded Supavisor performance in us-east-1

none

Feb 16, 11:48 PM→Feb 17, 12:29 AMresolved

Feb 17, 12:29 AM

resolved — Performance has returned to normal levels. This incident has been resolved.

Feb 17, 12:16 AM

monitoring — We've identified degraded performance in a Supavisor cluster resulted in elevated connection latency and increased p99 response times. The problematic node has been replaced and performance is returni...

Feb 16, 11:48 PM

investigating — Starting from Feb 22:55 UTC, degraded performance in one of our Supavisor clusters resulted in elevated connection latency and increased query p99 response times.

Elevated Supavisor query response times in us-east-1

minor

Feb 15, 10:00 PM→Feb 16, 01:00 AMresolved

Feb 16, 01:35 AM

resolved — Degraded performance in a Supavisor cluster resulted in elevated connection latency and increased p99 response times between 2026-02-15 22:00 and 2026-02-16 01:00. The problematic node was replaced an...

Outage in US-East-2 (Ohio)

major

Feb 12, 09:32 PM→Feb 13, 01:53 AMpostmortem

Feb 14, 03:26 AM

postmortem — We’ve published a [post-mortem on our blog](https://supabase.com/blog/supabase-incident-on-february-12-2026).

Feb 13, 01:53 AM

resolved — Service has been fully restored. All impacted jobs have been requeued and are currently processing normally. We will be publishing a public post-mortem with additional details about this incident.

Feb 13, 01:26 AM

monitoring — The revert of the change helped and most of the metrics are back to the pre incident levels. We are requeuing failed jobs and monitoring to make sure the issue doesn’t come back.

+5 more updates

Regional network issues in Yemen

none

Feb 3, 09:38 PM→Feb 10, 09:28 PMresolved

Feb 10, 09:28 PM

resolved — This issue is now resolved.

Feb 10, 03:24 PM

identified — We continue to work with network vendors to mitigate this issue. In the interim, using a VPN will give you access to your Supabase project.

Feb 4, 06:08 PM

identified — We are actively working with network vendors to mitigate this issue.

+1 more updates

High connection latency via shared Pooler in us-west-1

minor

Feb 9, 05:39 PM→Feb 9, 07:34 PMresolved

Feb 9, 07:34 PM

resolved — This incident has been resolved.

Feb 9, 06:37 PM

monitoring — The team noticed that some connection pools had workers stuck as a consequence of the previous issue. This could cause query failures. Stuck workers were now restarted.

Feb 9, 05:56 PM

monitoring — We've removed the problematic cluster node and latency returned to the normal level. We are now monitoring.

+1 more updates

Edge Function issues when using supabase-js@2.95.0

minor

Feb 5, 06:09 PM→Feb 6, 01:00 AMresolved

Feb 6, 01:00 AM

resolved — Function deploys are working normally now. We are resolving this incident.

Feb 5, 11:53 PM

monitoring — esm.sh maintainers have implemented a fix which should unblock deploys of Edge Functions that were importing supabase-js from esm.sh.

Feb 5, 09:36 PM

identified — We’ve attempted several fixes on the npm registry side, but the esm.sh issue persists. We are continuing to investigate. In the meantime, use npm: or jsr: specifiers, or jsdelivr as an alternative CDN...

+3 more updates

Storage upload via S3 Protocol is degraded

minor

Feb 5, 08:21 PM→Feb 5, 09:04 PMresolved

Feb 5, 09:04 PM

resolved — We have deployed a fix and confirmed that the issue is fully resolved.

Feb 5, 08:21 PM

investigating — We are aware of issues with S3 upload protocols affecting projects in us-east-1 and ap-northeast-2. We are working on a fix.

Realtime cluster instabilty

minor

Feb 5, 02:13 PM→Feb 5, 03:49 PMresolved

Feb 5, 03:49 PM

resolved — This incident has been resolved.

Feb 5, 02:40 PM

investigating — We've observing a recovery for latency and error rates after the capacity increase. We will be monitoring to make sure the problem was fully resolved.

Feb 5, 02:13 PM

investigating — We're seeing elevated errors and latency in Realtime service. We are already working on increasing cluster capacity to stabilize it.

Reports of DNS lookup errors for some customers in the United States

major

Feb 5, 01:52 AM→Feb 5, 06:49 AMresolved

Feb 5, 06:49 AM

resolved — This incident has been resolved.

Feb 5, 03:48 AM

monitoring — Our upstream provider has pushed a fix, and requests seem to be back to normal now. According to data from our partner, users in the US South were largely affected, with users in and around Texas bein...

Feb 5, 03:22 AM

identified — Our upstream provider has identified the specifc issues with DNS resolution and has begun working on a fix. Projects and the underlying infrastructure are unaffected, and remain running and available...

+3 more updates

Issues with setting DNS for newly created and unpaused projects

major

Feb 4, 05:55 PM→Feb 4, 07:17 PMresolved

Feb 4, 07:17 PM

resolved — This issue is now resolved.

Feb 4, 06:48 PM

monitoring — New project creation and unpauses are now available. We are working on remediation of projects impacted during the incident and will continue to monitor.

Feb 4, 06:14 PM

identified — We have identified the issue and are working towards a resolution.

+1 more updates