PostHog statusManual checkVerified May 24, 2026Source: posthogstatus.com
Is PostHog down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from posthogstatus.com. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About PostHog status
PostHog is the all-in-one product analytics, feature flags, session replay, and A/B testing platform (open source and hosted). Incidents typically scope to a single component: event ingestion, feature flag evaluation, session recording ingestion, or insights queries.
Components and surfaces that can break
- Surface 01
Event ingestion endpoints (us.i.posthog.com and eu.i.posthog.com).
- Surface 02
Feature flag evaluation API (latency-critical, sits on the request path).
- Surface 03
Session recording ingestion plus insights and HogQL queries.
What to do if PostHog is actually down
Short ingestion outages don't immediately break flag-gated UI
PostHog SDKs cache the most recent feature flag decisions client-side. If event ingestion is degraded for a few minutes, users keep seeing the variant they were assigned and your flag-gated UI keeps rendering. Analytics events may be queued or dropped, but the UI itself stays intact.
Confirm your project's region (US vs EU)
PostHog Cloud US and PostHog Cloud EU are separate deployments with separate status. If the status page lists a US incident and your project lives at eu.i.posthog.com, the issue is on your side, not PostHog's. Verify the region in your SDK config before assuming an outage is yours.
Set sensible feature-flag defaults so eval can't disable critical features
Bootstrap your SDK with default values for every flag that gates a critical path (checkout, login, kill-switches). When the evaluation API is degraded, the SDK falls back to those defaults instead of treating an unknown flag as off, which is what tends to surprise teams during an incident.
Keep firing through the incident
Schedule your own PostHog health check with Crontap
Daily feature-flag eval snapshot, weekly session-replay highlights, monthly product analytics digest. Crontap fires the endpoint that queries PostHog's API on the cadence you set, retries on 5xx, and emails you if the digest job itself fails.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
PostHog status: FAQ
- Where can I see the official PostHog status?
- PostHog publishes status at status.posthog.com, which currently redirects to posthogstatus.com. It lists component status for event ingestion, the feature flag API, session recording, and the app, with separate breakdowns for US Cloud and EU Cloud.
- Can I verify PostHog is receiving my events on a schedule?
- Yes. Set up a Crontap job that hits a small /api/posthog-heartbeat endpoint on your app every few minutes. The endpoint captures a known test event (e.g. 'crontap_heartbeat'), waits a beat, then runs a HogQL query for that event in the last 5 minutes. If the row isn't there, return 5xx and Crontap will alert you, independent of PostHog's own status page.
- Will my feature flags break during a PostHog incident?
- Usually not. SDKs cache the last-known flag decisions per user, and if you bootstrap defaults at init time the SDK falls back to those when the evaluation API is unreachable. The biggest real risk is brand-new sessions for users the SDK has never evaluated; configure bootstrap defaults and the impact stays small.