An online whiteboard tool by Figma designed for team brainstorming, diagramming, and interactive project planning.
Are you on the FigJam team and see something inaccurate? Report it to us. We respond within one business day.
Is FigJam down right now?
No. FigJam has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
FigJam is operating normally
No elevated reports in the last 15 minutes. Baseline 5 reports/hour.
Reports 24h
0
Last incident
None recorded
Trend
0/15m
Baseline
5/hr
Product checks
Coverage gap: no product check is qualified to corroborate an incident for this service. Homepage and gateway checks do not verify the affected workflow.
Observed health
Unknown
No samples qualify for a combined success and latency score.
Evidence strength
No current issue evidence
No current corroborated or observed finding.
Evidence describes support for an issue, not its outage probability.
Monitoring coverage
0/0 configured operation checks fresh
0 qualified operation checks · 0 measurement origins.
Other operations and customer regions remain unverified.
How this score works
100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.
A component issue stays visible even when other operations pass. Forecasts are separate from current health.
30 days incident history
Daily incident severity and duration for FigJam.
0
Incident days
30
No recorded incident
0 min
Recorded duration
30-day outage frequency
Recorded incidents per day and recorded incident duration for FigJam. Hover a day for detail.
Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.
0
Days with incidents
0 incidents
Busiest day
0 min
Recorded duration
Report volume
0 reports in last 24H
Issue types
No data
Top cities
No location data
Top providers
No provider data
Reliability
Detected by PulseWatch30-day uptime
99.99%
90-day uptime
99.99%
Calculated from FigJam's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.
Other productivity services we monitor
Browse all- Normal
AI21 Labs
Is AI21 Labs down? Live status & reports.
- Normal
ActiveCampaign
Is ActiveCampaign down? Live status & reports.
- Normal
Acuity Scheduling
Is Acuity Scheduling down? Live status & reports.
- Normal
Aha!
Is Aha! down? Live status & reports.
- Normal
Airtable
Is Airtable down? Live status & reports.
- Normal
Amplitude
Is Amplitude down? Live status & reports.
Community reports
0 comments
Confirm what you're seeing — your report helps others know if it's just them.
Be the first to post a report.
Incident timeline
Scrub through detection, peak, status updates, and resolution.
No incidents recorded for this service.
Subscribe to updates
Get an email the moment FigJam enters an incident — and again when it's resolved. No account required.
Free for anyone. Unsubscribe anytime from any email we send.
Signal quality
- 0 reports aggregated in last 24h
- Crowdsourced baseline detection
- Official status page
Live signal
- Status
- Normal
- Monitoring
- Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).
- Coverage
- Verified against the vendor's own incident history
- Reports (24h)
- 0
- Baseline / hour
- 5
- Open threshold
- 3x
Official site
www.figma.com/figjam