Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

PostHog US Outage History

Every past PostHog US outage tracked by IsDown, with detection times, duration, and resolution details.

There were 358 PostHog US outages since March 2023. The 165 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor March 3, 2026

March 2026: Errors affecting some queries

Detected Mar 3, 2026 10:49 PM EST · Resolved Mar 3, 2026 11:55 PM EST · Duration about 1 hour

PostHog experienced an issue causing analytics queries to timeout or fail, affecting dashboards, insights, and other query-driven views which became slow or unavailable. The incident lasted 1.1 hours and was classified as minor severity. The service was restored after the query performance issues were resolved.

Major March 3, 2026

March 2026: Web app not accessibe

Detected Mar 3, 2026 11:59 AM EST · Resolved Mar 3, 2026 12:54 PM EST · Duration about 1 hour

PostHog's web application was inaccessible for 55 minutes due to access issues. The service has been restored and the team is monitoring performance to ensure stability.

Minor March 2, 2026

March 2026: Errors loading some queries / dashboards

Detected Mar 2, 2026 3:37 PM EST · Resolved Mar 3, 2026 6:26 AM EST · Duration about 15 hours

PostHog experienced a 14.8-hour incident where a sharp spike in query volume caused database overload, resulting in failed queries, dashboard loading errors, and event ingestion lag for customers in the US region. The team restarted affected services and adjusted application retry behavior to restore functionality, while continuing to monitor and investigate the underlying cause of the query volume spike.

Minor March 2, 2026

March 2026: Web app not accessibe

Detected Mar 2, 2026 11:39 AM EST · Resolved Mar 2, 2026 12:25 PM EST · Duration about 1 hour

PostHog's web app experienced accessibility issues that prevented users from accessing the service. The incident was classified as minor and lasted 45 minutes. The team investigated and resolved the access problems, restoring normal service functionality.

Minor March 2, 2026

March 2026: Feature flags API: elevated error rates

Detected Mar 2, 2026 11:34 AM EST · Resolved Mar 2, 2026 12:29 PM EST · Duration about 1 hour

PostHog's feature flags API experienced elevated error rates for 55 minutes, causing flag evaluations to fail or fall back to default behavior for some requests. The issue was caused by increased database load, which was resolved by provisioning a new database instance. API request responses returned to normal after the new database resources were deployed.

Minor March 2, 2026

March 2026: PostHog AI: elevated API error rates

Detected Mar 2, 2026 7:49 AM EST · Resolved Mar 2, 2026 9:25 AM EST · Duration about 2 hours

PostHog AI experienced elevated API error rates caused by upstream provider issues. The service disruption lasted 1.6 hours while the team monitored the situation. This was classified as a minor incident affecting the AI functionality within PostHog.

Minor February 27, 2026

February 2026: Event ingestion: processing delays

Detected Feb 27, 2026 4:15 AM EST · Resolved Feb 27, 2026 5:36 AM EST · Duration about 1 hour

PostHog experienced processing delays in their event ingestion pipeline at the final Clickhouse ingestion stage, causing events to take longer than usual to appear in the product. While no data was lost, users experienced delays in seeing events show up in PostHog apps and queries. The processing delays were resolved after 1.4 hours with processing times returning to normal levels.

Minor February 25, 2026

February 2026: Event ingestion: processing delays

Detected Feb 25, 2026 9:05 PM EST · Resolved Feb 26, 2026 12:12 PM EST · Duration about 15 hours

PostHog experienced a 15.1-hour event ingestion processing delay caused by a degraded shard during routine maintenance and elevated part counts on ClickHouse, which led to insert rejections and Kafka consumer lag. Events took longer than usual to appear in PostHog apps and queries, though no data was lost during the incident. The root cause was identified and resolved, with ingestion resumed and the backlog processed over approximately 2 hours.

Minor February 19, 2026

February 2026: Logs ingestion delayed in US Cloud

Detected Feb 19, 2026 3:17 PM EST · Resolved Feb 23, 2026 6:01 AM EST · Duration 4 days

PostHog's logs ingestion service in the US region experienced a database corruption issue that initially caused 30-minute delays but escalated to complete data loss for all customer logs prior to February 16th, 21:00 UTC. The incident affected only the new Logs product, while other PostHog services like analytics events and replays remained unaffected due to isolated infrastructure. PostHog restored the service by removing corrupted database files and successfully backfilled available backup data within 24 hours, returning the logs service to normal operation.