outages.live
Live

PostHog

PostHog is operational

Checked 3 min ago Operational

History

90 days agoToday

Incidents in 90 days

28

Days with an incident

22

Median duration

1 h 14 min

Longest incident

27 h 36 min

Components

31

US Cloud 🇺🇸

App (Web & Desktop) Operational
90 days ago5 days with an incidentToday
Event Ingestion Success Operational
90 days agoNo incidentsToday
Event Ingestion Lag Operational
90 days agoNo incidentsToday
Error Tracking Ingestion Lag Operational
90 days agoNo incidentsToday
Session Replay Ingestion Operational
90 days agoNo incidentsToday
Logs Operational
90 days agoNo incidentsToday
Feature Flags API Operational
90 days ago1 day with an incidentToday
Destination Delivery (realtime) Operational
90 days ago3 days with an incidentToday
Destination Delivery (batch exports) Operational
90 days agoNo incidentsToday
Data Warehouse Source Ingestion Operational
90 days ago3 days with an incidentToday
Workflows Operational
90 days ago3 days with an incidentToday
Cloud AI Agents Operational
90 days ago7 days with an incidentToday
MCP Server Operational
90 days ago3 days with an incidentToday
REST API Query endpoints Operational
90 days agoNo incidentsToday
All other REST API endpoints Operational
90 days agoNo incidentsToday

EU Cloud 🇪🇺

App (Web & Desktop) Operational
90 days ago1 day with an incidentToday
Event Ingestion Success Operational
90 days agoNo incidentsToday
Event Ingestion Lag Operational
90 days agoNo incidentsToday
Error Tracking Ingestion Lag Operational
90 days agoNo incidentsToday
Session Replay Ingestion Operational
90 days agoNo incidentsToday
Logs Operational
90 days ago1 day with an incidentToday
Feature Flags API Operational
90 days agoNo incidentsToday
Destination Delivery (realtime) Operational
90 days ago1 day with an incidentToday
Destination Delivery (batch exports) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 27, 2026

Duration2 h 40 min10:23 to 13:02Agents: elevated GitHub error ratesDegraded

We’ve deployed a mitigation for transient GitHub errors and haven’t observed further failures since.

Oct 22, 2026

Duration59 min21:00 to 21:59Application: partial outageDegraded

All services have returned to normal.

Oct 13, 2026

Duration10 min18:14 to 18:24PostHog AI connectionsDegraded

This issue has been resolved. PostHog AI and other services are back to normal. Apologies for the interruption.

Oct 9, 2026

Duration1 h 48 min06:30 to 08:19Google Ads Data Warehouse source - some schemas are failing to syncDegraded

We've released a fix for this - affected Google Ads tables will catch up automatically at their next scheduled sync, or you can trigger a refresh manually to update the tables sooner.

Oct 6, 2026

Duration1 h 2 min15:56 to 16:58Warehouse sources delayed importsDegraded

Warehouse sources backlog has been processed

Sep 30, 2026

Duration1 h 23 min07:21 to 08:43PostHog failing to loadDegraded

PostHog has been loading fine after the fix and everything is back to normal.

Duration2 h 6 min01:27 to 03:33Analytics: query timeouts/failuresDegraded

We’ve rolled back the deployment which caused the issue and query failures have returned to normal levels.

Sep 28, 2026

Duration16 min19:56 to 20:12Log ingestion: processing delaysDegraded

We temporarily experienced some ingestion delays for logs in the EU cloud region, caused by updates we were applying to our ingestion pipeline. We paused these updates and log ingestion has resumed to normal latencies.

Sep 14, 2026

Duration30 min10:24 to 10:54PostHog Cloud runs are failing to bootMajor outage

Issue has been fixed

Sep 10, 2026

Duration9 min14:53 to 15:01Analytics: query timeouts/failuresDegraded

Failures and timeouts due to load have been mitigated, and we are working on improvements to prevent this from happening again.

Duration2 h 26 min08:28 to 10:54Some warehouse sources are failing to syncDegraded

This incident has been resolved. Any warehouse sources that failed to sync will catch up on their next scheduled run. A manual sync can be triggered to refresh data for affected sources sooner.

Sep 9, 2026

Duration2 h 34 min14:42 to 17:16Workflows: Email sending currently delayedDegraded

We've caught up on all Workflow emails.

Duration10 h 35 min12:32 to 23:06Insights alerts are not being triggeredDegraded

The fix has been fully deployed, and alerts on insights are back to normal.

Sep 8, 2026

Duration2 h 40 min09:39 to 12:19Realtime destinations: delivery issuesPartial outage

The issue was fixed and everything is back to normal. The impacted customers will be informed.

Sep 2, 2026

Duration1 h 3 min15:28 to 16:32PostHog AI, PostHog Desktop, Cloud Agents: elevated API error ratesDegraded

Traffic has resumed back to normal.

Duration1 h 14 min07:37 to 08:51Application: elevated Scout API error ratesDegraded

We identified and reverted the PR that triggered elevated API errors in Scouts.

Follow PostHog

Your coding agent knows when PostHog is down, and tells you when a failure is theirs, not yours. You can also get PostHog incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "posthog" and tell me if PostHog has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=posthog
Slack
/feed subscribe https://outages.cc/feed.xml?providers=posthog

Go from tracking outages to fixing production issues with Polylane.

Try Polylane