CheckUpstream measured PostHog at 99.965% availability across 2817 independent checks (global · api). 12 incidents were recorded in the past 12 months; the most recent resolved earlier today after 43 minutes. Status signals are polled from PostHog's official status feed, alongside independent probes and community reports.
180 days measured availability how this is computed
99.965%
global · api · n=2817 · p95 425ms (30d)
Share of our own checks against PostHog endpoints that returned PostHog's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 12 incidents · 171 of 180 days with none posted · 11h 19m of declared impact
Fewer incidents in the last 30 days than 8% of 232 tracked services.
Share of each window with no impact declared by PostHog
7d
99.371%
30d
98.427%
90d
99.476%
180d
99.738%
1y
99.871%
Downtime like this can be refundable
If you're a paying PostHog customer, outages in these windows may count against PostHog's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your PostHog entitlement →Does PostHog actually matter to you?
A PostHog outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 12 incidents PostHog published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long PostHog takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 31, 23:57 UTC · resolved in 43m · Resolved
Aug 25, 09:22 UTC · resolved in 47m · Resolved
Aug 20, 19:18 UTC · resolved in 27m · Resolved
Aug 20, 16:05 UTC · resolved in 54m · Resolved
2signals across 1 source
Synthetic probes 2
All of these are CheckUpstream's own probes. Nobody else has reported PostHog in this window, so nothing here is corroboration.
Live PostHog status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/posthog)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
PostHog is currently Operational. CheckUpstream tracks PostHog in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
PostHog's last resolved incident started earlier today and lasted 43 minutes (a partial outage).
Looking for the live "is PostHog down" view? See the PostHog Live status page.
Aug 19, 20:10 UTC · resolved in 20m · Resolved
Aug 18, 20:35 UTC · resolved in 1h 19m · Resolved
Aug 17, 16:42 UTC · resolved in 48m · Resolved
Aug 17, 13:42 UTC · resolved in 1h 18m · Resolved
Aug 11, 07:35 UTC · resolved in 54m · Resolved
Aug 10, 11:40 UTC · resolved in 20h 29m · Resolved
Aug 4, 17:23 UTC · resolved in 56m · Resolved
Aug 2, 17:58 UTC · resolved in 41m · Resolved
PostHog's 30-day measured availability is 99.965%, from CheckUpstream's own probes against PostHog endpoints. It is the share of checks that returned the expected response, not a figure taken from PostHog's status page.
Sign up to CheckUpstream and add PostHog to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll PostHog's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.