Userpilot Outage History
Userpilot is up right nowPingoru has recorded 28 incidents for Userpilot: 26 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 6 of 720 (1%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 1 | 1 of 720 (0%) |
| July 2026 | 13 | 3 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 743 (0%) |
Incidents, newest first
Major October 20, 2025 SSO Unavailable 1h 30m section-1995 (Web Application), section-1995 (Web Application)
Started Oct 20, 2025, 08:00 AM UTC· resolved Oct 20, 2025, 09:30 AM UTC
- investigating Oct 20, 2025, 08:00 AM UTC
Our SSO service is impacted by the AWS incident in US-EAST-1. We are currently investigating options for restoring the SSO service despite the AWS incident.
- resolved Oct 20, 2025, 09:30 AM UTC
SSO Service has recovered. Our team continues to monitor the situation with our cloud provider.
Minor October 14, 2025 System Degradation 1h 41m section-1995 (Event Ingestion (US - Standard))
Started Oct 14, 2025, 03:27 PM UTC· resolved Oct 14, 2025, 05:08 PM UTC
- investigating Oct 14, 2025, 03:27 PM UTC
We are experiencing service degradation. Our team is actively monitoring and working to restore full performance.
- resolved Oct 14, 2025, 05:08 PM UTC
We’ve taken steps to address the service degradation and are closely monitoring performance. Post Mortem What happened: After upgrading our columnar database, an incompatibility stopped automatic consolidation on a core table. Impact: Partial data loss and content triggering issues. Cause: The new version didn’t work correctly with tables that use pre-computed summaries, leading to too many small data fragments. Fix: Rebuilt the summaries to force consolidation and rolled back to the prior database version. Performance recovered. Prevention: Added an alert on fragment count, paused similar upgrades, and expanded compatibility/performance testing before future releases. We’re sorry for the disruption and appreciate your patience.
- investigating Oct 14, 2025, 05:08 PM UTC
We’ve taken steps to address the service degradation and are closely monitoring performance. ## Post Mortem **What happened**: After upgrading our columnar database, an incompatibility stopped automatic consolidation on a core table. **Impact**: Partial data loss and content triggering issues. **Cause**: The new version didn’t work correctly with tables that use pre-computed summaries, leading to too many small data fragments. **Fix**: Rebuilt the summaries to force consolidation and rolled back to the prior database version. Performance recovered. **Prevention**: Added an alert on fragment count, paused similar upgrades, and expanded compatibility/performance testing before future releases. We’re sorry for the disruption and appreciate your patience.