Is FullStory Recording down? Check the current status
FullStory Recording is operational
Updated
FullStory Recording is operational
Updated
Join companies like Adobe, Coursera, and Glassdoor that use IsDown to monitor their vendors.
IsDown pulls data from FullStory's status page every few minutes and collects user-reported issues. Refresh the page to see if there are any updates.
This chart displays the number of user-reported issues over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem. We only consider an issue widespread if there are multiple reports within a short timeframe.
No comments yet
IsDown has tracked 17 incidents for FullStory Recording since started monitoring FullStory status in April 2020.
about 1 month ago · lasted about 4 hours
At 4:19pm ET, we noticed users experiencing slow loading or failure to load Fullstory. We are rolling back recent changes and continuing to investigate and fully resolve this issue. More details
2 months ago · lasted about 1 hour
We are currently experiencing delays in session processing and indexing that began at 4:00pm ET. There may be a delay in your ability to view newly captured sessions. We are investigating the issue. More details
5 months ago · lasted about 22 hours
Our team has identified an issue impacting data capture for web and mobile sessions that started October 31st, 2024 at 4:03pm ET. This issue impacted 4,770 Fullstory accounts, but only impacts about .5% of total captured sessions per account. Due... More details
We've tracked and collected 17 incidents for FullStory Recording since started monitoring FullStory status
Recording is part of FullStory. Check the FullStory's status.
2 incidents in 2025
Number of Incidents
0 issues
Last incident
33 days ago
Cloudflare
Twilio
AWS
Slack
Figma
Zoom
Intercom US
Jira Software
Calendly
Google Cloud
Google Workspace
GitLab
Zendesk
Microsoft Office 365
Azure
Why teams choose IsDown:
14-day free trial • No credit card required
Get instant alerts when your cloud vendors experience downtime. Create an internal status page to keep your team in the loop and minimize the impact of service disruptions.
FullStory Recording isn't down. You can check FullStory Recording status and incident details on the top of the page. IsDown continuously monitors FullStory Recording official status page every few minutes. In the last 24 hours, there were 0 outages reported.
FullStory Recording is currently operational. You can check FullStory Recording status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.
No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.
Currently there's no report of FullStory Recording being slow. Check on the top of the page if there are any reported problems by other users.
IsDown monitors the FullStory Recording official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.
FullStory Recording last outage was on March 18, 2025 with the title "Slow or failure to load Fullstory"
IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.
IsDown offers an easy way to monitor FullStory with maximum flexibility
IsDown monitors Recording for major outages. A major outage is when Recording experiences a critical issue that severely affects one or more services/regions. When FullStory marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.
IsDown monitors FullStory status page for minor outages. A minor outage is when Recording experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.
IsDown collects all information from the outages published in FullStory status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.
FullStory publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.
IsDown monitors FullStory and all their 12 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.
FullStory and other vendors don’t always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.
14-day free trial · No credit card required · No code required
