Reverse Contact experienced a minor incident on May 8, 2026 affecting V1 Scrapin & RC Legacy (Scrapin / RC) and V1 Scrapin & RC Legacy (Scrapin / RC), lasting —. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- 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.