Reverse Contact Outage History

Reverse Contact is up right now

Reverse Contact had 34 outages in the last 2 years totaling 557h 6m of downtime — averaging 1.4 incidents per month.

There were 34 Reverse Contact outages since April 15, 2026 totaling 557h 6m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.reversecontact.com/en

Major June 16, 2026

Fetch Person - Person (live...

Detected by Pingoru
Jun 16, 2026, 03:05 PM UTC
Resolved
Jun 16, 2026, 03:07 PM UTC
Duration
1m
Affected: Fetch Persons (Fetch Person - Person (live))
Timeline · 2 updates
  1. investigating Jun 16, 2026, 03:05 PM UTC

    Fetch Person - Person (live) went down.

  2. resolved Jun 16, 2026, 03:07 PM UTC

    Fetch Person - Person (live) recovered.

Read the full incident report →

Major May 22, 2026

All activities are down

Detected by Pingoru
May 22, 2026, 04:07 PM UTC
Resolved
Jun 04, 2026, 09:13 AM UTC
Duration
12d 17h
Affected: Fetch Activities (Person posts)Fetch Activities (Person reactions)Fetch Activities (Person comments)Fetch Activities (Post details)Fetch Activities (Company posts)
Timeline · 1 update
  1. investigating May 22, 2026, 04:07 PM UTC

    Due to stability problems all the activities are down

Read the full incident report →

Minor May 21, 2026

Database is updating

Detected by Pingoru
May 21, 2026, 08:16 AM UTC
Resolved
May 21, 2026, 08:16 AM UTC
Duration
—
Affected: Fetch Persons (Fetch Person - Person (cache))
Timeline · 1 update
  1. resolved May 21, 2026, 08:16 AM UTC

    Database is good.

Read the full incident report →

Minor May 8, 2026

V1 Endpoints: degraded perf...

Detected by Pingoru
May 08, 2026, 09:11 AM UTC
Resolved
May 08, 2026, 09:11 AM UTC
Duration
—
Affected: V1 Scrapin & RC Legacy (Scrapin / RC)V1 Scrapin & RC Legacy (Scrapin / RC)
Timeline · 1 update
  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.

Read the full incident report →