Is Pendo Down?

No — Pendo is up

Reachable from all 8 checked regions

Average response time: 299ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://status.pendo.io

Pendo uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

329ms

Avg response, 30 days

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

30-day history

62-day clean streak

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

176ms

DNS 20ms TCP 6ms TLS 10ms TTFB 175ms

arn

275ms

DNS 109ms TCP 6ms TLS 23ms TTFB 275ms

cdg

212ms

DNS 59ms TCP 2ms TLS 12ms TTFB 211ms

dfw

245ms

DNS 209ms TCP 1ms TLS 6ms TTFB 245ms

ewr

383ms

DNS 310ms TCP 7ms TLS 12ms TTFB 382ms

fra

320ms

DNS 140ms TCP 1ms TLS 14ms TTFB 320ms

syd

518ms

DNS 158ms TCP 1ms TLS 158ms TTFB 518ms

yyz

266ms

DNS 206ms TCP 1ms TLS 27ms TTFB 266ms

What Pendo does

Pendo combines product analytics with in-app guides, surveys and feedback collection. A snippet inside the host application sends usage data to Pendo and pulls back guides, walkthroughs and NPS prompts, so it sits inside the product experience rather than beside it. Pendo runs separate US, EU and Australian environments, and reports status for each one independently.

What an outage looks like

In-app guides, walkthroughs and NPS prompts stop appearing for end users, which is the visible symptom inside your own product. The Pendo dashboard will not load, or charts return no data. Analytics data collection pauses, leaving a gap in usage figures for the incident window. Webhooks stop firing and Session Replay recordings do not appear afterwards.

What to do about it

Check status.pendo.io and read the section for your environment: Pendo reports US at app.pendo.io, EU at app.eu.pendo.io and AU at app.au.pendo.io separately. Guide Deliverability, Analytics Data Collection and Analytics Data Processing are distinct components, so guides can fail while collection is fine, and a processing incident shows as figures arriving late rather than as a collection failure.

Is it down for everyone, or just you?

If this page says Pendo 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

Pendo outage FAQ

Will my users see errors if Pendo is down?

Generally not errors, but missing guides. Pendo loads through a snippet in your application, so when it is unavailable the guides, walkthroughs and surveys it would inject simply do not appear, and your own application continues to work. That is worth knowing in advance, because it means the failure is silent from your users' point of view rather than loud.

Do I lose analytics data during a Pendo outage?

Pendo lists Analytics Data Collection and Analytics Data Processing as separate components, so the answer depends on which one failed. A processing incident shows as figures arriving late rather than never. A collection incident is the one that leaves a genuine gap in the window. Check which row was affected before reconciling numbers or explaining a dip to anyone.

Which Pendo environment am I on?

Look at the URL you sign in to: app.pendo.io is the US environment, app.eu.pendo.io is the EU one and app.au.pendo.io is Australian. Pendo publishes status for all three separately and they do not fail together. Reading the wrong section is the most common way to conclude nothing is wrong while your own environment is affected.

Does a Pendo outage affect Session Replay?

It can, and Pendo lists Session Replay as its own component per environment. A replay incident means sessions during that window may not be captured, or may not be viewable afterwards. Because replay is retrospective, the loss only becomes visible later, so note the incident window if you rely on replays for support or debugging.

Should I remove the Pendo snippet during an outage?

No. Removing and re-adding a snippet is a code change made under time pressure, and Pendo failing to load does not stop your application rendering. If you are seeing genuine slowness attributable to it, that is an argument for loading the snippet asynchronously as a permanent change, not a change to make in the middle of an incident.

How we measure this

We request Pendo'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 Pendo 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 Pendo 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