Reverse Contact Outage History

Reverse Contact is up right now

Pingoru has recorded 831 incidents for Reverse Contact: 831 in the last 12 months and 43 in the last 90 days.

Source: status.reversecontact.com

831incidents recorded
831last 12 months
43last 90 days
2 hourstypical duration
Incidents per month
0250500AprMayJunJulAugSepOct9
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct1%
Pingoru began tracking Reverse Contact in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026325302 of 720 (42%)
May 2026443349 of 744 (47%)
June 202612191 of 720 (27%)
July 2026974 of 744 (10%)
August 202615138 of 744 (19%)
September 202618166 of 720 (23%)
October 202696 of 590 (1%)

Incidents, newest first

Minor May 4, 2026 Fetch Activities - Company posts (live) recovered –

Started May 04, 2026, 12:56 PM UTC· resolved May 04, 2026, 12:56 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 4, 2026 Fetch Activities - Persons comments (live) recovered –

Started May 04, 2026, 12:56 PM UTC· resolved May 04, 2026, 12:56 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor May 4, 2026 Fetch Activities - Post details (live) recovered –

Started May 04, 2026, 12:56 PM UTC· resolved May 04, 2026, 12:56 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 24, 2026 Contact - Email verify recovered –

Started Apr 24, 2026, 05:47 AM UTC· resolved Apr 24, 2026, 05:47 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Minor April 23, 2026 API Incident 3d 10h section-313604 (Fetch Person - Person (live)), section-313606 (Fetch Company - company (live))

Started Apr 23, 2026, 07:48 AM UTC· resolved Apr 26, 2026, 05:51 PM UTC

  1. investigating Apr 23, 2026, 07:48 AM UTC

    We're aware of an ongoing incident impacting API requests. Our team is fully mobilized and working to restore normal service as quickly as possible. Thanks for your patience.

Read the full incident report →

Minor April 18, 2026 Search API Degraded Perform... 24d 20h section-313605 (Search API - Person Search), section-313605 (Search API - Company Search)

Started Apr 18, 2026, 12:06 PM UTC· resolved May 13, 2026, 08:47 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Major April 17, 2026 Service Disruption – Data P... 1h 37m section-313604 (Fetch Person - Person (live)), section-313606 (Fetch Company - company (live)), Resolve (async mode) (Resolve - Persons (name)), Resolve (async mode) (Resolve - Persons (email)) and 1 more

Started Apr 17, 2026, 12:10 PM UTC· resolved Apr 17, 2026, 01:47 PM UTC

  1. investigating Apr 17, 2026, 12:10 PM UTC

    We are currently experiencing a service outage. Our system is currently delivering improperly formatted data, causing malformed input on our side. To protect the integrity and quality of our data, our automated data quality protection system was triggered immediately upon detection of the issue. As a result, affected services are temporarily unavailable while the issue is being investigated and resolved. We are actively working with our data provider to address the root cause. Further updates will be posted here as the situation evolves. We apologize for the inconvenience and appreciate your patience.

Read the full incident report →

Major April 15, 2026 API Outage - Infrastructure... 36m section-313604 (Fetch Person - Person (cache)), section-313604 (Fetch Person - Person (live)), section-313606 (Fetch Company - company (cache)), section-313606 (Fetch Company - company (live)) and 13 more

Started Apr 15, 2026, 08:04 AM UTC· resolved Apr 15, 2026, 08:40 AM UTC

  1. investigating Apr 15, 2026, 08:04 AM UTC

    We're currently experiencing an infrastructure issue affecting all API endpoints. Our team is actively working on a fix and we'll keep this updated as we make progress. Sorry for the disruption.

Read the full incident report →