Pinecone[Serverless][AWS][us-west-2] Unavailability for some read path operations for some indexes
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
Resolved - At 9:49 AM PST, we experienced login API request failures due to errors on an RDS database in the US region. The database failover completed successfully, and all systems were fully operational by 10:00 AM PST.
Resolved
This incident has been resolved.
Resolved
The site loading issue affecting users in Brazil is now resolved. The issue was related to external network conditions with third-party Latin American ISP providers. Sites are now loading normally. No further action is required. We will continue monitoring to ensure stability.
Resolved
Webflow’s third-party provider has resolved issues on their end, and Webflow is fully operational. No user action is required at this time.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Services have returned to normal for all users.
Resolved
The Push API delay issue is resolved. The backlog of events not sent since 01:07 UTC is now being delivered and will clear over the next few hours. We’re monitoring until completion.
Resolved
**Incident**: Around 2025-08-17 23:35, a conflict occurred between two database management systems. For most Asana customers, database locks prevented execution of background actions, automations, and webhooks were delayed. **Impact**: Users experienced delays in asynchronous operations, including automations and webhooks. Core application functions remained available and operational throughout the incident. No customer data was lost. The incident lasted approximately 2 hours, after which delayed operations ran normally. **Moving forward**: Asana engineers completed an investigation into the root cause, and have implemented changes to prevent the conflict between these systems. We are also reviewing our upgrade and management processes to be resilient against similar issues in the future. Our metric considers a weighted average of uptime experienced by users at each data center. The number of minutes of downtime shown reflects this weighted average.
Resolved
Showcases are now fully operational.
Resolved
# **What happened** On August 19, between approximately 12:45 PM and 2:00 PM EDT, Vimeo Enterprise customers were unable to access their video libraries or play videos through our China delivery solution. # **What caused it** Our third-party hosting provider experienced an outage that disrupted data access between Mainland China and other regions. # **How we responded** Our internal monitoring systems brought this issue to our attention. We began investigating it immediately, determined that the cause was external, and confirmed the outage with our provider once their ability to provide status updates was restored. # **What we’re doing to prevent a recurrence** While outages caused by external infrastructure are outside our direct control, we’re improving our monitoring to include a continuous health check on the provider’s service, so that we know from the outset whether the outage is external.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue where users were unable to preview documents has been resolved. The incident occurred from 8 AM to 10:35 AM PT. Please refresh Lever in your browser. 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
Braze Engineers continue to monitor service health. Both US06 and EU02 services are operating within normal operational bounds. This incident has been resolved.
Resolved
Bitbucket Cloud is fully recovered.
Resolved
A misconfiguration in us-east-1-cell-2 resulted in stuck suspend_compute operations for a subset of customers with databases that attempted to scale to zero in this cell during the incident timeframe. The issue has been fully resolved. All affected components are operating normally again.
Resolved
**Incident Narrative** On July 1, 2025, at 02:36 UTC, a service disruption occurred leaving Atlassian customers unable to access Bitbucket. The primary issue was identified as an inconsistent network access control list \(ACL\) rule, which inadvertently blocked certain IP ranges necessary for file system access. This network misconfiguration caused a service outage until the rule was corrected at 04:35 UTC, restoring normal service operations. **Root Cause** The root cause of the incident was traced to a network ACL misconfiguration during a routine update. A race condition in the deployment software led to an inconsistent state. This left a gap in network traffic management, disrupting essential services and resulting in inaccessibility of Bitbucket functionalities. **Mitigators** To restore service, the team repaired the inconsistent network ACL configuration, recreated the missing network ACL rule, re-establishing connections to the affected file systems. **Actions** In response to the incident, we have implemented additional mechanisms to help prevent the inconsistent network configuration and better ensure the expected network ACL rules remain intact, including during deployment.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
From 14:30 UTC to 14:50 UTC, some users may have experienced issues saving changes while working in the Designer.
Resolved
This incident has been resolved.
Resolved
Between 12:37 UTC and 12:50 UTC, an overload in the connection proxying system resulted in instability for a subset of databases. The root cause was identified as a misconfiguration in the routing rules, which caused certain requests to experience timeouts during the initial phase of a gradual deployment. Upon detection, the deployment was immediately rolled back, restoring normal service. We are reviewing our deployment and configuration validation processes to prevent similar issues in the future.
Resolved
The fix for this issue has been deployed and has performed as expected during ongoing monitoring. This issue is now resolved.
Resolved
Between 18:45 and 19:35 UTC we experienced degraded functionality for Loom. The issue has been resolved and the service is operating normally.
Resolved
The issue has been identified and a fix has been implemented.
Resolved
The issue has been resolved, Anyscale Metrics are now operating normally. Please note: customers may see a gap in metric data for the duration of the incident (August 14, 2:57 PM PDT to August 14, 4:13 PM PDT).
Resolved
This incident has been resolved.
Resolved
The incident is now fully resolved.
Resolved
The site loading issue affecting users in Brazil is now resolved. The issue was related to external network conditions with third-party Latin American ISP providers. Sites are now loading normally. No further action is required. We will continue monitoring to ensure stability.
Resolved
Integration test is complete
Resolved
The issue causing Lever's Sandbox environment to go down has been resolved. The incident occurred from 10:45 AM to 12:36 PM PT on 8/14/2025. 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
The site loading issue affecting users in Brazil is now resolved. The issue was caused by problems with 3rd party Tier 2 Latin American ISP provders. Sites are now loading normally, the issue was fixed by the 3rd party provider. No further action is required. We will continue monitoring to ensure stability.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
For a period of approximately 1h30, from 9:34 UTC to 11:08 UTC, our ingestion of events in the EU region was delayed. All events were eventually processed, but for that duration, triggers, SLOs, and regular queries could have seen missing data for a brief period of time. As we re-balanced traffic loads and scaled the system, ingestion caught up and data has since then been fully available. We are still actively working on improving the scaling margins and behaviors of the EU instance of Honeycomb to better sustain load variations we are observing at this time.
Resolved