rewindex

CompaniesFigmaIncidents

Figma: Reports of service disruption

No impact listedStatus: resolvedStarted Resolved (9 d)1 updatestatus.figma.com (opens in new tab)

Timeline of updates

  1. resolved

    The incident resulted from increased global network congestion. We were able to resolve the issue by deploying a CDN for users to connect to in Europe and Asia.

From Figma’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.figma.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Figma, started 2020-04-01 07:59 UTC, resolved after 9 d, 1 update(s).

Title
Reports of service disruption
Vendor
Figma
Date
URL
https://rewindex.com/company/figma/incidents/bqq1sgh5gd0r

Figma profileRecent Figma incidentsAll outages on April 1, 2020Figma in April 2020MarkdownJSON