Skip to main content
PostHog logo

Is PostHog Down?

No — PostHog is up

Reachable from all 8 checked regions

Average response time: 185ms

Last checked · checks run every 6 hours

Official status page: https://www.posthogstatus.com

PostHog uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
168ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 77 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

77-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 23 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 35 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
112ms
DNS 7ms TCP 1ms TLS 19ms TTFB 55ms
lhr
95ms
DNS 41ms TCP 2ms TLS 8ms TTFB 70ms
nrt
729ms
DNS 25ms TCP 2ms TLS 8ms TTFB 702ms
ord
151ms
DNS 47ms TCP 2ms TLS 26ms TTFB 106ms
sin
76ms
DNS 9ms TCP 2ms TLS 8ms TTFB 43ms
sjc
66ms
DNS 7ms TCP 1ms TLS 7ms TTFB 36ms
syd
82ms
DNS 39ms TCP 0ms TLS 7ms TTFB 68ms
yyz
174ms
DNS 6ms TCP 11ms TLS 31ms TTFB 96ms

What PostHog does

PostHog is a product analytics platform combining event tracking, session replay, feature flags and experiments in one tool. Product and engineering teams use it to see how features are actually used, and because its snippet runs inside the customer's own application, the integration point sits in the browser rather than only on the server.

What an outage looks like

The PostHog web app fails to load or dashboards render without data, so charts appear flat rather than broken. Newly captured events stop appearing in live views, and session replays either do not record or cannot be played back. Because the tracking snippet runs client-side, the application being measured usually keeps working normally while its analytics quietly go blank.

What to do about it

Check posthogstatus.com, where PostHog posts incidents; status.posthog.com redirects there. Confirm the gap is in PostHog rather than in your own instrumentation before changing any tracking code, since a deploy made mid-incident is hard to untangle afterwards. Note the affected window so that later analysis does not read missing data as a genuine drop in user activity.

Is it down for everyone, or just you?

If this page says PostHog is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Sentry
Sentry
Datadog
Datadog
Supabase
Supabase
Vercel
Vercel

PostHog outage FAQ

Is PostHog down or has my tracking broken?
Check posthogstatus.com first, because the symptoms are identical from your side. A misconfigured snippet, a blocked script and a PostHog incident all produce the same empty dashboard. If the status page reports no incident, look at your browser console for errors from the PostHog script and confirm the events are being sent at all before assuming the platform is at fault.
Does a PostHog outage break my website or app?
It should not. PostHog runs as an analytics layer alongside your application rather than in the path of a user request, so pages continue to load and features keep working while data collection fails. The exception is anything you have made dependent on PostHog at runtime, such as gating a feature on a flag, where a failure to reach the service does affect what users see.
Will I lose analytics data recorded during the outage?
Possibly, and that is the real cost of these incidents. Events that cannot reach PostHog while the browser session is open may never be delivered, since the visitor moves on and the page is gone. Record the start and end of the incident so that any later comparison accounts for the gap rather than reading it as a genuine fall in usage.
Why do my dashboards look flat rather than empty?
Because a missing event and an event that did not happen look the same on a chart. Ingestion problems show up as an unusually quiet period rather than an error, which is exactly what a real drop in traffic looks like. Cross-check against a system that does not depend on PostHog, such as your server logs or revenue numbers, before acting on a sudden decline.
Is session replay affected separately from event capture?
They can fail independently, so check what is actually degraded before investigating. Replay carries far more data than event capture and tends to be the first thing to suffer, which means replays may be missing or unplayable for a window while ordinary event data continues to arrive. Recordings that failed to upload at the time are generally not recoverable afterwards.

How we measure this

  • We request PostHog's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where PostHog publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when PostHog goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required