Triage agent responses delayed by up to 4 minutes
Timeline · 2 updates
- investigating Dec 15, 2025, 03:48 PM UTC
We are currently investigating this issue.
- resolved Dec 15, 2025, 04:38 PM UTC
This incident has been resolved.
Thread had 51 outages in the last 2 years totaling 7427h 46m of downtime, averaging 2.1 incidents per month.
There were 51 Thread outages since April 11, 2025 totaling 7427h 46m of downtime. Each is summarised below. Incident details, duration, and resolution information.
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.
We are currently investigating this issue.
This incident has been resolved.
Due to the Cloudflare outage, We will not be able to support deploying new Slack Service Apps until tomorrow morning.
This incident has been resolved.
We are working to better understand the reason for the issue and possible workarounds to restore services, we will follow with an update in 30 mins.
CloudFlare confirmed an outage: https://www.cloudflarestatus.com/
We are seeing improvements and currently working to re-enabled webhooks for PSA integrations as they could automatically disable them when services were unavailable.
Due to a large scale outage of Cloudflare, the largest CDN and WAF provider on the internet, Thread has had issues over the last 3 hours. We are migrating our DNS from Cloudflare to Amazon Route53. We have completed the migration of getthread.com, and are migrating remaining domain names. Inbox, Admin, Messenger are back up and running. Teams and Slack are still down. Thread and PSA may not be in sync over the last 3 hours.
We are functioning again. As part of this process we are resyncing all tickets to ensure nothing was lost. During the next two to three hours Sync jobs from the admin panel will be delayed until this process is complete. This will also cause a 2 or 3 hour delay on pressing the resync button in inbox.
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.
> As part of the **Contact Intelligence General Availability** release, we introduced contact intelligence loading into ticket queries. The rollout performed well in Inbox; however, when we extended it to the PSA Pods, it significantly increased both the amount of data fetched from the database and the number of requests. This led to severe degradation in our real-time application performance.Our engineering team was alerted by our monitoring systems and promptly rolled back the changes. Despite the quick response, the issue caused temporary slowness in processing incoming events from PSA and our internal systems for about an hour after the rollback.Following the incident, our engineering team conducted an internal post-mortem and is actively addressing the issues identified in this release. We’re implementing several action items to ensure future releases don’t impact production and to strengthen both our release and rollback processes.
We are currently investigating this issue.
This incident has been resolved. Please verify correct settings in Thread Admin -> Magic Agents -> Reminder Agent -> Manage Access
We will update as soon as we have additional details. Details: https://health.aws.amazon.com/health/status
AWS has remediated the issue, and services are gradually coming back online. However, we’re still seeing residual effects impacting Twilio, preventing messages from loading in Inbox and Messenger.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
If you press the retry button, it will submit successfully. We have opened an issue with Microsoft on this to investigate the root cause.
This incident has been resolved.
We are currently investigating this issue.
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 aware of a recent spike in failure messages coming from Microsoft Teams.
A Fix have been implemented and we are monitoring.
This incident has been resolved.
This only affects new custom apps and does not affect any existing apps.
We are currently investigating an issue affecting new deployments of Microsoft Teams customer applications and bots. This is due to Microsoft’s recent enforcement of a deprecation related to multi-tenant app and bot support. Importantly, existing deployments remain fully functional and are not impacted by this change. The issue is limited to attempts to deploy or register new customer-facing Teams apps that rely on multi-tenant configuration. Our team is working toward a resolution and actively engaging with Microsoft support to clarify deprecation timelines and potential mitigation paths. We will continue to provide updates as we make progress. Please reach out to [email protected] or help.getthread.com if you have any questions or would like a thread to be made to track this and report back directly when resoled.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of the issue and have implemented a fix.
We expect the issue to be fully resolved in 30-40 minutes.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We expect normal operations to resume within approximately one hour. No data has been lost during the outage; however, the delay in real-time operations is due to the system processing the backlog.
We are continuing to monitor for any further issues.
This incident has been resolved.
Our Email vendor is experiencing a major outage. If you are using SSO this will not affect you.
This incident has been resolved.
We are currently investigating this issue.
We have an outage related to a service provider that we use. Tickets are still being made in your PSA but Threads will not load in inbox or Messenger Teams or Web Impacted systems: Inbox Messenger web Messenger teams
This incident has been resolved.