Orchestry Outage History

Orchestry is up right now

Orchestry had 7 outages in the last 2 years totaling 366h 28m of downtime — averaging 0.3 incidents per month.

There were 7 Orchestry outages since November 25, 2024 totaling 366h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://orchestry.statuspage.io

Minor October 15, 2026

File Archival jobs failing for some tenants

Detected by Pingoru
Oct 15, 2026, 02:51 PM UTC
Resolved
Oct 15, 2026, 08:46 PM UTC
Duration
5h 54m
Affected: Web Application
Timeline · 5 updates
  1. investigating Oct 15, 2026, 02:51 PM UTC

    We’re aware of an issue causing File Archival jobs to fail for some customers in our US region. Affected jobs fail during execution, and archival actions scheduled during this period may not have completed. We’ve traced the cause to a recent change in Microsoft SharePoint Online that affects how certain search requests are processed. Microsoft has acknowledged reports of the problem, which appears to be impacting a subset of SharePoint Online tenants. Our team is investigating if the issue can be worked around on our side so that File Archival no longer depends on the affected behavior, and we’re also monitoring Microsoft’s progress on a resolution. No files have been lost or modified as a result of this issue; jobs that failed simply did not run. We’ll post another update as soon as we have more information or a fix is deployed.

  2. identified Oct 15, 2026, 04:21 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Oct 15, 2026, 07:44 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 15, 2026, 08:46 PM UTC

    This incident has been resolved.

  5. postmortem Oct 16, 2026, 06:53 PM UTC

    **What happened:** From October 14 to 15, File Archival jobs failed for some customers in our US region. Scheduled archival actions during this time did not run. No files were lost or modified. **Detection:** Our monitoring caught the failures early, which allowed us to begin investigating right away. **Why:** A change Microsoft made to SharePoint Online caused some of the search requests File Archival relies on to be rejected. It affected only some SharePoint tenants. **How we fixed it:** We updated File Archival to work with the change and deployed the fix on October 15. Jobs are completing normally again. We apologize for the disruption. If you have questions, please contact our support team.

Read the full incident report →

Minor August 17, 2026

Delayed background processing and workspace provisioning

Detected by Pingoru
Aug 17, 2026, 02:26 PM UTC
Resolved
Aug 17, 2026, 10:06 PM UTC
Duration
7h 39m
Affected: ProvisioningLifecycle
Timeline · 4 updates
  1. investigating Aug 17, 2026, 02:26 PM UTC

    We are experiencing delays in background processing across all regions. Some customers may see workspace provisioning and reporting data updates take longer than usual or appear stuck in progress. The Orchestry app itself remains available. We have identified the cause and are working on remediation. No data has been lost, delayed work will complete once processing recovers.

  2. identified Aug 17, 2026, 05:34 PM UTC

    We have confirmed the cause of the background processing delays and are working towards a fix. Affected job servers are being restarted along with a temporary mitigation to restore throughput while we finalize the fix.

  3. monitoring Aug 17, 2026, 09:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Aug 17, 2026, 10:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 25, 2024

Microsoft Service Degradation Impacting Orchestry Services

Detected by Pingoru
Nov 25, 2024, 10:30 AM UTC
Resolved
Nov 26, 2024, 01:00 PM UTC
Duration
1d 2h
Affected: Web ApplicationAPIProvisioningLifecycle
Timeline · 3 updates
  1. identified Nov 25, 2024, 06:06 PM UTC

    Microsoft services (Exchange Online, Microsoft 365 suite, Microsoft Power Automate in Microsoft 365, Microsoft Purview, Microsoft Teams, SharePoint Online, Universal Print) are experiencing an active service degradation. As such, Orchestry services that depend on these services may fail to work. We are actively monitoring this situation. Microsoft has this Issue as ID MO941162 within Microsoft Administration Service Health.

  2. monitoring Nov 26, 2024, 01:10 PM UTC

    On Nov 25th at 11:32 PM EST, Microsoft announced that core services have been restored, with the exception of Outlook on the web. We have confirmed that Orchestry services are no longer impacted.

  3. resolved Nov 26, 2024, 01:27 PM UTC

    This incident has been resolved.

Read the full incident report →