outages.live
Live
PostHogIncident · 2026-10-06 15:56 UTC

Warehouse sources delayed imports

ResolvedOfficial update

Warehouse sources backlog has been processed

The latest update from PostHog.

State

Resolved

Started

26 d ago

2026-10-06 15:56 UTC

Lasted

1 h 2 min

until 2026-10-06 16:58 UTC

Worst impact

Degraded

Timeline

2 updates
15:5616:1116:2716:4216:58
DegradedUpdate postedTimes in UTC

Monitoring

1 h 2 min 100%

Updates

Times in UTC

As posted by PostHog

Resolved2026-10-06 16:58 UTC

Warehouse sources backlog has been processed

Monitoring2026-10-06 15:56 UTC

There's a delay in processing warehouse sources imports - we've identified the issue and have applied a fix. Now monitoring the backlog - there is no data loss

Affected components

1
Data Warehouse Source Ingestion

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