Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jul 30, 2025

Jul 29, 2025

  1. Help ScoutWeb App Performance Issues

    We are no longer seeing errors with attachments or Beacon, and all inbound emails have been successfully received. If you continue to experience any issues, please reach out to our team and let us know. Apologies for the inconvenience today, and thank you for your patience!

    Resolved

Jul 28, 2025

  1. PandaDocDocument access in editor

    We're all set! PandaDoc is working properly and the incident has been fully resolved. If you continue to experience issues with this, please contact our Support team (https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support).

    Resolved

  2. TypeformTypeform Builder- Can't edit forms

    We are glad to inform you that the fix has been implemented and the incident resolved. We will run a problem investigation to understand what happened and how to prevent it from happening again. Thanks for your understanding & sorry for any inconvenience this has caused.

    Resolved

Jul 27, 2025

Jul 26, 2025

Jul 25, 2025

  1. CerebrasService Unavailable - Resolved

    Llama-3.3-70B, DeepSeek-R1-Distill-Llama-70B, Qwen-3-32B (7/25/2025 from 1:17 PM to 1:41 PM PT) were unavailable. We restored normal service performance at 1:41 PM PT on July 25th.

    Resolved

  2. JamfJCDS Outage

    **Detailed Root Cause Analysis Report: JCDS Outage**   **Incident Date:** July 17, 2025  **Duration:** 29 minutes    **Impact:**  Global disruption of Jamf Cloud Distribution Service \(JCDS\)  **Summary and Timeline**  On July 17, 2025, a JCDS outage impacted customers globally when a parameter value did not update, blocking content distribution to end-user devices. Jamf restored full service within 29 minutes.  **Root Cause & Timeline**  * **Root Cause:** The ‘CsaIssuer’ parameter set in non-production was different than the way it was set in production.   * **Key Events:**   * 11:43 UTC – JCDS was updated to support authentication through the Tyk API gateway using both ‘tenant\_id’ and ‘Instance\_id’ values. This will support the new API gateway for customers who have not yet adopted tenantID.   * 11:45 UTC – Incident triage initiated. Post-deployment alerts investigated. Root cause identified.  * 12:12 UTC – Initiated rollback to the prior JCDS deployment. Services restored.    * 12:45 UTC – Continued monitoring confirmed rollback was successful and Jamf Pro instances were communicating successfully with JCDS.  **Business & User Impact**  * Unable to distribute content to devices using the JCDS  * Affected products: Jamf Pro  * Services affected: Jamf Cloud Distribution Service \(JCDS\).  JCDS is a cloud distribution point utilizing server-less deployment architecture leveraging AWS Lambdas to manage file uploads and downloads. Since JCDS is a serverless stack and decoupled from Jamf Pro, changes are deployed to JCDS without customer facing maintenance windows. This type of service does not require downtime for new deployments or upgrades. No customer data loss occurred from this outage.   **Gaps Identified**  * The cloud formation stack’s URL parameter was not updated when the JCDS deployment pipeline ran for production. The team discovered that modifying the default value in the pipeline template does not automatically update the value in the main template.  * Pre-production testing did not reveal this parameter update behavior.   **Remediation Items & Next Steps**  * The status page was updated to reflect the outage and ensure customer awareness - Complete   * The JCDS deployment was rolled back - Complete     * Change the pipeline so parameters are passed in the same way in each environment.   * Review rollback procedures to ensure for any future deployment issues.  * Enhance pipeline monitoring by improving alerts when pipeline tests fail.    * Fine tune additional JCDS alerts for service issues.

    Resolved

  3. 1PasswordActivity Log fails to load or return errors for some users

    **Date of Incident:** 2025-07-22 **Time of Incident \(UTC\):** 10:40 - 06:30 **Services Affected: Admin Console Activity log and User Details page** **Impact Duration:** 43 hrs ## Summary A change to our internal data model that removed an unused type definition led to multiple failures in the Reports system. ## Impact on Customers * **Events API and Reporting:** The activity log widget failed to display activities. * Admin console: User details page failed to display user details ## What Happened? A software update introduced an API change that caused a mismatch between client and server. The Audit log page in the admin console was still collecting data but was not able to render it. * **Timeline of Events \(UTC\):** * 10:40 : Detected by 1Password personnel and root cause identified * 10:42: Issue Identified * 13:38 Fix created and testing initiated * 06:30: Fix released, Service fully restored * **Root Cause Analysis:** A User State was removed from the [1Password.com](http://1Password.com) server but not the client. This was a breaking API change. ## How Was It Resolved? * **Resolution Steps:** The user state in the 1Password client was removed to get the server and client back into parity. * **Verification of Resolution:** 1Password engineering tested the changes and validated that full system functionality was restored. ## What We Are Doing to Prevent Future Incidents * **User State change process: 1Password is investigating how to catch breaking API changes by implementing additional end-to-end tests in the CI pipeline.** * Audit log architecture change: Engineering is investigating a rework of the audit log page to change how it aggregates data so that it is not reliant on an endpoint. This would mitigate future occurrences that caused this issue. ## Next Steps and Communication * No action is required from our customers at this time. * If you are still experiencing issues, please contact our support team at [support@1password.com](mailto:support@1password.com). We are committed to providing a reliable and stable service, and we are taking the necessary steps to learn from this event and prevent it from happening again. Thank you for your understanding. Sincerely, The 1Password Team

    Resolved

  4. AsanaInbound email outage

    On 7/25/2025, between approximately 01:24 and 01:32 UTC, our inbound email system was completely down, which means that no emails from customers emailing Asana (e.g. at @mail.asana.com) were processed. No tasks or messages were created via email during that time.

    Resolved

Jul 24, 2025

  1. AppsFlyerGoogle SKAN data availability for July 21

    The issue has been fully resolved, and Google SKAN data for July 21 is now available across all products. If you continue to experience any issues, please contact our support team.

    Resolved

Jul 23, 2025

  1. UpCloud[PL-WAW1] Network Connectivity Issues

    We have successfully resolved the connectivity issue affecting the creation and management of new and existing Cloud Servers, Managed Object Storage and Managed Kubernetes clusters in our PL-WAW1 data center. The impacted services are now functioning as expected. If you continue to experience any further issues, please contact our Support team via Live Chat or email support@upcloud.com We sincerely apologise for any inconvenience this may have caused and appreciate your kind patience and understanding.

    Resolved

Jul 22, 2025

Older incidents