Analytics Reports are not responding
Timeline · 2 updates
- identified Jul 31, 2026, 08:22 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Jul 31, 2026, 08:25 PM UTC
This incident has been resolved.
Thread had 49 outages in the last 2 years totaling 140h 58m of downtime — averaging 2 incidents per month.
There were 49 Thread outages since March 19, 2025 totaling 140h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating an issue causing delays in message delivery and processing. Affected users may experience slower-than-normal delivery of inbound and outbound messages. Our team is actively working to identify the root cause and restore normal performance as quickly as possible. We will provide additional updates as more information becomes available.
We have identified the issue and are working on deploying a fix.
A fix has been deployed and we are monitoring the results.
The incident has been resolved and we are back to real time.
We are currently experiencing delays in processing a subset of platform events. As a result, some updates may take longer than expected to be reflected in the system. Our team has identified the issue and has implemented mitigation measures to reduce the backlog and restore normal processing. We are continuing to monitor progress closely. We will provide another update as more information becomes available.
This incident has been resolved.
We are currently experiencing a 4-5 minute delay in ticket arrival into Thread, This is resulting in Assistive AI delays and delays in tickets arriving in inbox. We expect this delay to resolve in under 30 minutes.
This incident has been resolved.
We are experiencing intermittent failures with assistive AI features. Rerunning should resolve the issue while we investigate.
We have identified the root cause and we are working to mitigate the issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently experiencing a service disruption due to an upstream provider issue affecting Anthropic’s Claude services. Claude has recently reported elevated error rates and instability across multiple models and API endpoints, which may impact Thread features that rely on AI processing. We will provide updates as soon as more information becomes available or once service stability improves.
We’ve implemented a mitigation to reduce impact from the ongoing upstream Claude service disruption. Affected Magic AI features have been temporarily migrated to OpenAI while Anthropic works to resolve the current issues. We are continuing to monitor Anthropic’s recovery and will transition back once their services are fully stable.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have identified that the Triage agent is not responding to clients as well as other AI functions not fully working. We are investigating and will follow up soon.
This incident has been resolved.
We identified an issue that is causing the HaloPSA webhooks to not be processed. We're investigating the issue at the moment and will provide an update as soon as possible.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently experiencing slowness with our Slack service and companion app. This is caused by an ongoing outage on Slack's infrastructure https://slack-status.com/. Our team is actively monitoring the situation. No action is required on your end.
Slack services appear to be coming back online. We are continuing to monitor the outage.
This incident has been resolved.
We are seeing a delay in processing of webhooks. This will result in tickets not arrving in inbox for up to 15 minutes.
This incident has been resolved.
We have Identified the problem and are working with Microsoft to work towards a resolution.
Issue with intermittent failures in message delivery from Teams app has been resolved. Issue with intermittent failures in attachment deliver is still open and we are working with Microsoft Support on remediation.
Our engineering team is still actively investigating the issue with end user messages not syncing to the PSA. We appreciate your patience and will continue to provide updates as we make progress. A further update will be shared shortly.
This incident has been resolved.
We are currently investigating this issue.
We are currently investigating an issue where messages from end users in group chats are not being synced to the Thread/PSA. Our engineering team is actively looking into the root cause. An update will be provided in approximately 15 minutes.
Our engineering team is still actively investigating the issue with end user messages not syncing to the PSA. We appreciate your patience and will continue to provide updates as we make progress. A further update will be shared shortly.
This incident has been resolved.
We are aware of an issue where some users experience a blinking or flickering screen immediately after signing in to the Messenger web app. Our engineering team is actively investigating the root cause. No user data has been affected.
This incident has been resolved.
We are currently investigating an issue where creating new Teams Service apps is failing or not completing successfully. Users attempting to create or install a Teams app may encounter errors, timeouts, or see the process fail without completing. Existing Teams apps are not impacted at this time. Our team is actively investigating the cause and working toward a resolution. We will provide updates as more information becomes available.
We’ve shipped fixes and reliability improvements to the Teams Service app creation and install flow. New app creation should complete normally again. Existing Teams apps were never affected. Thanks for your patience while we investigated.
We are currently experiencing issues with our Inbox platform due to upstream connectivity problems related to Cloudflare, which is impacting dependent services. As a result, some users may encounter delayed message delivery, intermittent loading issues, or errors when accessing the Inbox. Our core systems remain operational, but performance and availability may be reduced while this upstream issue persists. We are actively monitoring the situation and coordinating with Cloudflare as they work toward resolution. Updates will be provided as more information becomes available.
This incident has been resolved.
We're aware of an issue affecting SSO authentication when logging into Inbox. As a temporary workaround, please disable SSO and use the One-Time Password (OTP) option to log in. We'll share an update as soon as we have more information.
We are continuing to investigate this issue.
This incident has been resolved.
Identified Issue: ConnectWise is currently experiencing delays in sending webhooks. Delivery may be delayed by up to 30 minutes. We are monitoring the situation and will provide updates as more information becomes available.
This incident has been resolved.
We are currently investigating an issue causing delays in our webhook processing pipeline. As a result, inbound webhook events may take longer than expected to be processed and reflected in downstream systems. All other platform services remain fully operational. Our engineering team is working to identify the source of the slowdown and restore normal processing speeds. Further updates will be provided as they become available. Thank you for your patience and understanding.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing an issue where emails sent from our environment to recipients hosted on Microsoft 365 (including Outlook.com and Exchange Online) are being delayed or not received. If you use SSO for sign in you should be unaffected.
We are continuing to investigate this issue.
We have verified email addresses not hosted by Microsoft are unaffected and are able to sign in as usual
You can monitor the outage here https://status.cloud.microsoft/m365/referrer=serviceStatusRedirect.
This incident has been resolved.
A fix has been deployed and we are monitoring
This incident has been resolved.
Thread is currently experiencing intermittent delays in message delivery. This behavior aligns with an ongoing issue affecting one of our infrastructure providers (Cloudflare), which Thread utilizes for network edge and traffic routing.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We have deployed a fix for the underlying issue and systems are recovering. Some messages may continue to experience brief delays as queues process remaining backlog. We expect full normalization shortly (within approximately 10 minutes). We’re actively monitoring recovery and will provide another update once all message flow is fully restored.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.