outages.live
Live
PostHogIncident · 2026-09-14 10:24 UTC

PostHog Cloud runs are failing to boot

ResolvedOfficial update

Issue has been fixed

The latest update from PostHog.

State

Resolved

Started

48 d ago

2026-09-14 10:24 UTC

Lasted

30 min

until 2026-09-14 10:54 UTC

Worst impact

Major outage

Timeline

2 updates
10:2410:3110:3910:4610:54
Major outageUpdate postedTimes in UTC

Identified

30 min 100%

Updates

Times in UTC

As posted by PostHog

Resolved2026-09-14 10:54 UTC

Issue has been fixed

Identified2026-09-14 10:24 UTC

Problem has been identified and a fix is being rolled out

Affected components

1
Cloud AI Agents

PostHog in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

28

Days with an incident

22

Median duration

1 h 14 min

This incident

59% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

27 h 36 min
median 1 h 14 min
90 days agoToday

Other PostHog incidents

All incidents

PostHog·Agents: elevated GitHub error rates

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

Resolvedresolved 5 d ago

PostHog·Application: partial outage

All services have returned to normal.

Resolvedresolved 10 d ago

PostHog·PostHog AI connections

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

Resolvedresolved 19 d ago

PostHog·Google Ads Data Warehouse source - some schemas are failing to sync

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.

Resolvedresolved 23 d ago

PostHog·Warehouse sources delayed imports

Warehouse sources backlog has been processed

Resolvedresolved 26 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane