Skip to content

MaintenanceThe former company search endpoint goes into maintenance on November 9Migration guide

Reverse ContactDocs
Reverse ContactDocs
What's changing Data Coverage & Performance
Get API keyLog in
Supportreversecontact.com

Performance

API performance and availability

Response times, webhook delivery and availability of the Reverse Contact API, measured on production traffic.

Fetch Persons P90
967 ms
Search People P90
1.2 s
Enrich Persons P90
7.0 s
Webhook delivery P90
5.6 s

Response times

Time taken by each endpoint to respond, measured on customer traffic and excluding rate-limited requests.

By endpoint

Oct 28 to Nov 1, 2026

EndpointP50P90P99
Enrich
/v2/enrich/persons2.0 s7.0 s9.9 s
/v2/enrich/companies67 ms232 ms712 ms
Fetch
/v2/fetch/persons305 ms967 ms3.4 s
/v2/fetch/persons/check56 ms206 ms858 ms
/v2/fetch/companies168 ms408 ms1.0 s
/v2/fetch/companies/check134 ms248 ms819 ms
Search
/v2/search/people330 ms1.2 s3.9 s
/v2/search/people/count304 ms481 ms995 ms
/v2/search/people/lookalike4.2 s8.7 s9.9 s
/v2/search/people/prompt1.8 s4.3 s4.9 s
/v2/search/people/available-fields25 ms45 ms50 ms
/v2/search/organizations142 ms433 ms987 ms
/v2/search/organizations/count145 ms436 ms825 ms
/v2/search/organizations/prompt1.8 s4.3 s4.9 s
/v2/search/organizations/available-fields25 ms45 ms50 ms
Account
/v2/usage26 ms46 ms82 ms
Asynchronous
These endpoints return 202 immediately and deliver the result by webhook. The times below stop at the 202 response. See webhook delivery times
/v2/fetch/persons/live152 ms484 ms1.8 s
/v2/fetch/companies/live188 ms565 ms1.8 s
/v2/contact/email130 ms231 ms436 ms
/v2/contact/phone174 ms322 ms535 ms

Webhook delivery

Asynchronous endpoints return 202 immediately and deliver the result by webhook. Delivery time runs from the request to the webhook.

P50
3.1 s
P90
5.6 s
P99
18.5 s
Delivered within 10 min
99.998%

Oct 30 to Nov 2, 2026. All webhooks.

Delivery time at P50 (rolling 24-hour median)

Sep 2 to Nov 2, 2026. All webhooks. Each point is the median of the preceding 24 hours.

0 s5 s10 s15 s20 sSep 15Oct 1Oct 15Nov 1

On Oct 27, 2026, we improved how our services process asynchronous jobs: each job now starts as soon as it is queued. The median delivery time fell from about 13 s to under 4 s. The curve drops later that day because each point is the median of the preceding 24 hours.

Daily values
Day (UTC)P50
Nov 12.7 s
Oct 313.1 s
Oct 303.5 s
Oct 293.7 s
Oct 283.7 s
Oct 273.4 s
Oct 2613.1 s
Oct 2512.9 s
Oct 2413.0 s
Oct 2313.1 s
Oct 2213.1 s
Oct 2113.3 s
Oct 2013.9 s
Oct 1913.7 s
Oct 1813.3 s
Oct 1713.1 s
Oct 1614.3 s
Oct 1513.4 s
Oct 1413.5 s
Oct 1313.7 s
Oct 1213.8 s
Oct 1113.5 s
Oct 1013.3 s
Oct 913.5 s
Oct 813.6 s
Oct 713.6 s
Oct 613.4 s
Oct 513.6 s
Oct 413.4 s
Oct 313.3 s
Oct 213.4 s
Oct 113.8 s
Sep 3013.4 s
Sep 2913.5 s
Sep 2813.4 s
Sep 2713.4 s
Sep 2613.4 s
Sep 2513.5 s
Sep 2414.2 s
Sep 2314.2 s
Sep 2214.4 s
Sep 2114.2 s
Sep 2013.9 s
Sep 1913.8 s
Sep 1813.9 s
Sep 1714.1 s
Sep 1614.0 s
Sep 1513.8 s
Sep 1413.7 s
Sep 1313.5 s
Sep 1213.6 s
Sep 1113.6 s
Sep 1014.1 s
Sep 914.1 s
Sep 813.8 s
Sep 713.9 s
Sep 616.4 s
Sep 513.9 s
Sep 414.6 s
Sep 314.4 s
Sep 212.6 s

