Skip to main content
Pipl logo

Is Pipl Down?

No — Pipl is up

Reachable from all 8 checked regions

Average response time: 868ms

Last checked · checks run every 6 hours

Official status page: https://status.pipl.com

Pipl uptime

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

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

30-day history

30-day clean streak
Sep 12: 100.00% uptime, 8 checks
Sep 13: 100.00% uptime, 24 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 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, 40 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, 29 checks
Oct 1: 100.00% uptime, 28 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, 31 checks
Oct 11: 100.00% uptime, 32 checks
Sep 12 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.

gru
1421ms
DNS 534ms TCP 106ms TLS 216ms TTFB 1099ms
iad
215ms
DNS 87ms TCP 1ms TLS 3ms TTFB 146ms
jnb
1719ms
DNS 366ms TCP 225ms TLS 228ms TTFB 1134ms
lax
602ms
DNS 263ms TCP 27ms TLS 31ms TTFB 498ms
lhr
468ms
DNS 37ms TCP 71ms TLS 75ms TTFB 324ms
nrt
714ms
DNS 108ms TCP 100ms TLS 103ms TTFB 499ms
ord
227ms
DNS 48ms TCP 13ms TLS 30ms TTFB 181ms
sin
1582ms
DNS 167ms TCP 234ms TLS 241ms TTFB 957ms

What Pipl does

Pipl resolves identity data, returning information linked to an email address, phone number or name. Its Trust products score the risk attached to an identity and are called during signup or checkout to flag fraud; its Search products are used by investigators, fraud teams and due-diligence workflows. Both are reached through APIs, so Pipl usually sits inside another company's product rather than in front of a user.

What an outage looks like

API calls to Pipl time out or return errors, and because Pipl is normally called from another service, the failure surfaces there: signups hang at the verification step, checkout risk checks stall, or a fraud review queue stops receiving enrichment. Whether users are blocked or waved through depends on how the calling application handles a failed lookup. The Pipl dashboard itself may be unreachable.

What to do about it

Read status.pipl.com, which reports Pipl Trust API, Trust Insights, Search API, Search Insights and Account Management as separate components, and check the scheduled maintenance list before treating a failure as an incident, because Pipl posts recurring maintenance windows. Then check your own side: decide deliberately whether a failed identity lookup should block a signup or let it through, because that choice is yours and not Pipl's.

Is it down for everyone, or just you?

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

ZoomInfo
ZoomInfo
Apollo.io
Apollo.io
Okta
Okta
Salesforce
Salesforce

Pipl outage FAQ

Pipl is down. Should my signups fail or go through?
That is your application's decision, not Pipl's, and it is worth making before an incident rather than during one. A risk check that fails closed blocks legitimate customers for the length of the outage; one that fails open admits whatever the check would have caught. A common middle path is to admit the signup and queue it for review once Pipl returns, so neither the customer nor the check is simply discarded.
Is the Trust API down if Search is down?
Not necessarily. Pipl lists Trust API, Trust Insights, Search API, Search Insights and Account Management as five separate components, and Trust and Search are different product lines. An incident can take one while the other answers normally. Check the specific row for the endpoint your integration calls, rather than reading the headline state at the top of the page.
How do I tell a Pipl outage from a problem in my own integration?
Check the status page components first, then your own request. Expired credentials, a rate limit and an exhausted quota all produce failed calls that look like an outage from inside your application, and Account Management is a separate component from the APIs, so billing or key management can be unavailable while the APIs answer. The regional measurements on this page show whether Pipl responded to our probes.
Is this maintenance or an incident?
Check the scheduled maintenance list on status.pipl.com before assuming. Pipl posts maintenance windows regularly, with three scheduled across September 2026 covering cloud infrastructure, Pipl services and security patches, and a failure inside a posted window is expected work rather than an unplanned outage. It matters because the two have different timelines: maintenance has a published end, an incident does not.
Will my queries run once Pipl comes back?
Only if your own code retries them. Pipl is a request-and-response API rather than a queue, so a call that failed during an outage is not held anywhere on Pipl's side waiting to be replayed. Anything that must not be lost needs a retry with backoff in your integration, or a record of which lookups were skipped so they can be run again afterwards.

How we measure this

  • We request Pipl'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 Pipl 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 Pipl 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