Reverse Contact Outage History

Reverse Contact is up right now

Reverse Contact had 37 outages in the last 2 years totaling 467h 6m of downtime — averaging 1.5 incidents per month.

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

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

Major August 2, 2026

Resolve - Persons (name) a...

Detected by Pingoru
Aug 02, 2026, 10:15 AM UTC
Resolved
Aug 02, 2026, 06:14 PM UTC
Duration
7h 59m
Affected: Resolve (async mode) (Resolve - Persons (name))Resolve (async mode) (Resolve - Persons (email))
Timeline · 4 updates
  1. investigating Aug 02, 2026, 10:15 AM UTC

    Resolve - Persons (name) went down.

  2. resolved Aug 02, 2026, 10:16 AM UTC

    Resolve - Persons (name) recovered.

  3. resolved Aug 02, 2026, 06:02 PM UTC

    Resolve - Persons (name) recovered.

  4. resolved Aug 02, 2026, 06:14 PM UTC

    Resolve - Persons (email) recovered.

Read the full incident report →

Major August 1, 2026

Fetch Person - Person (live...

Detected by Pingoru
Aug 01, 2026, 01:09 PM UTC
Resolved
Aug 01, 2026, 09:01 PM UTC
Duration
7h 52m
Affected: Fetch Persons (Fetch Person - Person (live))Fetch Companies (Fetch Company - company (live))Resolve (async mode) (Resolve - Persons (name))Resolve (async mode) (Resolve - Persons (email))Resolve (async mode) (Resolve - Companies (domain))
Timeline · 3 updates
  1. investigating Aug 01, 2026, 01:09 PM UTC

    Fetch Person - Person (live), Fetch Company - company (live), Resolve - Persons (name), and 2 other resources went down.

  2. resolved Aug 01, 2026, 01:11 PM UTC

    Fetch Person - Person (live), Fetch Company - company (live), Resolve - Persons (name), and 2 other resources recovered.

  3. resolved Aug 01, 2026, 09:01 PM UTC

    Resolve - Persons (email) recovered.

Read the full incident report →

Major July 14, 2026

Fetch Company - company (li...

Detected by Pingoru
Jul 14, 2026, 11:23 AM UTC
Resolved
Jul 14, 2026, 02:03 PM UTC
Duration
2h 40m
Affected: Fetch Companies (Fetch Company - company (live))Resolve (async mode) (Resolve - Persons (name))Resolve (async mode) (Resolve - Persons (email))Resolve (async mode) (Resolve - Companies (domain))
Timeline · 9 updates

Read the full incident report →

Major July 9, 2026

Fetch Person - Person (cach...

Detected by Pingoru
Jul 09, 2026, 12:05 AM UTC
Resolved
Jul 09, 2026, 12:46 PM UTC
Duration
12h 41m
Affected: Fetch Persons (Fetch Person - Person (cache))Fetch Persons (Fetch Person - Person (live))Fetch Companies (Fetch Company - company (cache))Enrich (sync) (Enrich - Persons)
Timeline · 15 updates

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 →