●Incident
Figma degradation.
ResolvedDEGRADATION · MEDIUMNov 4, 2026, 01:32 PM · about 10 hours ago · Duration: 51min
Incident Summary
Incident Summary
API Figma is currently DOWN in europe.
Diagnostic Details
Error Type: http HTTP Status: 503 Error Message: API returned HTTP 503 Retry Attempts: 1 (all failed)
Validation Results
Validation Reason: DOWN in 2 regions: us-west, europe Consecutive DOWN Checks: 2 Time Between Checks: 295s
Cross-Region Impact
Also DOWN in: us-west Total Affected Regions: 2
Severity Assessment
Level: MEDIUM Limited regional impact or recoverable error type.
Detected by Probecast Health Monitor - 2026-11-04T13:32:11.301Z
Timeline
●Started
Nov 4, 2026, 01:32 PM
about 10 hours ago
●Resolved
Nov 4, 2026, 02:23 PM
about 9 hours ago
●Duration
51min
Total downtime
Evidence Logs10 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Nov 4, 01:32 PM | europe | down | 5ms | 503 |
| Nov 4, 01:29 PM | asia | degraded | 6095ms | 401 |
| Nov 4, 01:28 PM | us-west | down | 6ms | 503 |
How many of your clients depend on Figma?
When Figma 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 up to 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.