We started checking FullStory on November 2, 2026, which is 5 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when FullStory reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what FullStory's own status page declared. Below it, any public chatter we saw about FullStory and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what FullStory's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about FullStory in the last 24 hours, which is not evidence that nothing is wrong.
FullStory's status page
Delays in syncing to S3 data warehouses (EU1): minor incident
Delays in syncing to S3 data warehouses (EU1): minor incident, from before this window to 20:45 UTC.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is FullStory's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention FullStory next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
449
US-West
100.00%
348
Europe
100.00%
319
Asia-Pacific
100.00%
193
Their declared record
FullStory's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Delays in syncing to S3 data warehouses (EU1)Minor incident
Nov 4, 2026, 11:47 AM UTC to Nov 4, 2026, 8:33 PM UTC (8h 46m)resolved
their latest update (Nov 4, 2026, 8:33 PM UTC): Backlogged warehouse data has been successfully synced.
If you have any questions or are experiencing any continued issues, please don't hesitate to reach out to our team at support@fullstory.com.
[Resolved] Delayed Session Data Availability (NA1 & EU1 Data Centers)All systems operational
Nov 3, 2026, 10:30 PM UTC to Nov 3, 2026, 10:30 PM UTC (0 min)resolved
their latest update (Nov 3, 2026, 10:30 PM UTC): From November 2, 2026 at 11:00 AM (ET) to November 3, 2026 at 4:10 PM (ET), there was an issue that caused delays in session data availability in the Fullstory Web Application. During this time, entry page, exit page, and next page data was not available for organizations with pa…
Failure to load assets during playback for sessions (EU1 Data Center)Partial outage
Sep 23, 2026, 7:00 PM UTC to Sep 23, 2026, 7:00 PM UTC (0 min)resolved
their latest update (Sep 23, 2026, 7:00 PM UTC): A change was made on the 23rd of September to how URLs for captured assets are resolved; this inadvertently led to playback being broken for sessions in the EU1 Data Center. This was fixed by rolling back this change at 9:45am UTC.
Delayed Session Data Availability for a Subset of NA1 Data Center OrgsMinor incident
Sep 7, 2026, 3:00 PM UTC to Sep 8, 2026, 5:46 AM UTC (14h 46m)resolved
their latest update (Sep 8, 2026, 5:46 AM UTC): This incident has now been resolved. If you are experiencing any issues past 6:15 PM (ET), please email us at support@fullstory.com.
Multiple Fullstory Services Unavailable (NA1 Data Center)Major outage
Sep 1, 2026, 3:19 PM UTC to Sep 1, 2026, 8:36 PM UTC (5h 17m)resolved
their latest update (Sep 1, 2026, 8:36 PM UTC): The issue reported by our cloud infrastructure provider (Google Cloud Platform) is now resolved and Fullstory services are fully operational as of September 1st, 2026 at 4:32 PM (ET).
Any backlogged data is currently being processed and will be available shortly.
If you have an…
Delays for Warehouse Customers in NA1 Data CenterMinor incident
Aug 18, 2026, 5:57 PM UTC to Aug 18, 2026, 8:24 PM UTC (2h 27m)resolved
their latest update (Aug 18, 2026, 8:24 PM UTC): The issue that caused delays for Silver Schema warehouse customers in the NA1 region has been resolved and service is back to full operation as of August 18th, 2026 at 4:23 PM ET.
If you have any questions or are experiencing any continued issues, please don't hesitate to reach…
Guides & Surveys: Users unable to create or edit tours and smart tips; end-user content delivery disruption (NA1 & EU1)All systems operational
Aug 6, 2026, 7:00 PM UTC to Aug 6, 2026, 7:00 PM UTC (0 min)resolved
their latest update (Aug 6, 2026, 7:00 PM UTC): From 7:58pm UTC on the 6th of August, users in NA1 & EU1 organisations with Guides & Surveys enabled were unable to create or edit tours and smart tips. There was also some disruption of end-user content delivery, though this was mitigated by edge caching serving cached content.
…
Anywhere: Warehouse - Delayed data syncs in NA1 Data CenterMinor incident
Jul 23, 2026, 3:46 PM UTC to Jul 23, 2026, 8:58 PM UTC (5h 12m)resolved
their latest update (Jul 23, 2026, 8:58 PM UTC): This incident is resolved. The underlying BigQuery degradation has been mitigated, and the data transformation layer that Fullstory uses for Anywhere: Warehouse in NA1 has returned to normal operation. Any syncs that were delayed during this period have now caught up, and affecte…
Google outage degrading some StoryAI featuresMinor incident
Jul 16, 2026, 8:38 PM UTC to Jul 16, 2026, 10:41 PM UTC (2h 2m)resolved
their latest update (Jul 16, 2026, 10:41 PM UTC): This incident has been resolved
[Resolved] Incorrect filter values on default metrics, NA1 Data CenterAll systems operational
Jul 6, 2026, 12:30 PM UTC to Jul 6, 2026, 12:30 PM UTC (0 min)resolved
their latest update (Jul 6, 2026, 12:30 PM UTC): Between July 6, 2026 at 8:47 AM EDT and July 7, 2026 at 12:00 PM EDT, incorrect filter configurations were intermittently applied to the default canned metrics (Users Today, Sessions Today, Error Rate, and Avg Page Load Time), which could have caused them to display unexpected fi…
Showing the 10 most recent of 52 incidents FullStory has declared in the history we hold.
These entries are FullStory's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
FullStory's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.