PostHog Status: How to Check If PostHog Is Down Right Now (2026)
Updated June 2026 · 6 min read · By API Status Check
Quick Answer: Check PostHog Status Now
PostHog is an open-source product analytics platform used by engineering and product teams for event tracking, session recording, feature flags, A/B tests, and data pipelines. Like n8n, PostHog comes in two flavors: PostHog Cloud (fully managed) and self-hosted (run on your own infrastructure). Troubleshooting paths are completely different between the two.
PostHog Cloud vs Self-Hosted: Which Are You Running?
- • Your host is
app.posthog.comorus.posthog.com/eu.posthog.com - • Managed by PostHog — no infrastructure to maintain
- • Check status.posthog.com for outages
- • US and EU regions on separate infrastructure
- • Your own domain or IP, configured in POSTHOG_HOST
- • You own the infrastructure — and the outages
- • No central status page — check your own servers
- • Requires ClickHouse, Kafka, Redis, and Postgres
Understanding PostHog Cloud's Status Page (status.posthog.com)
PostHog Cloud operates status.posthog.com to track their infrastructure components. PostHog's architecture separates event capture from processing — events may be ingested successfully while dashboard analytics are delayed.
Event Ingestion
The pipeline that accepts events from your PostHog SDK or API. This is the most critical component — if degraded, events from your users are dropped or queued. PostHog uses Kafka for ingestion buffering, which provides some resilience against brief spikes.
Dashboard & Queries
The PostHog web app and analytics query engine. A slow dashboard usually means ClickHouse query performance is degraded — your data is safe but reports take longer to load. Queries involving large date ranges or many users are most affected.
Feature Flags
PostHog's feature flag evaluation endpoint. SDKs cache flag decisions locally, so brief outages may not cause immediate user-facing failures. Prolonged outages can cause stale flag decisions if the cache TTL expires.
Session Recordings
Session recording capture and playback. Separate from event ingestion — recordings can fail independently. If session playback is down, new recordings may not be captured or existing ones may not be viewable.
Data Pipelines
PostHog's data export and integration system — exports to BigQuery, S3, Snowflake, and webhook destinations. Pipeline failures do not affect event collection or the PostHog dashboard directly.
API
The PostHog REST API used for server-side event capture, flag evaluation, and data export. API degradation affects server-side integrations and backend analytics pipelines that don't use the client-side SDK.
Diagnosing Self-Hosted PostHog Issues
Self-hosted PostHog runs multiple services — if any one of them is down, your analytics can silently stop working.
Self-Hosted PostHog Diagnostic Commands
# 1. Check all PostHog containers (Docker Compose)
docker ps --filter "name=posthog"
# All containers should show "Up" status
# 2. Test PostHog health endpoint
curl http://localhost:8000/_health
# Should return: {ok: true}
# 3. Check ClickHouse is healthy
curl http://localhost:8123/ping
# Should return: Ok.
# 4. Check PostHog web logs
docker logs posthog-web --tail 50
# 5. Check disk space (ClickHouse is storage-hungry)
df -h
Common Self-Hosted PostHog Failure Causes
- 🔴 ClickHouse disk full: PostHog stores all events in ClickHouse. When disk fills, ingestion halts. ClickHouse needs significant headroom — plan for 3-4x your current data size.
- 🔴 Kafka queue overflow: If the PostHog worker falls behind processing events, the Kafka queue fills. Events may appear to ingest but never appear in the dashboard.
- 🔴 Memory exhaustion: ClickHouse queries are memory-intensive. OOM kills on the ClickHouse container cause queries to fail. Check container memory limits and consider increasing them.
- 🔴 Wrong POSTHOG_HOST in SDK: If your SDK points to the wrong host URL, events silently fail. Verify the host in your SDK config matches your PostHog instance URL exactly (including https://).
- 🔴 Plugin server crash: PostHog plugins (data pipelines, transformations) run in a separate plugin-server process. If it crashes, exports and webhooks stop but event ingestion continues.
Monitor your PostHog instance from outside your network
Whether you're on PostHog Cloud or self-hosting, Better Stack can ping your PostHog health endpoint and alert you the moment event ingestion fails. Free plan available.
Try Better Stack Free →What PostHog Status Colors Mean (Cloud)
Common PostHog Issues and What They Mean
"Events not appearing in PostHog dashboard"PostHog Cloud has a natural 1-5 minute processing delay. Wait a few minutes before diagnosing. If events are still missing after 15 minutes, check the Event Ingestion component on status.posthog.com. For self-hosted: verify the plugin-server is running and check its logs for ClickHouse write errors."Feature flags returning wrong values"Check your flag rollout percentage and targeting conditions. PostHog SDKs evaluate flags based on the distinct_id hash — if you recently changed the rollout percentage, users already assigned to a flag bucket may shift. Also verify you're passing the correct distinct_id and that any property-based targeting rules match your user's current properties."PostHog session recordings not capturing"Verify the PostHog JS snippet is loading on the page (check browser console). Check that session recording is enabled for the project in PostHog Settings → Recording. Also verify that the page is not excluded by URL suppression rules and that your plan includes session recording."autocapture stopped working after a site update"PostHog's autocapture relies on DOM event listeners. Some SPA frameworks (especially those with heavy virtualization) can interfere with autocapture after route changes. Check whether posthog.capture() calls work manually — if they do, the SDK is fine but autocapture needs explicit Virtual Pageview calls after route changes."PostHog CORS errors in browser console"CORS errors occur when your SDK's configured host doesn't match the actual PostHog instance URL. For Cloud: ensure the host is set to https://app.posthog.com (US) or https://eu.posthog.com (EU). For self-hosted: verify your PostHog instance has CORS configured to allow your application's origin."Funnel or retention query times out"ClickHouse-backed queries on large datasets can time out. For Cloud, try narrowing the date range or reducing the number of steps. For self-hosted, increase ClickHouse query timeout limits and consider adding more memory to the ClickHouse container.Frequently Asked Questions
Where is the official PostHog status page?
PostHog Cloud's official status page is status.posthog.com. It covers both US and EU cloud regions and breaks down status by component: Event Ingestion, Dashboard, Feature Flags, Recordings, and Data Pipelines. Self-hosted PostHog has no central status page — you monitor your own infrastructure.
Are PostHog Cloud US and EU regions on the same infrastructure?
No. PostHog Cloud US (app.posthog.com) and EU (eu.posthog.com) run on separate infrastructure in different geographic regions to meet data residency requirements. An outage affecting US Cloud may not affect EU Cloud, and vice versa. Status.posthog.com tracks both regions.
If PostHog Cloud was down, were my events lost?
PostHog uses Kafka as a buffer between event capture and ClickHouse storage. During short ingestion degradations, events may be queued in Kafka and processed once the issue clears, rather than being lost. During prolonged outages, some events may be dropped. Check PostHog's incident post-mortems at status.posthog.com for details on specific incidents.
How is PostHog different from Mixpanel or Amplitude for outage purposes?
PostHog's key differentiator is the self-hosted option — you can run the entire stack on your own infrastructure, giving you full control and no dependency on PostHog's servers. PostHog Cloud is similar to Mixpanel and Amplitude in terms of operational dependency. Self-hosted PostHog trades operational responsibility for complete data ownership.
How do I get alerts when PostHog goes down?
For PostHog Cloud, subscribe to updates at status.posthog.com. For self-hosted, set up external uptime monitoring on your PostHog health endpoint (/_health) from outside your network — this catches outages that internal monitoring can miss.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time PostHog goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for PostHog + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial