●Incident
Tableau outage.
ResolvedDEGRADATION · HIGHMar 9, 2026, 02:40 PM · 8 months ago · Duration: 174h 24min · Regions: europe
Incident Summary
Incident Summary
API Tableau is currently DOWN in asia.
Diagnostic Details
Error Type: timeout HTTP Status: N/A Error Message: Request timeout after 10000ms Retry Attempts: 3 (all failed)
Validation Results
Validation Reason: All 3 retry attempts failed Consecutive DOWN Checks: 2 Time Between Checks: 322s
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:50.077Z
Timeline
●Started
Mar 9, 2026, 02:40 PM
8 months ago
●Resolved
Mar 16, 2026, 09:05 PM
7 months ago
●Duration
174h 24min
Total downtime
Evidence Logs20 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Mar 9, 02:40 PM | asia | down | 10000ms | — |
| Mar 9, 02:36 PM | europe | down | 10001ms | — |
| Mar 9, 02:36 PM | us-west | down | 10000ms | — |
How many of your clients depend on Tableau?
When Tableau 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.
Alerts land on email, Slack, push or webhooks — with the client's name on them.