Is Orchestry down?

Last checked 1m ago
Current status
Orchestry is up

No incidents right now.

Orchestry is operational right now. Last checked 1m ago; the most recent incident resolved 16d ago.

Real-time Orchestry status, recent outages, and incident history: pulled directly from Orchestry's official status page at orchestry.statuspage.io every 5 minutes. Pingoru tracks 4 Orchestry services and has captured 2 incidents in the last 90 days (99.17% uptime). Get email, Slack, Discord, or webhook alerts the moment Orchestry reports a new incident, free for 3 monitors, no credit card.

Users who monitor Orchestry also follow these IT services: Jamf TeamViewer Cisco Meraki Datto Workato GoToMyPC Ubiquiti Splashtop Cursor Auvik View all 8,000+ providers
Orchestry uptime 99.17% uptime · past 90 days
Mon Wed Fri
AugSepOct
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 5h 54m
    Started Oct 15, 2026, 02:51 PM UTC · Resolved Oct 15, 2026, 08:46 PM UTC
    Web Application
    Timeline · 5 updates
    • 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.

    • identified · Oct 15, 2026, 04:21 PM UTC

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

    • monitoring · Oct 15, 2026, 07:44 PM UTC

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

    • resolved · Oct 15, 2026, 08:46 PM UTC

      This incident has been resolved.

    • 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.

    Latest: **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…

  2. Resolved 7h 39m
    Started Aug 17, 2026, 02:26 PM UTC · Resolved Aug 17, 2026, 10:06 PM UTC
    ProvisioningLifecycle
    Timeline · 4 updates
    • 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.

    • 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.

    • monitoring · Aug 17, 2026, 09:28 PM UTC

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

    • resolved · Aug 17, 2026, 10:06 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

Incident record

Since April 2026 · Statuspage by Atlassian · 4 components checked every 5 minutes
18incidents recorded
5last 12 months
2last 90 days
3 daystypical duration, 12 months

The longest incident in the last year, Advisory: Archival Policies with Group Configuration Options on January 8, 2026, ran for 12 days. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Lifecycle2
  • Provisioning2
  • Web Application2

Latest incidents

Outage history

Past 90 days · 2 incidents View full outage history →