CheckUpstream measured FullStory at 100.000% availability across 672 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.
7 days measured availability how this is computed
100.000%
global · api · n=672 · p95 413ms (7d)
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.
FullStory posted no incidents in this window. That is either a clean run or a communication policy — from outside, the two look identical.
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%
Does FullStory actually matter to you?
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.
Check a repository →Aug 18, 17:57 UTC · resolved in 2h 32m · Resolved
Jul 23, 15:46 UTC · resolved in 5h 13m · Resolved
Jul 16, 20:38 UTC · resolved in 2h 11m · Resolved
Live FullStory status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/fullstory)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
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.
FullStory's last resolved incident started 13 days ago and lasted 2h 32m (degraded performance).
Looking for the live "is FullStory down" view? See the FullStory Live status page.
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.
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).
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.