Vendor reports: degradedResolved · vendor status “resolved”Vendor incident feed · inferred
Log ingestion: processing delays
Reported by PostHog · Data & Analytics · source last read just now
- Vendor posted
- Sep 28, 2026, 20:12 UTC
- When the vendor's feed dated it
- Resolved
- Sep 28, 2026, 20:12 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- This source does not publish reliable durations
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-09-28 20:12 UTC · summary s1, evidence 9cc12d7ba380452a
Evidence (7)
- E1PostHog reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "Log ingestion: processing delays". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor posted it: 2026-09-28 20:12 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2026-09-28 20:12 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
PostHog is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Sep 28, 2026, 20:12 UTCVendor posted this incidentVendor time
- Sep 28, 2026, 20:12 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.