Skip to content

Outage tracker / FullStory

Is FullStory down?

Short linkrlup.io/down/fullstory

I'm having a problem

Vendor reports no incidentWhat FullStory reports

FullStory reports no incident on its status page.

As of the last successful poll, 2026-11-05 14:44 UTC.

FullStory's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked moments ago

Our checks of FullStory pass from all 4 regions we check.

As of Nov 5, 2026, 2:57 PM UTC, RealUptime's checks of FullStory passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:57 PM UTC
US-East565 msChecks passing
US-West867 msChecks passing
Europe865 msChecks passing
Asia-Pacific1692 msChecks passing
their status pagetheir claim, not our reading

FullStory reports: All systems operational (“All Systems Operational”)

from FullStory's own status page, checked Nov 5, 2026, 2:27 PM UTC

FullStory's own component breakdown, as they publish it

  • Data Capture - WebOperational
  • Data Capture - WebOperational
  • Data Capture - Native MobileOperational
  • Data Capture - Native MobileOperational
  • APIOperational
  • APIOperational
  • Fullstory Web ApplicationOperational
  • Fullstory Web ApplicationOperational
  • Webhooks & AlertsOperational
  • Webhooks & AlertsOperational
  • Anywhere: WarehouseOperational
  • Anywhere: WarehouseOperational
  • Guides and SurveysOperational
  • Guides and SurveysOperational
  • StoryAIOperational
  • StoryAIOperational
  • WorkforceOperational
  • WorkforceOperational

These are FullStory's components, named and scored by FullStory. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is FullStory's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

FullStory response time, by region

US-East
1.6sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.6s
Oct 7Oct 21Nov 5
US-West
1.4sp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.8s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 1.4s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
Europe
1.3sp95 · latest
2s1s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 713ms2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.2s2026-11-05 UTC: p95 1.3s
Oct 7Oct 21Nov 5
Asia-Pacific
2.1sp95 · latest
2.5s1.3s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.7s2026-11-03 UTC: p95 1.4s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.1s
Oct 7Oct 21Nov 5
Why some readings show as awaiting data. 1 of 8 readings for FullStory came back as a filtered response to our automated checks (a response code that refuses automated clients, such as 403, 405, 406, 429 or 451, a redirect loop, or a timeout that a second endpoint answered) rather than a normal pass or failure. That tells us about our own probe's reception, not about FullStory's health, so we publish no verdict for those readings rather than guessing in either direction. Read how we tell the difference.

Check your own site while you wait on FullStory

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not FullStory. It cannot diagnose FullStory's own systems.

What we measured, function by function

FullStory answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Awaiting dataUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Email me when FullStory reports an incident on its status page, and again when it reports it resolved.

Get an email when FullStory reports an incident

Email me when FullStory reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is FullStory's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 565msstatus code: 401checked: Nov 5, 2026, 2:53 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach FullStory normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 867msstatus code: 401checked: Nov 5, 2026, 2:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach FullStory normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionFullStory is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionFullStory is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionFullStory is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 865msstatus code: 401checked: Nov 5, 2026, 2:55 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach FullStory normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionFullStory is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 1692msstatus code: 401checked: Nov 5, 2026, 2:57 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach FullStory normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionFullStory is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionFullStory is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using FullStory, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for FullStory yet, which is not evidence that nothing is wrong.

Recent probe events

Delays in syncing to S3 data warehouses (EU1), 8h 46mdeclared on their status page2026-11-04
[Resolved] Delayed Session Data Availability (NA1 & EU1 Data Centers), 1mdeclared on their status page2026-11-03
Failure to load assets during playback for sessions (EU1 Data Center), 1mdeclared on their status page2026-09-23
Delayed Session Data Availability for a Subset of NA1 Data Center Orgs, 14h 46mdeclared on their status page2026-09-07
Multiple Fullstory Services Unavailable (NA1 Data Center), 5h 17mdeclared on their status page2026-09-01
Delays for Warehouse Customers in NA1 Data Center, 2h 27mdeclared on their status page2026-08-18
Guides & Surveys: Users unable to create or edit tours and smart tips; end-user content delivery disruption (NA1 & EU1), 1mdeclared on their status page2026-08-06
Anywhere: Warehouse - Delayed data syncs in NA1 Data Center, 5h 12mdeclared on their status page2026-07-23

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring FullStory since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for FullStory covering any window you pick, with our check readings and FullStory's own claim at the time, side by side.

Full check history for FullStory: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

FullStory uptime by RealUptime's checksLive, from this page's own readings.
[![FullStory uptime by RealUptime's checks](https://realuptime.io/outages/fullstory/badge.svg?days=30)](https://realuptime.io/outages/fullstory)
<a href="https://realuptime.io/outages/fullstory"><img src="https://realuptime.io/outages/fullstory/badge.svg?days=30" alt="FullStory uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is FullStory down?", https://realuptime.io/outages/fullstory. The readings change with every check, so give the date you read them.

What we check

primaryfunctional: live API
https://api.fullstory.com/v2/users
secondary
https://www.fullstory.com/
secondary
https://status.fullstory.com/

What our check can and cannot see

A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.

Host checked: api.fullstory.com

RealUptime is not affiliated with FullStory; the name identifies what we checked, and nothing here speaks for FullStory's own team. We send a single web request to FullStory from 4 regions on our own schedule and time the response. We do not see inside FullStory's systems, do not use an account or real transaction, and are not the same signal FullStory's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for FullStory is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. FullStory operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 3762 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

1PasswordAWS (Amazon Web Services)AblyAcuity SchedulingAdobe Fonts