Agent runs: elevated API error rates
ResolvedOfficial update
The issue has been resolved and agent cloud tasks are healthy again
The latest update from PostHog.
State
Resolved
Started
83 d ago
2026-08-11 07:35 UTC
Lasted
20 min
until 2026-08-11 07:55 UTC
Worst impact
Partial outage
Timeline
2 updates07:3507:4007:4507:5007:55
Partial outageUpdate postedTimes in UTC
Investigating
20 min 100%
Updates
Times in UTCAs posted by PostHog
Resolved2026-08-11 07:55 UTC
The issue has been resolved and agent cloud tasks are healthy again
Investigating2026-08-11 07:35 UTC
We’re investigating elevated API error rates impacting parts of the application.
Affected components
3Cloud AI Agents01KTQC5C6Y19HPGSNJN2RCZFJA01KTQC5C6Y2R2P18SD3T1W7100
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=posthogSlack
/feed subscribe https://outages.cc/feed.xml?providers=posthogFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane