FigJam: vendor-reported critical incident on September 27 (tracked 1h 30m)
Sep 27, 01:50 AM → Sep 27, 03:20 AM · 1h 30m · high
FigJam reported a critical-impact incident on its own status page. PulseWatch followed the vendor's status page and did not independently confirm the incident. PulseWatch tracked the incident for 1h 30m, from Sun, 27 Sep 2026 01:50:42 GMT to Sun, 27 Sep 2026 03:20:47 GMT. That is how long PulseWatch kept the incident open, not a measurement of how long the service was affected.
Impact
During the 1 hour and 30 minute high-severity incident, FigJam experienced a service disruption. The outage was identified through automated signals and the vendor's status page. No user-reported data was collected for this incident, and therefore, no specific user-visible features, regions, or issue types were recorded from user reports.
Incident timeline
- Sep 27, 01:50 AM
The vendor reported a critical-impact incident on its own status page; PulseWatch began tracking it
- Sep 27, 01:50 AM
Status updated: possible issue
- Sep 27, 03:20 AM
PulseWatch closed the incident
Official updates
- Sep 27, 01:50 AM
FigJam reported the incident on its status page.
View official source