Delivery time by endpoint

Oct 30 to Nov 2, 2026. All webhooks, with or without a result. Email lookups with no match take longer because the waterfall queries several sources first.

EndpointP50P90P99
/v2/fetch/persons/live3.1 s4.4 s6.7 s
/v2/fetch/companies/live1.9 s2.7 s5.9 s
/v2/contact/email7.4 s32.1 s47.3 s
Email found5.8 s16.7 s38.8 s
No email found (waterfall)23.3 s45.4 s50.6 s
/v2/contact/phone4.5 s7.6 s13.3 s

Availability

Share of customer requests served by the API, over the last four weeks and by week.

All endpoints
99.95%
Fetch
99.97%
Enrich
99.87%
Search
99.93%
Contact
99.97%

Oct 5 to Nov 1, 2026. Share of customer requests served by the API.

Weekly availability

Sep 2 to Nov 1, 2026. All endpoints. Dates mark the start of each week.

  1. Sep 299.94%
  2. Sep 799.92%
  3. Sep 1499.85%
  4. Sep 2199.92%
  5. Sep 2897.76%
  6. Oct 599.94%
  7. Oct 1299.94%
  8. Oct 1999.97%
  9. Oct 2699.94%
View the status page

Methodology

How each metric is defined and which traffic it covers.

What is measured

From the request to the response.

Synchronous endpoint

Response timeRequestData returned

Asynchronous endpoint

Response timeProcessingRequest202 acceptedWebhook deliveredWebhook delivery

Percentiles

100 requests to an endpoint, sorted from fastest to slowest.

P50
Median: 50% of requests are faster.
P90
90% of requests are faster.
P99
99% of requests are faster.

Response-time percentiles are interpolated from a latency histogram and are less precise above 5 s.

Delivery time curve

Each point is the median of the preceding 24 hours.

Hourly values24-hour medianIllustrative data.

A rolling median smooths out isolated slow hours, so they do not appear on the curve. The figures above the chart include all webhooks.

Traffic included

Applies to response times and availability. Webhook delivery covers all webhooks.

  • Included: Customer requests
  • Included: All documented endpoints
  • Excluded: 429 responses
  • Excluded: Internal workspaces
  • Excluded: Personal accounts
  • Excluded: Retired endpoints

Availability

Measured on customer traffic.

  1. Request
  2. API
  3. Served

A request counts as served unless the API fails to respond. Invalid requests and empty results count as served, since the API responded. Requests that never reach the API cannot be measured this way, so the status page relies on independent monitors.

FAQ

How fast is the Reverse Contact API?

From Oct 28 to Nov 1, 2026, /v2/fetch/persons responded in 305 ms at P50 and 967 ms at P90, /v2/search/people in 330 ms and 1.2 s, and /v2/enrich/persons in 2.0 s and 7.0 s.

What do P50, P90 and P99 mean?

P50 is the median response time: 50% of requests to an endpoint complete within it. P90 and P99 are the times within which 90% and 99% of requests complete.

How long does a Reverse Contact webhook take to arrive?

From Oct 30 to Nov 2, 2026, 50% of webhooks were delivered within 3.1 s and 90% within 5.6 s. /v2/contact/email has the longest delivery time, 7.4 s at P50 and 32.1 s at P90: 5.8 s and 16.7 s when an email is found, 23.3 s and 45.4 s when none is found, because the waterfall queries several sources first.

Do Reverse Contact response times include rate-limited requests?

No. Reverse Contact response times exclude 429 responses, internal workspaces and personal accounts.

What is the availability of the Reverse Contact API?

From Oct 5 to Nov 1, 2026, the Reverse Contact API served 99.95% of customer requests. status.reversecontact.com provides live status and incident history.