Reverse Contact incident

V1 Endpoints: degraded perf...

Reverse Contact is currently experiencing a minor incident affecting V1 Scrapin & RC Legacy (Scrapin / RC), which began 18h ago. The vendor's full update timeline is below.

Started
May 08, 2026, 09:11 AM UTC
Resolved
Ongoing
Duration
● 18h 29m
Detected by Pingoru
May 08, 2026, 09:11 AM UTC

Affected components

V1 Scrapin & RC Legacy (Scrapin / RC)

Update timeline

  1. investigating May 08, 2026, 09:11 AM UTC

    Some V1 endpoints (not listed on this status page) are currently experiencing degraded performance, including long response times and intermittent unavailability. This stems from the live scraping nature of these legacy endpoints, which makes them inherently more sensitive to external disruptions. Our team has been actively working on stabilizing these endpoints over the past several weeks. In the meantime, we recommend migrating to the V2 API, which relies on our proprietary data lake and is not affected by these issues. Migration guides are available at app.reversecontact.com/docs/getting-started. We will continue to provide updates as the situation evolves.