- Detected by Pingoru
- Dec 15, 2025, 03:48 PM UTC
- Resolved
- Dec 15, 2025, 04:38 PM UTC
- Duration
- 49m
Affected: Triage Agent
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.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 01:30 PM UTC
- Resolved
- Dec 10, 2025, 01:55 PM UTC
- Duration
- 25m
Affected: Thread Message Processing
Timeline · 2 updates
-
monitoring Dec 10, 2025, 01:30 PM UTC
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.
-
resolved Dec 10, 2025, 01:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 05:27 PM UTC
- Resolved
- Dec 08, 2025, 06:15 PM UTC
- Duration
- 47m
Affected: Thread RT APIThread Inbox, Messenger, & AdminTriage Agent
Timeline · 2 updates
-
investigating Dec 08, 2025, 05:27 PM UTC
We are currently investigating this issue.
-
resolved Dec 08, 2025, 06:15 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 08, 2025, 04:15 PM UTC
- Resolved
- Dec 08, 2025, 04:48 PM UTC
- Duration
- 32m
Affected: Thread Inbox, Messenger, & Admin
Timeline · 2 updates
-
investigating Dec 08, 2025, 04:15 PM UTC
We are currently investigating this issue.
-
resolved Dec 08, 2025, 04:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 26, 2025, 08:43 PM UTC
- Resolved
- Nov 26, 2025, 08:48 PM UTC
- Duration
- 5m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 2 updates
-
investigating Nov 26, 2025, 08:43 PM UTC
We are currently investigating this issue.
-
resolved Nov 26, 2025, 08:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 03:52 PM UTC
- Resolved
- Nov 19, 2025, 11:05 AM UTC
- Duration
- 19h 12m
Affected: Slack Apps/Integrations/APIs
Timeline · 2 updates
-
identified Nov 18, 2025, 03:52 PM UTC
Due to the Cloudflare outage, We will not be able to support deploying new Slack Service Apps until tomorrow morning.
-
resolved Nov 19, 2025, 11:05 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 03:39 PM UTC
- Resolved
- Nov 18, 2025, 06:40 PM UTC
- Duration
- 3h 1m
Affected: Thread RT APIThread Inbox, Messenger, & AdminThread Message Processing
Timeline · 6 updates
-
investigating Nov 18, 2025, 11:45 AM UTC
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.
-
identified Nov 18, 2025, 11:49 AM UTC
CloudFlare confirmed an outage: https://www.cloudflarestatus.com/
-
monitoring Nov 18, 2025, 11:58 AM UTC
We are seeing improvements and currently working to re-enabled webhooks for PSA integrations as they could automatically disable them when services were unavailable.
-
monitoring Nov 18, 2025, 01:53 PM UTC
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.
-
monitoring Nov 18, 2025, 03:39 PM UTC
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.
-
resolved Nov 18, 2025, 06:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 06, 2025, 05:03 PM UTC
- Resolved
- Nov 06, 2025, 05:20 PM UTC
- Duration
- 16m
Affected: Thread Inbox, Messenger, & AdminMicrosoft Teams ServiceSlack Apps/Integrations/APIs
Timeline · 2 updates
-
investigating Nov 06, 2025, 05:03 PM UTC
We are currently investigating this issue.
-
resolved Nov 06, 2025, 05:20 PM UTC
This incident has been resolved.
Read the full incident report →
Critical November 6, 2025 - Detected by Pingoru
- Nov 06, 2025, 04:17 PM UTC
- Resolved
- Nov 06, 2025, 04:38 PM UTC
- Duration
- 21m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 3 updates
-
investigating Nov 06, 2025, 04:17 PM UTC
We are currently investigating this issue.
-
resolved Nov 06, 2025, 04:38 PM UTC
This incident has been resolved.
-
postmortem Nov 10, 2025, 04:42 PM UTC
> 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.
Read the full incident report →
- Detected by Pingoru
- Oct 24, 2025, 01:55 PM UTC
- Resolved
- Oct 24, 2025, 03:52 PM UTC
- Duration
- 1h 57m
Affected: Reminder Agent
Timeline · 2 updates
-
investigating Oct 24, 2025, 01:55 PM UTC
We are currently investigating this issue.
-
resolved Oct 24, 2025, 03:52 PM UTC
This incident has been resolved. Please verify correct settings in Thread Admin -> Magic Agents -> Reminder Agent -> Manage Access
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 02:16 PM UTC
- Resolved
- Oct 21, 2025, 03:09 AM UTC
- Duration
- 12h 53m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 10 updates
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 08:02 AM UTC
- Resolved
- Oct 20, 2025, 12:32 PM UTC
- Duration
- 4h 29m
Affected: Thread RT APIThread Inbox, Messenger, & AdminThread Message ProcessingMicrosoft Teams Service
Timeline · 4 updates
-
identified Oct 20, 2025, 08:02 AM UTC
We will update as soon as we have additional details. Details: https://health.aws.amazon.com/health/status
-
identified Oct 20, 2025, 10:59 AM UTC
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.
-
monitoring Oct 20, 2025, 12:07 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 20, 2025, 12:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 17, 2025, 05:04 PM UTC
- Resolved
- Dec 03, 2025, 04:23 PM UTC
- Duration
- 46d 23h
Affected: Microsoft Teams Service
Timeline · 2 updates
-
investigating Oct 17, 2025, 05:04 PM UTC
If you press the retry button, it will submit successfully. We have opened an issue with Microsoft on this to investigate the root cause.
-
resolved Dec 03, 2025, 04:23 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 30, 2025 - Detected by Pingoru
- Sep 30, 2025, 04:10 PM UTC
- Resolved
- Sep 30, 2025, 04:35 PM UTC
- Duration
- 24m
Affected: Thread Inbox, Messenger, & Admin
Timeline · 2 updates
-
investigating Sep 30, 2025, 04:10 PM UTC
We are currently investigating this issue.
-
resolved Sep 30, 2025, 04:35 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 05, 2025, 04:53 PM UTC
- Resolved
- Sep 05, 2025, 05:46 PM UTC
- Duration
- 53m
Affected: Assistive AI
Timeline · 3 updates
Read the full incident report →
Critical September 3, 2025 - Detected by Pingoru
- Sep 03, 2025, 07:31 PM UTC
- Resolved
- Sep 04, 2025, 02:00 AM UTC
- Duration
- 6h 28m
Affected: ConnectWise PodsThread Inbox, Messenger, & AdminTwilio ConversationsAutoTask PodsHaloPSA Pods
Timeline · 9 updates
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 02:41 PM UTC
- Resolved
- Aug 19, 2025, 03:50 PM UTC
- Duration
- 1h 9m
Affected: Thread Message Processing
Timeline · 3 updates
-
investigating Aug 19, 2025, 02:41 PM UTC
We are aware of a recent spike in failure messages coming from Microsoft Teams.
-
monitoring Aug 19, 2025, 02:44 PM UTC
A Fix have been implemented and we are monitoring.
-
resolved Aug 19, 2025, 03:50 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2025, 02:58 PM UTC
- Resolved
- Aug 12, 2025, 01:38 PM UTC
- Duration
- 7d 22h
Affected: Microsoft Teams ServiceMicrosoft Teams Integration
Timeline · 4 updates
-
investigating Aug 04, 2025, 02:58 PM UTC
This only affects new custom apps and does not affect any existing apps.
-
investigating Aug 04, 2025, 08:56 PM UTC
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.
-
identified Aug 05, 2025, 12:13 PM UTC
The issue has been identified and a fix is being implemented.
-
resolved Aug 12, 2025, 01:38 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2025, 02:38 PM UTC
- Resolved
- Jul 24, 2025, 03:13 PM UTC
- Duration
- 34m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 2 updates
-
investigating Jul 24, 2025, 02:38 PM UTC
We are currently investigating this issue.
-
resolved Jul 24, 2025, 03:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 18, 2025, 05:17 PM UTC
- Resolved
- Jul 18, 2025, 05:53 PM UTC
- Duration
- 36m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 3 updates
-
investigating Jul 18, 2025, 05:17 PM UTC
We are currently investigating this issue.
-
monitoring Jul 18, 2025, 05:50 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jul 18, 2025, 05:53 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 14, 2025, 02:45 PM UTC
- Resolved
- Jul 14, 2025, 04:33 PM UTC
- Duration
- 1h 47m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 3 updates
-
monitoring Jul 14, 2025, 02:45 PM UTC
We are aware of the issue and have implemented a fix.
-
monitoring Jul 14, 2025, 02:46 PM UTC
We expect the issue to be fully resolved in 30-40 minutes.
-
resolved Jul 14, 2025, 04:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2025, 02:42 PM UTC
- Resolved
- Jun 18, 2025, 05:08 PM UTC
- Duration
- 2h 26m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 6 updates
-
investigating Jun 18, 2025, 02:42 PM UTC
We are currently investigating this issue.
-
identified Jun 18, 2025, 03:49 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Jun 18, 2025, 03:55 PM UTC
A fix has been implemented and we are monitoring the results.
-
monitoring Jun 18, 2025, 03:58 PM UTC
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.
-
monitoring Jun 18, 2025, 05:08 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jun 18, 2025, 05:08 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2025, 09:55 PM UTC
- Resolved
- Apr 23, 2025, 10:51 PM UTC
- Duration
- 56m
Affected: Thread Inbox, Messenger, & Admin
Timeline · 2 updates
-
investigating Apr 23, 2025, 09:55 PM UTC
Our Email vendor is experiencing a major outage. If you are using SSO this will not affect you.
-
resolved Apr 23, 2025, 10:51 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2025, 08:07 PM UTC
- Resolved
- Apr 17, 2025, 10:21 PM UTC
- Duration
- 2h 14m
Affected: Thread RT APIThread Inbox, Messenger, & Admin
Timeline · 3 updates
-
investigating Apr 17, 2025, 08:07 PM UTC
We are currently investigating this issue.
-
identified Apr 17, 2025, 08:14 PM UTC
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
-
resolved Apr 17, 2025, 10:21 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 11, 2025, 05:55 PM UTC
- Resolved
- Apr 11, 2025, 06:02 PM UTC
- Duration
- 6m
Affected: Assistive AITriage Agent
Timeline · 3 updates
-
investigating Apr 11, 2025, 05:55 PM UTC
We are currently investigating this issue.
-
investigating Apr 11, 2025, 06:01 PM UTC
We are continuing to investigate this issue.
-
resolved Apr 11, 2025, 06:40 PM UTC
This incident has been resolved.
Read the full incident report →