CheckUpstream measured FullStory at 100.000% availability across 2825 independent checks (global · api). 3 incidents were recorded in the past 12 months; the most recent resolved 13 days ago after 3 hours. Status signals are polled from FullStory's official Atlassian Statuspage status page, alongside independent probes and community reports.
Share of our own checks against FullStory endpoints that returned FullStory's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 3 incidents · 364 of 365 days with none posted · 45m of declared impact
Fewer incidents in the last 30 days than 45% of 232 tracked services.
Share of each window with no impact declared by FullStory
7d
100.000%
30d
99.894%
90d
99.965%
180d
99.982%
1y
99.991%
Downtime like this can be refundable
If you're a paying FullStory customer, outages in these windows may count against FullStory's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A FullStory outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is FullStory currently down?
FullStory is currently Operational. CheckUpstream tracks FullStory in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
›When did FullStory last have an outage?
FullStory's last resolved incident started 13 days ago and lasted 2h 32m (degraded performance).
FullStory's 30-day measured availability is 100.000%, from CheckUpstream's own probes against FullStory endpoints. It is the share of checks that returned the expected response, not a figure taken from FullStory's status page.
›How do I monitor FullStory in production?
Sign up to CheckUpstream and add FullStory to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track FullStory?
We poll FullStory's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.