Fullstory logo

Is Fullstory Down?

AnalyticsLive status, outages, and incident history

No. Fullstory is up right now.

Every monitored Fullstory system is operational as of November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Fullstory breaks

Fullstory is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Fullstory status page
How we know: the official Fullstory status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Fullstory Status Summary

As of 22:52 UTC on 9 November 2026, Fullstory is operational. PulsAPI checked Fullstory's official status page and found 18 of 18 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Fullstory, counting degraded performance as up. The latest incident, "[Resolved] Delayed Session Data Availability (NA1 & EU1 Data Centers)", was on Nov 4, 2026.

Cite as: PulsAPI, “Fullstory status”, checked 9 November 2026, 22:52 UTC. https://www.pulsapi.com/services/fullstory

Fullstory Component Status

The main Fullstory systems on this page. All 18 are operational right now.

18operational
EU1 Data Center » Anywhere: Warehouse
Operational
EU1 Data Center » API
Operational
EU1 Data Center » Data Capture - Native Mobile
Operational

15 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking EU1 Data Center » Data Capture - Web, EU1 Data Center » Fullstory Web Application, EU1 Data Center » Guides and Surveys, EU1 Data Center » StoryAI, EU1 Data Center » Webhooks & Alerts, EU1 Data Center » Workforce, NA1 Data Center » Anywhere: Warehouse, NA1 Data Center » API, NA1 Data Center » Data Capture - Native Mobile, NA1 Data Center » Data Capture - Web, NA1 Data Center » Fullstory Web Application, NA1 Data Center » Guides and Surveys, and 3 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Fullstory Outages & Incidents

Incident history from the official Fullstory status page, including resolution updates.

[Resolved] Delayed Session Data Availability (NA1 & EU1 Data Centers)Resolved Nov 4, 2026Resolved

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 page definitions configured. The issue is now resolved and any backlogged data is currently being processed and will be available shortly. Configured alerts reliant on entry page, exit page, and next page data would not have received during this issue timeframe. If you have any questions or are experiencing any continued issues, please reach out to support@fullstory.com.

Delays in syncing to S3 data warehouses (EU1)Resolved Nov 4, 2026 · 8h 46mResolved

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. --- [2026-11-04T06:47:11.928-05:00] (monitoring) From 16:00 UTC on the 3rd of November, EU1 orgs may notice a drop in data synced to EU1 data warehouses. We have rolled back the deployment responsible and are currently monitoring the data syncs.

Failure to load assets during playback for sessions (EU1 Data Center)Resolved Sep 23, 2026 · 0 minResolved

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.

Fullstory Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Fullstory incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
Aug 1199.80% average · 5 days with incidentsNov 9

Going further back: Fullstory uptime by month and every recorded Fullstory outage.

Live Fullstory Outage Reports

Problems reported by engineers using Fullstory. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Fullstory problems reported yet.

Something wrong with Fullstory on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Fullstory

Is Fullstory down? Fullstory reports live availability for 20 components at status.fullstory.com, among them Data Capture - Web, NA1 Data Center and Data Capture - Native Mobile. Track Fullstory outages, degradations and past incidents here, with uptime history and alerts across your analytics stack.

Over the past 30 days, PulsAPI has measured Fullstory uptime at 100.00%. Response times, incident history, and SLA tracking for Fullstory are available on the PulsAPI dashboard.

Fullstory Status FAQ

Is Fullstory down right now?

The verdict at the top of this page comes from the latest poll of the official Fullstory status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Fullstory is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Fullstory recovers.

How do I check Fullstory uptime history?

PulsAPI tracks Fullstory uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Fullstory changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Fullstory outages?

PulsAPI reads the official Fullstory status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Fullstory components?

Yes. PulsAPI monitors 18 individual Fullstory components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Fullstory goes down?

Yes. Create a free account and subscribe to Fullstory: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Fullstory to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Fullstory problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Fullstory?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Fullstory plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Fullstory with the rest of your stack

2660+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services