Is Fullstory Down?

No — Fullstory is up

Reachable from all 8 checked regions

Average response time: 585ms

Last checked 1 hour ago · checks run every 6 hours

Official status page: https://status.fullstory.com

Fullstory uptime

—

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Aug 12 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

arn

712ms

DNS 0ms TCP 6ms TLS 22ms TTFB 710ms

bom

1401ms

DNS 0ms TCP 2ms TLS 69ms TTFB 1399ms

cdg

525ms

DNS 0ms TCP 2ms TLS 12ms TTFB 523ms

dfw

158ms

DNS 0ms TCP 1ms TLS 6ms TTFB 156ms

ewr

254ms

DNS 0ms TCP 7ms TLS 13ms TTFB 252ms

fra

575ms

DNS 0ms TCP 11ms TLS 13ms TTFB 573ms

gru

860ms

DNS 0ms TCP 2ms TLS 56ms TTFB 858ms

iad

199ms

DNS 0ms TCP 2ms TLS 10ms TTFB 197ms

What Fullstory does

Fullstory records how people use a website or mobile app, replaying sessions and building product analytics from what it captures. Product, support and design teams use it to see what a user actually did before they complained. The capture script runs on customers' own sites, so an incident affects data collection rather than the site itself.

What an outage looks like

Your own site keeps working, because the capture script fails independently of the page it runs on. What breaks sits inside Fullstory: sessions are missing or arrive late, replays load without styling so the page looks broken in playback, and searches return fewer sessions than expected. Webhooks and alerts stop firing and warehouse exports stall.

What to do about it

Check Fullstory's status page and find your own data center row, since NA1 and EU1 are reported separately and an incident often touches only one. Data Capture, the web application, API, Webhooks and Alerts, and warehouse export are separate components. Missing sessions frequently backfill once indexing catches up, so wait before concluding data was lost.

Is it down for everyone, or just you?

If this page says Fullstory is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Fullstory outage FAQ

Is my website affected when Fullstory is down?

No. The capture script loads asynchronously and does not block your pages, so visitors browse and buy normally while Fullstory is unavailable. The cost is observability: you lose the recording of what those visitors did. That gap is usually noticed later, when someone goes looking for a session that was never captured.

Are my missing sessions gone for good?

Often not. Several Fullstory incidents have been indexing delays rather than capture failures, meaning the data arrived but was not yet searchable, and sessions appear once indexing catches up. A genuine Data Capture outage is different and does lose the sessions that occurred during it, since there is nothing to backfill from.

Why does my session replay look unstyled?

Replay pulls stylesheets and assets to reconstruct the page, so a fault in that path renders the recording without its CSS. Fullstory has reported exactly this as an incident affecting some customers. The underlying session data is intact; the playback rendering is what is degraded, and replays usually look correct again after the fix.

Does an outage in one data center affect the other?

Not usually. Fullstory splits its status reporting between NA1 and EU1, each with its own capture, API, application and warehouse components. Your organisation lives in one of them, so an incident in the other has no effect on your data. Check the row matching your region rather than the headline.

How we measure this

We request Fullstory's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Fullstory publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Fullstory goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required