# Is PostHog down? > PostHog is operational. Checked 2026-11-01 20:54 UTC. - Official status page: https://www.posthogstatus.com - Web page: https://outages.cc/posthog - JSON: https://outages.cc/api/v1/providers/posthog - RSS: https://outages.cc/feed.xml?providers=posthog ## Active incidents PostHog reports no active incident. Status pages can lag the start of a problem by a few minutes. ## Last 90 days 28 incidents on 22 of the last 90 days. - [PostHog: Agents: elevated GitHub error rates](https://outages.cc/outages/posthog-225sxyim817.md): Resolved, started 2026-10-27 10:23 UTC, lasted 2 h 40 min. We’ve deployed a mitigation for transient GitHub errors and haven’t observed further failures since. - [PostHog: Application: partial outage](https://outages.cc/outages/posthog-1lovc80lzlv.md): Resolved, started 2026-10-22 21:00 UTC, lasted 59 min. All services have returned to normal. - [PostHog: PostHog AI connections](https://outages.cc/outages/posthog-buf9lp6etq.md): Resolved, started 2026-10-13 18:14 UTC, lasted 10 min. This issue has been resolved. PostHog AI and other services are back to normal. Apologies for the interruption. - [PostHog: Google Ads Data Warehouse source - some schemas are failing to sync](https://outages.cc/outages/posthog-23o91jjh9p1.md): Resolved, started 2026-10-09 06:30 UTC, lasted 1 h 48 min. 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. - [PostHog: Warehouse sources delayed imports](https://outages.cc/outages/posthog-1721r2u72lh.md): Resolved, started 2026-10-06 15:56 UTC, lasted 1 h 2 min. Warehouse sources backlog has been processed - [PostHog: PostHog failing to load](https://outages.cc/outages/posthog-8ygqwkhfzg.md): Resolved, started 2026-09-30 07:21 UTC, lasted 1 h 23 min. PostHog has been loading fine after the fix and everything is back to normal. - [PostHog: Analytics: query timeouts/failures](https://outages.cc/outages/posthog-fgdinr2tko.md): Resolved, started 2026-09-30 01:27 UTC, lasted 2 h 6 min. We’ve rolled back the deployment which caused the issue and query failures have returned to normal levels. - [PostHog: Log ingestion: processing delays](https://outages.cc/outages/posthog-1jqnpznbr3g.md): Resolved, started 2026-09-28 19:56 UTC, lasted 16 min. 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. - [PostHog: PostHog Cloud runs are failing to boot](https://outages.cc/outages/posthog-1bua7zx6i61.md): Resolved, started 2026-09-14 10:24 UTC, lasted 30 min. Issue has been fixed - [PostHog: Analytics: query timeouts/failures](https://outages.cc/outages/posthog-smrtsclnzx.md): Resolved, started 2026-09-10 14:53 UTC, lasted 9 min. Failures and timeouts due to load have been mitigated, and we are working on improvements to prevent this from happening again. - [PostHog: Some warehouse sources are failing to sync](https://outages.cc/outages/posthog-2quiyp1cdc.md): Resolved, started 2026-09-10 08:28 UTC, lasted 2 h 26 min. 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. - [PostHog: Workflows: Email sending currently delayed](https://outages.cc/outages/posthog-11sa01rqrbq.md): Resolved, started 2026-09-09 14:42 UTC, lasted 2 h 34 min. We've caught up on all Workflow emails. - [PostHog: Insights alerts are not being triggered](https://outages.cc/outages/posthog-1fwd8hn21xz.md): Resolved, started 2026-09-09 12:32 UTC, lasted 10 h 35 min. The fix has been fully deployed, and alerts on insights are back to normal. - [PostHog: Realtime destinations: delivery issues](https://outages.cc/outages/posthog-uuqk2fb33s.md): Resolved, started 2026-09-08 09:39 UTC, lasted 2 h 40 min. The issue was fixed and everything is back to normal. The impacted customers will be informed. - [PostHog: PostHog AI, PostHog Desktop, Cloud Agents: elevated API error rates](https://outages.cc/outages/posthog-1azxfuqd0nn.md): Resolved, started 2026-09-02 15:28 UTC, lasted 1 h 3 min. Traffic has resumed back to normal. - [PostHog: Application: elevated Scout API error rates](https://outages.cc/outages/posthog-268isgjohwr.md): Resolved, started 2026-09-02 07:37 UTC, lasted 1 h 14 min. We identified and reverted the PR that triggered elevated API errors in Scouts. - [PostHog: Session Replay Outage](https://outages.cc/outages/posthog-7m9yia28r6.md): Resolved, started 2026-09-01 17:59 UTC, lasted 13 min. A fix has been deployed and Session Replay playback has been restored. No loss of data occurred as a result of this incident. - [PostHog: Analytics: query timeouts/failures](https://outages.cc/outages/posthog-29paktkq4ot.md): Resolved, started 2026-08-31 23:57 UTC, lasted 27 h 36 min. Queries have returned to normal. We have identified the cause and are working on a fix to prevent the issue from occurring again. - [PostHog: Application: partial outage](https://outages.cc/outages/posthog-169etxy9xjd.md): Resolved, started 2026-08-25 09:22 UTC, lasted 1 h 47 min. We've been monitoring the situation and everything is working fine again. - [PostHog: Application: partial outage](https://outages.cc/outages/posthog-21lt5gx22dg.md): Resolved, started 2026-08-20 19:18 UTC, lasted 15 min. The incident has been resolved - [PostHog: MCP: elevated API error rates](https://outages.cc/outages/posthog-1q550c10ds0.md): Resolved, started 2026-08-20 16:05 UTC, lasted 50 min. The MCP server operated normally throughout, and the elevated error rate was due to rate-limit responses to a few projects with unusually high request volume. - [PostHog: Application: elevated API error rates in US region](https://outages.cc/outages/posthog-1fxgwu7ojhi.md): Resolved, started 2026-08-19 20:06 UTC, lasted 1 h 5 min. We’re investigating elevated API error rates impacting parts of the application. - [PostHog: Workflows: email sending failing in certain workflows](https://outages.cc/outages/posthog-cmsvs4ohom.md): Resolved, started 2026-08-18 20:35 UTC, lasted 1 h 18 min. The fix is deployed and email sending is back to normal in both regions. We will reach out to affected customers about a rerun of the emails that failed during the incident. - [PostHog: Application: partial outage](https://outages.cc/outages/posthog-k1bl5s2qpv.md): Resolved, started 2026-08-17 16:42 UTC, lasted 1 h 24 min. The incident has been resolved - [PostHog: Application: elevated cloud tasks failures](https://outages.cc/outages/posthog-wg2q7yr6v0.md): Resolved, started 2026-08-17 13:42 UTC, lasted 1 h 15 min. Cloud tasks are now recovering and creation is healthy. - [PostHog: Agent runs: elevated API error rates](https://outages.cc/outages/posthog-xo4fxnjwzg.md): Resolved, started 2026-08-11 07:35 UTC, lasted 20 min. The issue has been resolved and agent cloud tasks are healthy again - [PostHog: Cannot authenticate PostHog with ChatGPT](https://outages.cc/outages/posthog-1gd97c2ezmu.md): Resolved, started 2026-08-10 11:40 UTC, lasted 20 h 29 min. The issue was resolved for both ChatGPT and Codex. - [PostHog: Realtime destinations and workflows: delivery delays](https://outages.cc/outages/posthog-2fq21v2zlbm.md): Resolved, started 2026-08-04 17:09 UTC, lasted 30 min. Destination deliveries and workflow runs are caught up and processing normally again.