Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 3, 2026

  1. UpstashUpstash Console login issue

    We experienced a brief issue affecting access to the Upstash Console. Our team quickly identified the cause and resolved the issue within minutes. The console is now operating normally.

    Resolved

  2. FirecrawlAPI is degraded

    Between 07:12 and 07:28 UTC today, a network issue in our upstream ISP caused a portion of jobs to fail. The issue resolved at 07:28 UTC and we are working on additional redundancy to avoid similar issues in the future.

    Resolved

  3. OpsgenieIssues with Microsoft Teams notifications for Opsgenie customers

    On August 19, we identified an issue affecting the delivery of Microsoft Teams notifications for Opsgenie standalone customers. The root cause was attributed to an operational error caused by our external partner, and they have taken corrective measures to restore services. If you are still experiencing issues, please follow these steps to restore your integration: https://support.atlassian.com/opsgenie/docs/restore-the-opsgenie-microsoft-teams-v2-integration/. If you require further assistance, please reach out to Atlassian Support via support.atlassian.com/contact.

    Resolved

  4. SnowflakeINC20000175

    Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site:  [https://community.snowflake.com/s/article/INC20000175](https://community.snowflake.com/s/article/INC20000175)

    Resolved

  5. BufferIssue with Editing Drafts and Posts

    We’ve continued monitoring the fix, and everything remains stable. This incident is now fully resolved. Thank you for your patience while we worked through this. If you’re still experiencing any issues, please reach out to us at hello@buffer.com: mailto:hello@buffer.com.

    Resolved

Sep 2, 2026

  1. ExpoElevated Linux worker queue times

    A fix was deployed at 2:50pm PT/5:50pm ET. The job queue has been running as expected. The root cause of this incident is that a new version of a cache needed more vCPUs than it was given, and we have increased the CPU count as the immediate fix along with additional monitoring for CPU usage on these cache instances.

    Resolved

  2. HarnessEntities in Harness are not loading on in Prod3

    ## Summary Between August 27 and August 28, 2026, customers experienced an issue where some pipelines, deployments, and related resources appeared as not found in the Harness UI and API, even though the underlying data remained intact. ‌ The issue occurred during a planned internal infrastructure update that affected communication between internal platform services. As a result, requests that depended on account, organization and project scope resolution were unable to complete successfully, which led to incorrect not found responses being returned to customers for existing entities. ‌ Engineering identified the issue, rolled back the change, and restored normal service. No customer data was lost or deleted during the incident. ‌ ## Root Cause The issue was caused by a configuration error introduced during a planned internal service routing update in Production. An internal platform service responsible for resolving account, organization, and project context was unable to validate requests from other Harness services after the change was applied. Because that validation step is required before many entity reads and pipeline-related actions can proceed, the failed requests surfaced to customers as not found errors for resources that continued to exist normally. The issue was limited to the affected production environment and was resolved by reverting the change and restoring the previous service communication path. ‌ ## Impact * Some customers saw existing pipelines, deployments, and related entities appear as not found in the UI and API. * Some pipeline-related operations, including execution progression, webhook-triggered starts, scheduled trigger evaluation, and entity listing, were temporarily disrupted. * The issue affected availability and visibility of existing entities, but it did not remove data or change customer configurations. * No unauthorized access occurred, and no customer data loss was observed. ## Remediation * **Immediate:** Reverted the infrastructure configuration update and restored the previously working service communication path. * **Recovery validation:** Verified that affected entity lookups, pipeline operations, and dependent APIs were functioning normally after rollback. * **Permanent:** Corrected the configuration handling associated with the update so similar issues do not interfere with service-to-service authentication in future rollouts. ## Action Items To prevent such issues from happening again, Harness will  1. Improve configuration validation by enhancing the pre-deployment tests to verify internal service communication before shifting production traffic. 2. Enhance monitoring and alerting for internal authentication failures so issues can be detected earlier. 3. Improve error handling so dependency failures are less likely to appear to customers as resource not found errors.

    Resolved

  3. AsanaAsana full outage for some users (2 hours, 25% outage)

    We’ve been working to add a caching layer to our update pipeline, tuning it carefully and rolling it out gradually. On Wednesday, August 26 we enabled it for most use cases, and it initially performed well. On Monday, August 31, a combination of unrelated infrastructure changes and peak traffic pushed the cache past its scaling limits. Once that threshold was crossed, the cache became unusable, and many pods serving read traffic for the Asana application could no longer serve it. We mitigated the incident by reverting the system to use the previous, non-cached code path. The revert was successful, but recovery took longer than we would expect for this class of issue. A fuller analysis is underway. We will follow up with root causes, action items, and improvements, including why recovery took as long as it did. We were fully down for about 25% of our users, for 2 hours, 15 minutes.

    Resolved

  4. PaddleReport downloads unavailable in the Paddle Dashboard

    The incident affecting report downloads in the Paddle Dashboard has been fully resolved. Our engineers deployed a fix, and the generated reports can now be downloaded as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com "sellers@paddle.com": mailto:sellers@paddle.com.

    Resolved

Older incidents