Live  /  Providers  /  Thread

Thread

getthread.comNo open incidents

Independent assessment — SquidGrid is not affiliated with Thread. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks Thread’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what Thread is reporting

Current & recent incidents

Resolved

Calls to numbers with extensions not reaching the extension

Minor impact · 2026-11-03 23:41 UTC · source

Resolved

Internal notes not visible from non-inbox sources

Major impact · 2026-10-30 18:18 UTC · source

Resolved

Voice AI inbound calls failing to connect

Major impact · 2026-10-29 00:18 UTC · source

Resolved

Autotask Webservices24 Region Not Sending Webhooks

Major impact · 2026-10-13 22:08 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 6 incidents from Thread’s own status page since 2026-10-13.

Recent incidents in the archive

Computed by SquidGrid from the incidents Thread published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what Thread has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

Thread runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of Thread is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with Thread.