PostHog status
PostHog service incidents. Match region and product to the analytics or ingestion operation that failed.
Live Domain Check
Is PostHog Down? Check posthog.com Status and Outages
Run a live reachability check for posthog.com. Compare the regional responses with the problem you see in PostHog.
Find PostHog help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Is PostHog working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding PostHog connection and service problems
PostHog dashboards, event ingestion, feature flags and session replay can fail independently.
The checker above requests posthog.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual PostHog action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
PostHog status information and official help
PostHog help and reporting
The PostHog customer-support product landing page is not a route to receive technical support.
Open posthog.com
Open the website in your browser and compare it with the result above.
Where to report problems with PostHog
Open PostHog help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Instance/region, project, product, event/request time and SDK/error details without user recordings or keys.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to PostHog.
What to check when PostHog is not working
These are troubleshooting comparisons, not claims that PostHog is currently experiencing a particular incident.
Start with the action that failed
Identify the cloud region or self-hosted instance and compare the failing product with one small read/test event.
Narrow down the affected service
Inspect ingestion or flag-request responses before changing production instrumentation or replaying batches.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if PostHog is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the posthog.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open PostHog status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If PostHog Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when PostHog seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open posthog.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader PostHog issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting PostHog support.
Frequently asked questions about PostHog problems
Is PostHog down, or is the problem limited to one feature?
Run the posthog.com check and compare its original timestamps and responses with your actual error. PostHog dashboards, event ingestion, feature flags and session replay can fail independently.
Where can I report a problem with PostHog?
Use the community buttons on this page to share whether the service works for you. For help from PostHog, use the official help/reporting resource linked above. The PostHog customer-support product landing page is not a route to receive technical support.
What should I check first when PostHog is not working?
Identify the cloud region or self-hosted instance and compare the failing product with one small read/test event. Inspect ingestion or flag-request responses before changing production instrumentation or replaying batches.
What information helps PostHog support investigate?
Instance/region, project, product, event/request time and SDK/error details without user recordings or keys.