Userpilot Outage History

Userpilot is up right now

Userpilot had 13 outages in the last 2 years totaling 14h 12m of downtime — averaging 0.5 incidents per month.

There were 13 Userpilot outages since June 12, 2025 totaling 14h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.userpilot.io

Minor July 10, 2026

Delayed Data Ingestion (US ...

Detected by Pingoru
Jul 10, 2026, 04:45 PM UTC
Resolved
Jul 10, 2026, 06:20 PM UTC
Duration
1h 35m
Affected: Current status by service (Event Ingestion (US - Enterprise))
Timeline · 2 updates
  1. investigating Jul 10, 2026, 04:45 PM UTC

    We are currently experiencing a delayed data ingestion in our "Enterprise US" cluster. New data could take up to 30-45 minutes to reflect on dashboards. Our realtime service which serves your end users is unaffected. There is no data loss.

  2. resolved Jul 10, 2026, 06:20 PM UTC

    The issue has been resolved. Ingestion throughput has returned to normal operating levels, and all data is being processed as expected.

Read the full incident report →

Minor July 4, 2026

EU Region Service Degradation

Detected by Pingoru
Jul 04, 2026, 10:50 AM UTC
Resolved
Jul 04, 2026, 11:40 AM UTC
Duration
50m
Affected: Current status by service (Event Ingestion (EU))
Timeline · 2 updates
  1. investigating Jul 04, 2026, 10:50 AM UTC

    We are investigating a service degradation in the EU region.

  2. resolved Jul 04, 2026, 11:40 AM UTC

    As a follow-up, we isolated the affected subsystem under its own supervisor so that any similar external change or failure will be contained without affecting regional service availability.

Read the full incident report →

Minor April 28, 2026

Userpilot services degradation

Detected by Pingoru
Apr 28, 2026, 03:07 PM UTC
Resolved
Apr 28, 2026, 06:35 PM UTC
Duration
3h 28m
Affected: Current status by service (Event Ingestion (US - Standard))
Timeline · 4 updates
  1. investigating Apr 28, 2026, 03:07 PM UTC

    We are currently experiencing degraded performance affecting data ingestion. Some customers may notice delays in incoming data. Our engineering team is actively investigating and working to restore full performance as quickly as possible. Thank you for your patience.

  2. investigating Apr 28, 2026, 03:07 PM UTC

    We are currently experiencing degraded performance affecting data ingestion. Some customers may notice delays in incoming data. Our engineering team is actively investigating and working to restore full performance as quickly as possible. Thank you for your patience.

  3. resolved Apr 28, 2026, 05:51 PM UTC

    A fix has been implemented and deployed, and we are currently monitoring system performance to ensure stability. We will share the postmortem for this incident as a follow-up message. Thank you for your patience.

  4. resolved Apr 28, 2026, 06:35 PM UTC

    Postmortem The incident was caused by our database background optimization process not running aggressively enough. This allowed data fragments to accumulate across tables used for real-time cache loading. As the number of fragments increased, queries that normally completed in milliseconds were forced to scan across many more fragments than necessary. This significantly increased query latency and led to exhaustion of available database connections, which impacted data ingestion and content publishing performance. To resolve this, we reconfigured our database to optimize these tables more frequently and in smaller batches. This keeps fragment counts low and ensures real-time queries remain fast and stable. Additionally, we have added monitoring and alerting on fragment count and size per table so we can detect abnormal accumulation early and prevent similar incidents in the future.

Read the full incident report →

Minor February 16, 2026

Delayed Data Ingestion

Detected by Pingoru
Feb 16, 2026, 01:00 PM UTC
Resolved
Feb 16, 2026, 05:30 PM UTC
Duration
4h 30m
Affected: Current status by service (Event Ingestion (EU))
Timeline · 3 updates
  1. investigating Feb 16, 2026, 01:00 PM UTC

    We are currently experiencing a delay in data insertion affecting our ingestion pipeline.

  2. resolved Feb 16, 2026, 05:30 PM UTC

    The issue causing delays in data ingestion has been fully resolved. Ingestion throughput has returned to normal operating levels, and all data is being processed as expected. There was no data loss during the incident. We will publish a post-mortem with additional details and preventive actions in a follow-up communication. Thank you for your patience and understanding.

  3. resolved Feb 16, 2026, 05:30 PM UTC

    The issue causing delays in data ingestion has been fully resolved. Ingestion throughput has returned to normal operating levels, and all data is being processed as expected. There was no data loss during the incident. We will publish a post-mortem with additional details and preventive actions in a follow-up communication. Thank you for your patience and understanding.

Read the full incident report →

Major November 18, 2025

Degraded Performance Due to...

Detected by Pingoru
Nov 18, 2025, 12:15 PM UTC
Resolved
Nov 18, 2025, 12:53 PM UTC
Duration
38m
Affected: Current status by service (Javascript SDK)Current status by service (Web Application)Current status by service (Web Application & Chrome Extension APIs)Current status by service (Userpilot Website)
Timeline · 3 updates
  1. investigating Nov 18, 2025, 12:15 PM UTC

    We are currently experiencing a service degradation due to an ongoing outage at our CDN provider, Cloudflare. This may affect both the loading of our web application and the download of our JavaScript SDK. Impact: Some customers may be unable to load the web app or may experience very slow load times. Some customers may experience failures or timeouts when downloading our SDK. Impact may vary by region and ISP depending on Cloudflare’s edge availability. What’s happening: Our assets (including the SDK and static web resources) are served through Cloudflare. As Cloudflare is currently having issues, some requests to these assets are failing or timing out.

  2. resolved Nov 18, 2025, 12:53 PM UTC

    We have switched CDN providers temporarily. Our services are no longer affected by Cloudflare’s outage and are functioning normally. Thank you for your patience and understanding.

  3. investigating Nov 18, 2025, 12:53 PM UTC

    We have switched CDN providers temporarily. Our services are no longer affected by Cloudflare’s outage and are functioning normally. Thank you for your patience and understanding.

Read the full incident report →

Major October 20, 2025

SSO Unavailable

Detected by Pingoru
Oct 20, 2025, 08:00 AM UTC
Resolved
Oct 20, 2025, 09:30 AM UTC
Duration
1h 30m
Affected: Current status by service (Web Application)
Timeline · 2 updates
  1. 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.

  2. resolved Oct 20, 2025, 09:30 AM UTC

    SSO Service has recovered. Our team continues to monitor the situation with our cloud provider.

Read the full incident report →

Minor October 14, 2025

System Degradation

Detected by Pingoru
Oct 14, 2025, 03:27 PM UTC
Resolved
Oct 14, 2025, 05:08 PM UTC
Duration
1h 41m
Affected: Current status by service (Event Ingestion (US - Standard))
Timeline · 3 updates
  1. investigating Oct 14, 2025, 03:27 PM UTC

    We are experiencing service degradation. Our team is actively monitoring and working to restore full performance.

  2. 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.

  3. 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.

Read the full incident report →