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 August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 26m agoLive, rechecked every 60s
Start monitoring FullstoryOfficial 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

Fullstory Component Status

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

18operational
EU1 Data Center » API
Operational
EU1 Data Center » Anywhere: Warehouse
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 » API, NA1 Data Center » Anywhere: Warehouse, 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.

Create a free account

Component statuses may change independently during partial outages.

Recent Fullstory Outages & Incidents

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

Uptime history4 days observed
Aug 8100.00% averageAug 11
Scheduled Maintenance (NA1 Data Center & EU1 Data Center)Scheduled for Aug 26, 2026 · 2h 0mScheduled

Fullstory will be conducting scheduled maintenance on August 26, 2026 from 7:00 PM to 9:00 PM (EDT). Customers may experience partial search and API unavailability as well as potential indexing delays during the period of planned maintenance. If you are experiencing any issues past 9:30 PM (EDT), please email us at support@fullstory.com.

Guides & Surveys: Users unable to create or edit tours and smart tips; end-user content delivery disruption (NA1 & EU1)Resolved Aug 7, 2026 · -1120 minResolved

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. The issue was resolved by 8:30am UTC on the 7th of August.

Anywhere: Warehouse - Delayed data syncs in NA1 Data CenterResolved Jul 23, 2026 · 5h 11mResolved

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 affected tables are up to date across all destinations (BigQuery, Redshift, Databricks, and Snowflake). The issue occurred from approximately 7:45 AM ET to 11:20 AM ET on July 23, 2026. We apologize for the disruption and thank you for your patience. Email us at support@fullstory.com if you continue to see issues. --- [2026-07-23T13:16:03.679-04:00] (monitoring) To clarify the scope of this incident: Fullstory uses BigQuery internally to transform data for all Anywhere: Warehouse customers in the NA1 data center, regardless of the final destination type. As a result, this BigQuery degradation may have delayed the sync of a small number of tables for all Anywhere: Warehouse customers in NA1 — including BigQuery, Redshift, Databricks, and Snowflake destinations — not only customers syncing directly to BigQuery. We are continuing to monitor and will provide a further update as syncs recover. --- [2026-07-23T11:46:53.697-04:00] (monitoring) We are aware of an issue with BigQuery that started around July 23, 2026 at 7:45 AM (ET) which is impacting Fullstory Anywhere: Warehouse connections utilising BigQuery. We are closely monitoring the situation and will provide updates as they become available.

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?

PulsAPI checks Fullstory every 60 seconds. 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.

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%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Fullstory.

How fast does PulsAPI detect Fullstory outages?

PulsAPI polls the official Fullstory status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

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 PulsAPI account and subscribe to Fullstory. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Fullstory status changes.

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. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Fullstory alongside up to 9 other services at pulsapi.com/signup.

Track Fullstory with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Fullstory status changes.

Start free trial