Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 24, 2026

  1. PleoIssues opening the mobile app on Android devices

    A fix (v26.9.0) has been released to the Google Play store. We will continue to monitor rollout to ensure affected users are no longer experiencing these issues. We are grateful for your patience during this time and apologise for any inconvenience this may have caused.

    Resolved

  2. ZapierAI by Zapier steps in Zaps with transcribe action running into an error

    Between approximately 10:00PM UTC on Feb 23 and 3:20 AM UTC on February 24, we saw errors being returned from the Transcribe cation in AI by Zapier. The team were able to identify and roll-back the change causing this issue and the issue should now be resolved. If you run into any unexpected errors, please feel free to reach out to us at: https://zapier.com/app/get-help

    Resolved

  3. Box[Major] Issues with Box Sign

    We recently addressed issues affecting several features of Box. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. ‌ On December 17, 2025, from 11:15 AM PST to 4:46 PM PST, some users may have experienced difficulties while working in Box Sign, Box AI, and Box Doc Gen. During this time, users may have noticed service degradation and delayed email delivery. The issue was caused by a missing schema, which was itself caused by a corrupted schema deployment. We were able to resolve the issue by rolling back the change that temporarily created issues. ‌ **Analysis** Box Sign, Box AI, and Box Doc Gen rely on a definition of the schemas that describe the events that they need to process. As we deliver new products, these schemas may occasionally need to be updated, and we have a standard process and pipeline to deploy these schema. As part of a project to upgrade our pipeline infrastructure, the schema deployment pipeline migrated to a new infrastructure. During the migration process, an external library version upgrade introduced a new default behavior that was not compatible with the existing pipeline. This resulted in a temporary degradation of the service. Additionally, the migration process exposed some observability and guardrail gaps in the pipeline that would have prevented this issue from happening and that extended the impact for a longer period of time. Once identified, the incompatible library was reverted to the previous version and the system resumed to normal. ‌ **Corrective Actions** Box has initiated the following corrective actions: * Introduce a schema validation step in the deployment pipeline so that incompatible schemas cannot be deployed * Enforce the environment promotion process as part of the schema deployment pipeline * Uplift the observability of the pipeline to enable more visibility around the different phases of the deployment process ‌ We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter.  ‌ Sincerely, The Box Team

    Resolved

Feb 23, 2026

  1. GitHubIntermittent authentication failures on GitHub

    On February 17, 2026, between 17:07 UTC and 19:06 UTC, some customers experienced intermittent authentication failures affecting GitHub Actions, parts of Git operations, and other authentication-dependent requests. On average, the Actions error rate was approximately 0.6% of affected API requests. Git operations ssh read error rate was approximately 0.29%, while ssh write and http operations were not impacted. During the incident, a subset of requests failed due to token verification lookups intermittently failing, leading to 401 errors and degraded reliability for impacted workflows.<br /><br />The issue was caused by elevated replication lag in the token verification database cluster. In the days leading up to the incident, the token store’s write volume grew enough to exceed the cluster’s available capacity. Under peak load, older replica hosts were unable to keep up, replica lag increased, and some token lookups became inconsistent, resulting in intermittent authentication failures.<br /><br />We mitigated the incident by adjusting the database replica topology to route reads away from lagging replicas and by adding/bringing additional replica capacity online. Service health improved progressively after the change, with GitHub Actions recovering by ~19:00 UTC and the incident resolved at 19:06 UTC.<br /><br />We are working to prevent recurrence by improving the resilience and scalability of our underlying token verification data stores to better handle continued growth.

    Resolved

  2. HashiCorpTerraform Runs not Proceeding

    Our Engineering team has resolved the issue. Terraform runs should be proceeding normally. Please retry any Terraform runs that appear stuck. If you continue to experience any problems, please open a ticket with our support team.

    Resolved

  3. Liquid WebDDOS Attack on cloudhost-323832-us-midwest-1-nxcli-net

    Following the mitigation efforts, we are no longer observing any signs of malicious or abnormal traffic, and the server is operating normally. All services remain stable at this time. If you have further questions or concerns, please contact us at support@nexcess.net or via Live chat.

    Resolved

Older incidents