Vendor record
FullStory
Checked
Front door check counts and FullStory’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented FullStory endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,879 of 2,879 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
- Endpoint checked
- api.fullstory.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every FullStory product, region or your app worked.
How we count front door checksFullStory says
Incident posts from FullStory’s status page, with its titles, impact levels and times. They say what FullStory chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
5
incidents FullStory posted, last 180 days
Median recorded duration: 5h 13m. From 5 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Delayed Session Data Availability for a Subset of NA1 Data Center Orgs
MinorFullStory’s postStarted, per FullStory
Closed in our record(14h 49m)
Multiple Fullstory Services Unavailable (NA1 Data Center)
CriticalFullStory’s postStarted, per FullStory
Closed in our record(5h 20m)
Delays for Warehouse Customers in NA1 Data Center
MinorFullStory’s postStarted, per FullStory
Closed in our record(2h 32m)
Anywhere: Warehouse (BigQuery) - Degraded performance in NA1 Data Center
MinorFullStory’s postStarted, per FullStory
Closed in our record(5h 13m)
Google outage degrading some StoryAI features
MinorFullStory’s postStarted, per FullStory
Closed in our record(2h 11m)
Your code, your dependencies
See which of your code paths call FullStory
Connect GitHub or GitLab to find where your public or private repository uses FullStory. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add FullStory status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is FullStory currently down?
FullStory's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did FullStory last have an outage?
The most recent closed incident record began 39 days ago and spans 14h 49m. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for FullStory?
No. CheckUpstream checks FullStory’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor FullStory in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track FullStory?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.