SupabaseDegraded logs ingestion
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.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
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.
Resolved
A fix has been deployed and this issue is now resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Users should no longer experience issues submitting Anyscale Jobs.
Resolved
This incident has been resolved.
Resolved
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.
Resolved
After a period of monitoring we have not observed a recurrence of the issue and are considering it resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue affecting WRITER Agent has been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. We are continuing to monitor. Please retry any failed /user/* requests.
Resolved
This incident has been resolved.
Resolved
A small number of customers experienced issues where custom domains were not appearing as expected in the publishing modal between Mar 30, 18:00 UTC and Mar 31, 18:30 UTC. A fix has been implemented, and we’re no longer seeing customer impact related to this issue. Thank you for your patience while we worked to resolve this.
Resolved
This incident has been resolved.
Resolved
Acuity Scheduling is now fully operational.
Resolved
On March 24, 2026, between 15:57 UTC and 19:51 UTC, the Microsoft Teams Integration and Teams Copilot Integration services were degraded and unable to deliver GitHub event notifications to Microsoft Teams. On average, the error rate was 37.4% and peaked at 90.1% of requests to the service -- approximately 19% of all integration installs failed to receive GitHub-to-Teams notifications in this time period.<br /><br />This was due to an outage at one of our upstream dependencies, which caused HTTP 500 errors and connection resets for our Teams integration.<br /><br />We coordinated with the relevant service teams, and the issue was resolved at 19:51 UTC when the upstream incident was mitigated.<br /><br />We are working to update observability and runbooks to reduce time to mitigation for issues like this in the future.
Resolved
This incident has been resolved.
Resolved
Error rates have dropped and functionality is restored.
Resolved
A routine infrastructure configuration change inadvertently blocked outbound webhook requests. Because webhooks are delivered once and not retried, any events during the affected window were lost and cannot be replayed. We've rolled out a fix and confirmed webhook delivery is working normally again. We're adding dedicated monitoring for webhook delivery to catch this kind of issue earlier in the future. The affected window was approximately 11:55 UTC to 17:30 UTC, with exact timings differing per site.
Resolved
Engineering team has investigated and resolved an issue related to the Linked Audience Builder. Specifically, traits could not be selected. This is now resolved as of 4:43 PM UTC.
Resolved
On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues.
Resolved
We’ve resolved the issue causing intermittent Internal Server Errors (HTTP 500) for some Enterprise customers when editing Zaps that use app approvals. Our teams implemented a fix and confirmed recovery. If you continue to experience issues editing affected Zaps, please contact support. https://zapier.com/app/get-help
Resolved
No impact observed to customers
Resolved
The issue has been resolved. We have switched traffic back to our main provider. Users can expect Deep Search to function normally.
Resolved
We have validated that the fix resolved the issue and customers are no longer seeing errors when accessing the org settings page in the Contentful WebApp.
Resolved
All impacted services have now fully recovered.
Resolved
Impact Summary Between 13:33 UTC and 14:30 UTC on March 31, 2026, customers may have experienced that some CreateProject requests in the azure westus3 region returned errors. Impact duration was 57 minutes. Other API operations were unaffected. During remediation of a hardware degradation event, a configuration issue temporarily reduced the availability of project creation in the westus3 region. The issue was identified and resolved by the team. The incident is now closed, and no further updates are planned. We apologize for any inconvenience this may have caused.
Resolved
This issue has now been resolved.
Resolved
This incident has now been resolved and the service is now fully operational.
Resolved
The root cause was an incompatibility in how ElevenLabs handled mid-dialog re-INVITEs. When SIP providers sent re-INVITEs, ElevenLabs responded with 488, which some providers treat as fatal, issue a BYE, and terminate the call. Per RFC 3261, a 488 should not necessarily result in session termination, but provider behaviour varied.
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
The incident is now resolved and the system is full operational. During this incident step.fetch and step.ai.infer were failing due to a bug causing empty request bodies to be returned. The root cause was determined, the system was rolled back and a fix will be rolled out today.
Resolved
Publishing was not working for a small amount of users who got errors when publishing. The issue has now resolved
Resolved
This incident has been resolved.
Resolved
The incident is resolved and the Lovable agent's performance has returned to normal.
Resolved