Is Thread down?

Last checked 1m ago
Current status
Thread is up

No active incidents. All 27 components operational.

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

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

Users who monitor Thread also follow these CRM services: HubSpot Intercom Make ActiveCampaign Teamwork Alchemer Formstack Help Scout Intapp Bullhorn View all 8,000+ providers
Thread uptime 99.97% uptime · past 90 days
Mon Wed Fri
AugSepOctNov
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 1h 47m
    Started Nov 03, 2026, 09:54 PM UTC · Resolved Nov 03, 2026, 11:41 PM UTC
    Voice AI
    Timeline · 6 updates
    • identified · Nov 03, 2026, 09:54 PM UTC

      Since November 2, 2:30 PM ET, outbound Voice AI calls to phone numbers saved with an extension may not reach the extension. This affects calls to technicians and to customer contacts. The call connects to the main line, but the phone system doesn’t receive the extension, so the call ends up in the main menu. Calls to direct numbers without an extension are not affected. We’ve traced this to an issue with a vendor and are working with them on a fix. In the meantime, calling a direct number avoids the problem. Adding extra pauses to the extension won’t help. We’ll post an update when it’s fixed.

    • identified · Nov 03, 2026, 10:00 PM UTC

      Our vendor has found the root cause and is deploying a fix now. Until it’s complete, outbound calls to numbers with an extension may still fail. We’ll confirm here once we’ve verified the fix.

    • identified · Nov 03, 2026, 10:08 PM UTC

      We now believe this issue also affects inbound Voice AI calls that are transferred to a number with an extension: the transfer may land in the destination’s main menu instead of reaching the extension. Our vendor has identified the root cause and is deploying a fix. Until it’s complete, outbound calls and transfers to numbers with an extension may still land in the main menu. Calls and transfers to direct numbers without an extension are not affected. We’ll post an update once we’ve verified the fix.

    • monitoring · Nov 03, 2026, 10:24 PM UTC

      Our vendor has deployed a fix. Outbound calls to technicians and contacts with an extension are reaching the extension again. Some inbound transfers to an extension may still land in the destination’s main menu. We’ll post another update once transfers are fully resolved.

    • monitoring · Nov 03, 2026, 10:46 PM UTC

      Our vendor has rolled back the change that caused this issue. Outbound calls to technicians and contacts with an extension are reaching the extension again. Some inbound transfers to an extension may still land in the destination’s main menu, and we’re working on a fix for those. As a temporary workaround, add a pause before the extension in your transfer settings (for example, w200 instead of 200). We’ll post an update once inbound transfers are resolved.

    • resolved · Nov 03, 2026, 11:41 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 3h 14m
    Started Nov 02, 2026, 05:18 PM UTC · Resolved Nov 02, 2026, 08:33 PM UTC
    Thread Inbox, Messenger, & AdminPSA API
    Timeline · 2 updates
    • identified · Nov 02, 2026, 05:18 PM UTC

      We’re seeing delays of 2–12 minutes in webhooks sent from ConnectWise to Thread. This affects only partners on ConnectWise Cloud in North America. The delay is on ConnectWise’s side: Thread processes every webhook as soon as it arrives. As a result, ticket changes made in ConnectWise may take a few extra minutes to appear in Thread. We’re in contact with ConnectWise and will post an update as soon as we know more.

    • resolved · Nov 02, 2026, 08:33 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 23m
    Started Oct 30, 2026, 05:55 PM UTC · Resolved Oct 30, 2026, 06:18 PM UTC
    Thread Inbox, Messenger, & Admin
    Timeline · 2 updates
    • investigating · Oct 30, 2026, 05:55 PM UTC

      We are currently investigating this issue.

    • resolved · Oct 30, 2026, 06:18 PM UTC

      This incident has been resolved. We are verifying if there is a way to recover the missed notes that happened during the outage.

    Latest: This incident has been resolved. We are verifying if there is a way to recover the missed notes that happened during the outage.

  4. Resolved 14m
    Started Oct 29, 2026, 12:04 AM UTC · Resolved Oct 29, 2026, 12:18 AM UTC
    Voice AI
    Timeline · 4 updates
    • investigating · Oct 29, 2026, 12:04 AM UTC

      Since approximately 7:32 PM ET, the majority of inbound calls to Voice AI phone numbers are failing to connect. Callers may hear the call fail or ring without being answered. The issue is caused by a service disruption at one of our voice infrastructure vendors, who are actively investigating. We are in contact with the vendor and will post an update as soon as calls are connecting reliably again.

    • investigating · Oct 29, 2026, 12:04 AM UTC

      We are continuing to investigate this issue.

    • monitoring · Oct 29, 2026, 12:05 AM UTC

      Inbound calls to Voice AI phone numbers have been connecting normally since approximately 7:52 PM ET. Between approximately 7:32 PM and 7:52 PM ET, most inbound calls failed to connect. Our vendor has not yet confirmed a full resolution, so we are continuing to monitor and will post a final update once they do.

    • resolved · Oct 29, 2026, 12:18 AM UTC

      Between approximately 7:32 PM and 7:52 PM ET, most inbound calls to Voice AI phone numbers failed to connect due to a service disruption at one of our voice infrastructure vendors. The vendor has confirmed the issue is resolved, and calls have been connecting normally since 7:52 PM ET. We apologize for the disruption.

    Latest: Between approximately 7:32 PM and 7:52 PM ET, most inbound calls to Voice AI phone numbers failed to connect due to a service disruption at one of our voice infrastructure vendors.…

  5. Resolved 56m
    Started Oct 21, 2026, 01:18 PM UTC · Resolved Oct 21, 2026, 02:14 PM UTC
    Timeline · 1 update
    • resolved · Oct 21, 2026, 02:30 PM UTC

      We are investigating an issue that caused call recordings to fail to save between approximately 9:18 AM ET and 10:14 AM ET today. The issue was related to a problem with one of our vendors during that time period. Our team has confirmed the issue has been resolved, and call recordings created after 10:14 AM ET are saving normally.

    Latest: We are investigating an issue that caused call recordings to fail to save between approximately 9:18 AM ET and 10:14 AM ET today. The issue was related to a problem with one of our…

See the full Thread outage history

5 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Thread outage history →

Or sign up free to get alerts when Thread breaks · 3 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 27 components checked every 5 minutes
57incidents recorded
38last 12 months
10last 90 days
4 hourstypical duration, 12 months

The longest incident in the last year, Scheduled Maintenance Notice on August 20, 2026, ran for 46 hours. 2 maintenance windows announced in the same period.

Most affected components, last 12 months

  • Thread Inbox, Messenger, & Admin18
  • Thread Message Processing10
  • Thread RT API7
  • Triage Agent6
  • Assistive AI3

Latest incidents

Outage history

Past 90 days · 10 incidents View full outage history →