Figma logo
ALL SYSTEMS OPERATIONAL

Figma systems
are operational.

Pulsetic detects outages before the provider officially reports them. Monitoring since Oct 2023 · 50 incidents caught

Last checked: 1 min ago · 0 user reports (24h) · Trusted by 30,000+ teams

  • ALL SYSTEMS OPERATIONAL

    Figma is up and running.

    Last incident resolved 3 weeks ago


    No active incidents at this time. Noticed something?
  • User Reports: Last 24 Hours

    0 reports

    Bars represent 20-min intervals. Occasional spikes may reflect individual issues, not widespread outages.

  • Outage Map

    No reports yet

    Reports by region (last 24h)

    No reports in the last 24h
  • Recent User Reports

    Live

    Latest 50 reports from the last 48 hours

You checked Figma. Who checks your website?

Pulsetic is website uptime monitoring. Add a website you own and it gets checked as often as every 30 seconds, so the next answer arrives by email.

10 monitors free, email alerts on failure and recovery. No credit card.

  • Top reported issues

    Click an issue to upvote it and help us better indicate the service status.

    Service outage 0
    Degraded performance 0
    Error messages 0
    Timeouts / no response 0
    Authentication issues 0
    Network / connectivity issues 0
    Feature not working 0
    API errors 0
    Billing or usage issues 0
    Other 0

    Have a different problem?

  • Issue breakdown

    0 total votes

    Distribution of reported issues over the last 24 hours.

    Service outage 0%
    Degraded performance 0%
    Error messages 0%
    Timeouts / no response 0%
    Authentication issues 0%
    Network / connectivity issues 0%
    Feature not working 0%
    API errors 0%
    Billing or usage issues 0%
    Other 0%

90-Day Health Summary

  • Total Incidents

    2

    Jun 19 to Sep 17, 2026

  • Major / Critical

    1

    50% of the total

  • Minor Incidents

    1

    Avg. 0.0 per day

  • Median Resolution

    3h 45m

    P95: 4h 10m

Figma Response Time, ms

By Continent
Location List

From official status page

Recent Outage History

View all incidents →
Incident Started Duration Impact Status Link
Figma MCP Disruption
Aug 26, 2026 · 12:08 PM 4h 10m
Major
Resolved
Details →
Service Disruption
Jul 27, 2026 · 7:29 PM 3h 20m
None
Resolved
Details →
Figma Make disruption - Gemini 3.1 Pro
Jun 18, 2026 · 11:46 PM 12h 53m
None
Resolved
Details →
Figma Make and Agent Service Disruption
Jun 16, 2026 · 5:58 PM 1h 42m
None
Resolved
Details →
Figma Make Service Disruption
Apr 20, 2026 · 6:42 AM 9h 8m
None
Resolved
Details →
Figma Make Service Disruption
Apr 9, 2026 · 7:00 PM 20h 59m
None
Resolved
Details →
Figma Make Publishing Disruption
Mar 12, 2026 · 2:00 PM 8h 11m
None
Resolved
Details →
Variant Properties Disruption
Mar 6, 2026 · 9:40 PM 20h 28m
None
Resolved
Details →
Figma Sites Publishing Disruption
Feb 17, 2026 · 2:16 PM 5h 44m
None
Resolved
Details →
Figma Make Publishing Disruption
Feb 5, 2026 · 7:05 PM 5h 29m
None
Resolved
Details →

How do they compare?

Alternatives to Figma

Common questions

Frequently Asked Questions

  • Is Figma down today?

    Check the status badge at the top of this page for the current status. Pulsetic polls the official status page every few minutes and cross-references with user reports to give you the most accurate picture.

  • How often does Figma go down?

    Based on our 90-day data, we've detected 2 incidents, of which 1 were major or critical. The median resolution time is 3h 45m.

  • How are outages detected?

    Pulsetic polls the official status page every few minutes from multiple global locations. Crowdsourced user reports provide an additional early-warning signal, often surfacing issues before the official monitors catch them.

  • Is it down for everyone or just me?

    The outage map and region breakdown help answer this. If reports are concentrated in one area it may be regional; if hotspots appear globally it's a widespread outage. Submit your own report to help others understand the scope.

  • What does "never acknowledged" mean?

    "Never acknowledged" means Pulsetic detected a real service disruption, confirmed by multiple user reports, but the official status page never posted an incident for it. This is one of the core reasons teams use third-party monitoring alongside official status pages.