Is Fullstory Down? How to Tell and What to Do

Fullstory captures every user session — clicks, scrolls, rage clicks, dead clicks, form interactions — to give product and CX teams a pixel-perfect replay of what users actually experience. When Fullstory degrades, session recordings stop silently. No error in your app. No alert. The sessions are just gone.

Statusfield brings reported Fullstory incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.

Follow Fullstory incidents with your team

Statusfield brings reported status for Fullstory together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

Common Signs of a Fullstory Outage

Symptom	What's likely happening
Session replays missing or incomplete	Session capture pipeline is degraded
Fullstory dashboards not loading	Query or serving infrastructure unavailable
Rage-click or dead-click heatmaps not updating	Event processing pipeline is lagging
Custom events not appearing in segments	Custom event ingestion is impacted
Fullstory → Segment or Amplitude sync delayed	Data connector pipeline is down
`FS.event()` calls silently dropping	Custom event API endpoint is degraded
Page load time in Fullstory console extremely slow	Query infrastructure is overloaded

How to Confirm It's Fullstory, Not You

Before changing your Fullstory snippet or opening a support ticket, rule out issues on your end:

1. Check the Fullstory script load in DevTools

Open DevTools → Network → filter for fullstory.com or rs.fullstory.com. The Fullstory snippet (edge.fullstory.com/s/fs.js) should load with a 200. If it's timing out or returning a 5xx, the CDN or script-serving infrastructure is down — all session capture stops immediately.

2. Check recording calls specifically

Fullstory sends recorded session data to a separate recording endpoint. Filter DevTools for rs.fullstory.com. A healthy recording flow returns 200 on these calls. Repeated failures here mean sessions are not being transmitted even if the snippet loaded fine.

3. Test FS.event() manually

Open your browser console and call FS.event('test', {source: 'debug'}). If this throws an error or returns no acknowledgment, the Fullstory object itself may not have initialized — check whether the snippet loaded at all. If it appears to succeed but the event doesn't appear in the Fullstory UI, the custom event ingestion pipeline is degraded.

4. Check your privacy rules and sampling rate

Fullstory allows teams to configure session sampling rates and privacy exclusions. A 0% sampling rate or overly broad privacy rules will cause sessions to appear missing without any platform-side outage. Verify your configuration hasn't changed before concluding it's an outage.

Use vendor reports as investigation context

A reported incident can help you decide where to investigate and what to tell your team. An operational status does not prove that your account, region or complete workflow is working. Review the affected components and timestamps alongside your own logs and checks.

What to Do During a Fullstory Outage

Immediate (first 5 minutes)

Determine scope — is the outage affecting only recording (new sessions not captured), only the UI (existing replays inaccessible), or both?
Note the exact start time — session replay outages create permanent gaps. You need to document exactly when recording stopped so your team knows which sessions to discard from UX analysis.
Check integrations — Fullstory syncs session data to tools like Heap, Segment, Amplitude, Salesforce, and Zendesk. If the Fullstory pipeline is down, those integrations stop receiving session URLs and behavioral signals.
Hold user research and UX reviews — if your team relies on Fullstory replays for active research, pause those sessions during the outage to avoid drawing conclusions from incomplete data.

Communication (first 15 minutes)

Alert your product, design, and CX teams that session replays are unavailable or incomplete for this window.
If you're in a period of active conversion optimization or UX research, document the exact outage window so future analysis accounts for the data gap.
Do not draw conclusions from funnel data correlated with Fullstory sessions during the affected window.

Recovery

After Fullstory recovers, verify that new sessions are being captured by running a test session and confirming it appears in the Fullstory UI within a few minutes.
Identify which sessions from the outage window are missing. For customer escalations that depended on replay evidence, mark them as inconclusive rather than resolved based on missing data.
If integrations were paused, confirm downstream systems (Zendesk, Amplitude) are receiving Fullstory session URLs again.

Fullstory Components and What Each Outage Looks Like

Fullstory has distinct systems that can fail independently:

Component	Impact when degraded
Snippet CDN (`edge.fullstory.com`)	Snippet fails to load; all session capture stops
Session recording pipeline (`rs.fullstory.com`)	Sessions not transmitted; recordings permanently lost
Custom event API (`FS.event()`)	Custom behavioral events dropped
Data processing / indexing	Sessions captured but not searchable or replayable
Fullstory UI / dashboard	Existing replays inaccessible; data intact but unviewable
Data connectors (Segment, Amplitude)	Downstream integrations stop receiving session data
Heatmaps and click aggregation	Heatmaps and rage-click data not updating

A snippet CDN failure is the most immediately impactful — it stops all recording the instant your page loads. A UI outage is less severe: existing sessions are safely stored, just temporarily inaccessible.

Match the check to the failure you need to catch

Follow supported Fullstory components for vendor-reported incidents. Add a public HTTPS check for your own website or API and define acceptable response codes, response time and body checks. A successful request is evidence about that endpoint, not proof that an entire customer journey works.

Use application logs and end-to-end tests for authenticated workflows, data correctness and transactions. Statusfield brings the monitoring results and vendor context together; it does not run a complete checkout or login flow.

Bring Fullstory updates to your team

Follow reported Fullstory status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.

Eligible first-time customers can start a free trial, no credit card required.

Follow Fullstory incidents with your team

Follow Fullstory and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.

Start free trial

Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.

FAQ

Is Fullstory down right now?

This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.

How can I get alerts about Fullstory incidents?

Does an operational Fullstory status mean my application is working?

No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.

Browse the service catalog and plans and alert destinations.

Is Fullstory Down? How to Tell and What to Do