Try or ByeTry or Bye

Why Is PostHog So Slow?

Workaround available Web app Updated October 21, 2026

Quick answer

PostHog insights get slow when they scan 'All events' over long date ranges or use pdi.person.properties lookups. Filter on specific events, shorten the range and use person.properties; dashboards can also serve pre-computed results.

Most likely fix: Narrow the query.

Symptoms

Insights and dashboards take a long time to load or time out; live events view loads slowly.

Why it happens

  • Queries over 'All events' instead of a specific event
  • Long date ranges on large datasets
  • pdi.person.properties lookups in SQL/HogQL
  • Ingestion delays or incidents

How to fix it

Try these in order — the most common fix is first.

  1. 1. Narrow the query

    1. Pick a specific event (or an action) instead of All events
    2. Shorten the date range
    3. Add property filters to reduce rows scanned

  2. 2. Use faster person properties

    1. In SQL insights, use person.properties.<name> instead of pdi.person.properties.<name> unless you need the latest value

  3. 3. Use dashboard pre-compute

    1. Keep 'Allow precompute' on in dashboard settings for faster tiles
    2. Turn it off only when you need live results

  4. 4. Check for incidents

    1. Check status.posthog.com if everything is slow at once

This guide also covers

  • why is posthog so slow
  • posthog slow queries
  • posthog insights slow
  • posthog dashboard slow loading

Still not working?

If PostHog keeps failing, you're not alone. See every PostHog problem users report or the alternatives people switch to.

Other PostHog errors