PlaidAPI downtime
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
A fix has been deployed by our engineers, and log stream performance is improved again.
Resolved
This issue is now resolved.
Resolved
The issue has been resolved
Resolved
This incident has been resolved.
Resolved
Hey There, We recently experienced a brief service disruption affecting Inbox 2.0 and Analytics. This occurred between 12:53pm and 1:23pm PST. While analytics data affected by this disruption has been restored, you may encounter some missing inbound content within Inbox 2.0 during this time. As of 1:23pm PST, all services are functioning as expected. Thanks for your patience and understanding while our team sorted this out
Resolved
This incident has been resolved.
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
The sandbox management should be fully working now.
Resolved
Service has recovered.
Resolved
We have confirmed full functionality of both EU and IN residency webpages.
Resolved
The configuration change has been deployed and we have seen stability with Sidekiq and pipeline processing. This incident is now resolved.
Resolved
The issue with the AI Interview Companion Enable for all Jobs settings in Lever has been resolved. The incident occurred from 11:59 am PST 3/6/2026 - 10 am PST 3/9/2026. There should be no further impact at this time, but please reach out to us at Support if any additional assistance is needed: https://help.lever.co/hc/en-us/requests/new
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
GitHub has resolved the webhook degradation. Preview builds and redeploys should now function normally.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
Jamf Pro 11.25.2 deployment to all standard Pro instances is complete.
Resolved
On March 6, between approximately 13:44–14:07 UTC, some databases experienced elevated latency and connection errors in the Tokyo \(ap-northeast-1\) region. The issue was caused by a sudden spike in traffic that significantly increased network utilization and connection load on a subset of nodes. Our team mitigated the incident by scaling up capacity in the region and redistributing load across additional nodes. Service recovered once the additional capacity was brought online. Resolution We have increased the number of machines in the Tokyo region to provide additional headroom and reduce the likelihood of similar incidents during traffic spikes. Next Steps We are continuing to review capacity safeguards and connection-handling limits to improve resilience against sudden traffic surges.
Resolved
The issue affecting chat requests in the Editor has been resolved and services have been stable for over 3 hours.
Resolved
Issues affecting the NGC Catalog service have been resolved and the service is operating normally.
Resolved
The issue should be resolved.
Resolved
We have confirmed with affected clients and in our analytics that SIP trunking functionality is now fully restored.
Resolved
We have resolved the issue.
Resolved
The issue affecting project creation in Lovable Cloud has been resolved. Our team identified the cause and implemented a fix, and project creation is now operating normally. We will continue to monitor the system to ensure stability. Thank you for your patience while we worked to resolve the issue.
Resolved
All storage operations have returned to normal.
Resolved
This incident has been resolved.
Resolved
From 5:50PM 3/6 UTC to 1:15AM 3/7 UTC, there was a bug that would cause library publishes to be incorrect. Files pulling in those updates would experience errors related to conflicting properties in variants. The issue with library publishes has been resolved. If you continue to see this error, please re-publish the affected components (by making a small change) and re-update the consuming files to apply the fix.
Resolved
Data operations have been restored.
Resolved
Error rates have returned to baseline and all regions are operating as expected.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The system remains stable. We will continue monitoring and investigate the service degradation happened between 8AM and 10AM CET.
Resolved
Engineers have resolved the issue with clips not having audio. Any new clips will function as expected. Impacted clips created during the incident window are not retroactively corrected, but can be re-created from the original asset.
Resolved
This incident has been resolved.
Resolved
GitHub has resolved the webhook degradation. Preview builds and redeploys should now function normally.
Resolved