Is Pipl Down?

No — Pipl is up

Pipl's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 7 of 7 regions · 1309 ms

Right now

The verdict is the worse of these two. How we decide

Pipl's status page

status.pipl.com · read 3 minutes ago · checked every 3 minutes

Operational

Pipl's components, as its status page reports them
Component	Status
Pipl Trust API	Operational
Pipl Trust Insights	Operational
Pipl Search API	Operational
Pipl Search Insights	Operational
Pipl Account Management	Operational

Open their status page

FlareWarden checks

pipl.com from 7 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 7 of 7
Response: 1309 ms
Checked: 1 hour ago

By region

Ashburn reachable, 611 ms
Frankfurt reachable, 956 ms
London reachable, 811 ms
Los Angeles reachable, 432 ms
Newark reachable, 301 ms
São Paulo reachable, 2239 ms
Tokyo reachable, 3813 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	139 ms	1 ms	5 ms	274 ms
Frankfurt	311 ms	88 ms	91 ms	678 ms
London	273 ms	71 ms	75 ms	592 ms
Los Angeles	71 ms	40 ms	45 ms	311 ms
Newark	85 ms	9 ms	13 ms	270 ms
São Paulo	1001 ms	137 ms	140 ms	1827 ms
Tokyo	75 ms	145 ms	149 ms	636 ms

We check that pipl.com loads, not every feature behind it. Test it yourself

History

Incidents Pipl reported

Since Oct 22, 15 days · from status.pipl.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Pipl website availability

Measured by FlareWarden · pipl.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 861ms

Last 30 days

55-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of pipl.com from multiple regions every 6 hours. Pipl's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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

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 7 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Pipl itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Pipl goes down

We check Pipl every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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