Figma Outage Check
Is Figma Down Right Now?
✅ Figma is up and working normally. Checked: 4:06 AM (GMT+8).
Auto-refreshing live data in 60s
Figma's Official Status Page
- Design file access and collaboration
- Figma plugin execution
- Dev Mode and design handoff
| Component | Status |
|---|---|
| APIs & Web Application | Operational |
| AWS Infrastructure | Operational |
| Real-time collaboration server | Operational |
SLA Grade: A
Based on 90-day verified uptime
99.944%
Uptime
63m
Mean Resolution Time (MTTR)
7
Avg Incidents / Month
10d ago
Last Incident
90 Days AgoToday
Figma Service Restoration
Resolved. Services returned to baseline response profiles.
Duration: 30m
Affected: Core Service
Figma Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 25m
Affected: Website, DNS Services
Figma API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 52m
Affected: API Requests, API Portal
Figma Network Congestion in Transit Provider
A major tier-1 network transit provider experienced packet loss in Europe and North America.
Duration: 1h 41m
Affected: Website, DNS Services
Figma API Gateway Timeout and Increased Error Rates
Engineers investigated a spike in 504 Gateway Timeout errors affecting public API endpoints.
Duration: 26m
Affected: API Requests, API Portal
Are you having problems with Figma?
Submit your report to help alert other developers.
Downtime Reports: Last 2 Hours
2 Hours AgoNow
Troubleshooting Guide
- 1Hard RefreshBypass cache (Ctrl+F5 or Cmd+Shift+R).
- 2Flush DNSRun
ipconfig /flushdns. - 3Check with alternative networkTry loading the site on a mobile cellular network or over a VPN. If it loads, the issue lies in your local ISP provider network routing.
Uptime Alternatives
GitHub
Leading developer platform.
Slack
Real-time team communication.
Yes, Figma maintains an official status page. However, our real-time tracker aggregates reports faster.
Historical records indicate that the mean time to resolve (MTTR) is approximately 63 minutes.
Outages can happen due to configuration mistakes, database freezes, edge network issues, or infrastructure drops.
You can subscribe to live alerts on this page. We send emails on status updates.
Try bypass caching by executing hard refresh, flush local DNS, or use alternatives listed below.