Statusfield Logo and Service Monitoring DashboardStatusfield
Fullstory

Fullstory Incident History

Get real-time status information for Fullstory. Our monitoring system continuously checks Fullstory's services and components across all global regions to provide you with the most up-to-date status information.

Fullstory is currently Operational. This means all systems are operating normally. In order to get more details about the status of the service, please check the detailed status information below

Live Status for Fullstory is OperationalLive Status
Operational
Last checked

Historical record of incidents for Fullstory

Mar 28, 2025

Scheduled Maintenance

Last update
Completed

The scheduled maintenance has been completed.

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

Fullstory will be conducting scheduled maintenance for our EU data center on Thursday, March 27th between 7:00 PM EDT through 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

Mar 19, 2025

Slow or failure to load Fullstory

Last update
Resolved

We have implemented a fix that has resolved the issue and our team is still actively investigating the underlying cause to prevent future occurrences. Please reach out to support@fullstory.com if you experience any further issues.

Monitoring

At 4:11 PM EDT, we detected an issue that resulted in degraded performance on Fullstory. The service has been restored, and we are actively investigating the root cause. We will provide further updates as our investigation progresses. If you encounter any additional issues or have questions, please contact support@fullstory.com.

Update

We are continuing to investigate this issue.

Investigating

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.