●Incident

ThoughtSpot outage.

ResolvedDEGRADATION · HIGH

Mar 9, 2026, 02:40 PM · 8 months ago · Duration: 185h 54min · Regions: asia, europe, us-east, us-west

Detected by Probecast

Incident Summary

Incident Summary

API ThoughtSpot is currently DOWN in asia.

Diagnostic Details

Error Type: network HTTP Status: N/A Error Message: fetch failed Retry Attempts: 3 (all failed)

Validation Results

Validation Reason: All 3 retry attempts failed Consecutive DOWN Checks: 2 Time Between Checks: 320s

Cross-Region Impact

Also DOWN in: europe, us-east, us-west Total Affected Regions: 4

Severity Assessment

Level: HIGH Multiple regions affected or critical error type detected.


Detected by Probecast Health Monitor - 2026-03-09T14:40:11.292Z

Timeline

●Started

Mar 9, 2026, 02:40 PM

8 months ago

●Resolved

Mar 17, 2026, 08:34 AM

7 months ago

●Duration

185h 54min

Total downtime

Evidence Logs20 checks

TimeRegionStatusLatencyCode
Mar 9, 02:40 PMasiadown324ms—
Mar 9, 02:36 PMeuropedown299ms—
Mar 9, 02:35 PMus-westdown42ms—
For the projects you ship

How many of your clients depend on ThoughtSpot?

When ThoughtSpot slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.

One provider breaks. See every client it touches.

Ordered by how many clients it hits, so you message the right people first.

Each client's site and store, checked from four regions.

US West & East, Europe and Asia — a regional outage never hides.

A monthly report under your brand, reviewed by your team before it goes out.

Uptime, incidents, traffic, revenue and support — signed off by a person.

Your team scoped per client. Every change on the record.

Freelancers see only their clients; every change lands in an append-only audit log.

Start freeBook 15 minutes →View ThoughtSpot full status →

Alerts land on email, Slack, push or webhooks — with the client's name on them.

Related Incidents