- Detected by Pingoru
- Oct 13, 2026, 06:24 PM UTC
- Resolved
- Oct 13, 2026, 06:24 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Oct 13, 2026, 06:24 PM UTC
Status: Resolved This issue has been resolved. PostHog AI and other services are back to normal. Apologies for the interruption. Affected components Cloud AI Agents (Operational) Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Oct 09, 2026, 08:19 AM UTC
- Resolved
- Oct 09, 2026, 08:19 AM UTC
- Duration
- —
Affected: US Cloud 🇺🇸 (Data Warehouse Source Ingestion)EU Cloud 🇪🇺 (Data Warehouse Source Ingestion)
Timeline · 1 update
-
resolved Oct 09, 2026, 08:19 AM UTC
Status: Resolved 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. Affected components Data Warehouse Source Ingestion (Operational) Data Warehouse Source Ingestion (Operational)
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 04:58 PM UTC
- Resolved
- Oct 06, 2026, 04:58 PM UTC
- Duration
- —
Affected: US Cloud 🇺🇸 (Data Warehouse Source Ingestion)EU Cloud 🇪🇺 (Data Warehouse Source Ingestion)
Timeline · 1 update
-
resolved Oct 06, 2026, 04:58 PM UTC
Status: Resolved Warehouse sources backlog has been processed Affected components Data Warehouse Source Ingestion (Operational) Data Warehouse Source Ingestion (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2026, 08:43 AM UTC
- Resolved
- Sep 30, 2026, 08:43 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 30, 2026, 08:43 AM UTC
Status: Resolved PostHog has been loading fine after the fix and everything is back to normal. Affected components App (Web & Desktop) (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2026, 03:33 AM UTC
- Resolved
- Sep 30, 2026, 03:33 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 30, 2026, 03:33 AM UTC
Status: Resolved We’ve rolled back the deployment which caused the issue and query failures have returned to normal levels.
Read the full incident report →
- Detected by Pingoru
- Sep 28, 2026, 08:12 PM UTC
- Resolved
- Sep 28, 2026, 08:12 PM UTC
- Duration
- —
Affected: US Cloud 🇺🇸 (Logs)EU Cloud 🇪🇺 (Logs)
Timeline · 1 update
-
resolved Sep 28, 2026, 08:12 PM UTC
Status: Resolved 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. Affected components Logs (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 14, 2026, 10:54 AM UTC
- Resolved
- Sep 14, 2026, 10:54 AM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Sep 14, 2026, 10:54 AM UTC
Status: Resolved Issue has been fixed Affected components Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 10, 2026, 10:54 AM UTC
- Resolved
- Sep 10, 2026, 10:54 AM UTC
- Duration
- —
Affected: US Cloud 🇺🇸 (Data Warehouse Source Ingestion)EU Cloud 🇪🇺 (Data Warehouse Source Ingestion)
Timeline · 1 update
-
resolved Sep 10, 2026, 10:54 AM UTC
Status: Resolved 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. Affected components Data Warehouse Source Ingestion (Operational) Data Warehouse Source Ingestion (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 11:06 PM UTC
- Resolved
- Sep 09, 2026, 11:06 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 09, 2026, 11:06 PM UTC
Status: Resolved The fix has been fully deployed, and alerts on insights are back to normal. Affected components App (Web & Desktop) (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 09, 2026, 05:16 PM UTC
- Resolved
- Sep 09, 2026, 05:16 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Workflows)US Cloud 🇺🇸 (Workflows)
Timeline · 1 update
-
resolved Sep 09, 2026, 05:16 PM UTC
Status: Resolved We've caught up on all Workflow emails. Affected components Workflows (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 12:19 PM UTC
- Resolved
- Sep 08, 2026, 12:19 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 08, 2026, 12:19 PM UTC
Status: Resolved The issue was fixed and everything is back to normal. The impacted customers will be informed. Affected components Destination Delivery (realtime) (Operational) Destination Delivery (realtime) (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 04:32 PM UTC
- Resolved
- Sep 02, 2026, 04:32 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Sep 02, 2026, 04:32 PM UTC
Status: Resolved Traffic has resumed back to normal. Affected components Cloud AI Agents (Operational) Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 08:51 AM UTC
- Resolved
- Sep 02, 2026, 08:51 AM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Sep 02, 2026, 08:51 AM UTC
Status: Resolved We identified and reverted the PR that triggered elevated API errors in Scouts. Affected components Cloud AI Agents (Operational) Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Sep 01, 2026, 06:12 PM UTC
- Resolved
- Sep 01, 2026, 06:12 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 01, 2026, 06:12 PM UTC
Status: Resolved A fix has been deployed and Session Replay playback has been restored. No loss of data occurred as a result of this incident.
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2026, 11:09 AM UTC
- Resolved
- Aug 25, 2026, 11:09 AM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Aug 25, 2026, 11:09 AM UTC
Status: Resolved We've been monitoring the situation and everything is working fine again. Affected components App (Web & Desktop) (Operational) Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 04:55 PM UTC
- Resolved
- Aug 20, 2026, 04:55 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (MCP Server)US Cloud 🇺🇸 (MCP Server)
Timeline · 1 update
-
resolved Aug 20, 2026, 04:55 PM UTC
Status: Resolved 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. Affected components MCP Server (Operational) MCP Server (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2026, 09:11 PM UTC
- Resolved
- Aug 19, 2026, 09:11 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 19, 2026, 09:11 PM UTC
Status: Resolved We’re investigating elevated API error rates impacting parts of the application.
Read the full incident report →
- Detected by Pingoru
- Aug 18, 2026, 09:53 PM UTC
- Resolved
- Aug 18, 2026, 09:53 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Workflows)US Cloud 🇺🇸 (Workflows)
Timeline · 1 update
-
resolved Aug 18, 2026, 09:53 PM UTC
Status: Resolved 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. Affected components Workflows (Operational) Workflows (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 17, 2026, 02:57 PM UTC
- Resolved
- Aug 17, 2026, 02:57 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Aug 17, 2026, 02:57 PM UTC
Status: Resolved Cloud tasks are now recovering and creation is healthy. Affected components Cloud AI Agents (Operational) Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2026, 08:09 AM UTC
- Resolved
- Aug 11, 2026, 08:09 AM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (MCP Server)US Cloud 🇺🇸 (MCP Server)
Timeline · 1 update
-
resolved Aug 11, 2026, 08:09 AM UTC
Status: Resolved The issue was resolved for both ChatGPT and Codex. Affected components MCP Server (Operational) MCP Server (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 11, 2026, 07:55 AM UTC
- Resolved
- Aug 11, 2026, 07:55 AM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Cloud AI Agents)US Cloud 🇺🇸 (Cloud AI Agents)
Timeline · 1 update
-
resolved Aug 11, 2026, 07:55 AM UTC
Status: Resolved The issue has been resolved and agent cloud tasks are healthy again Affected components Cloud AI Agents (Operational) Cloud AI Agents (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 04, 2026, 05:39 PM UTC
- Resolved
- Aug 04, 2026, 05:39 PM UTC
- Duration
- —
Affected: EU Cloud 🇪🇺 (Workflows)US Cloud 🇺🇸 (Workflows)
Timeline · 1 update
-
resolved Aug 04, 2026, 05:39 PM UTC
Status: Resolved Destination deliveries and workflow runs are caught up and processing normally again. Affected components Destination Delivery (realtime) (Operational) Workflows (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 24, 2026, 10:00 PM UTC
- Resolved
- Jul 24, 2026, 10:00 PM UTC
- Duration
- —
Affected: US Cloud 🇺🇸 (Event Ingestion Lag)EU Cloud 🇪🇺 (Event Ingestion Lag)
Timeline · 1 update
-
resolved Jul 24, 2026, 10:00 PM UTC
Status: Resolved We're now caught up on processing delays and events are being processed normally. Affected components Event Ingestion Lag (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 23, 2026, 01:19 PM UTC
- Resolved
- Jul 23, 2026, 01:19 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 23, 2026, 01:19 PM UTC
Status: Resolved The topics fully drained and everything is back to baseline and operational again. No data was lost. Affected components Destination Delivery (realtime) (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2026, 10:10 AM UTC
- Resolved
- Jul 19, 2026, 10:10 AM UTC
- Duration
- —
Affected: US Cloud 🇺🇸 (Data Warehouse Source Ingestion)EU Cloud 🇪🇺 (Data Warehouse Source Ingestion)
Timeline · 1 update
-
resolved Jul 19, 2026, 10:10 AM UTC
Status: Resolved Meta's Marketing API has recovered and Meta Ads data imports are succeeding normally again across US and EU. Failure rates are back to baseline. Any sources that failed during the incident will fully refresh on their next scheduled sync. Affected components Data Warehouse Source Ingestion (Operational) Data Warehouse Source Ingestion (Operational)
Read the full incident report →