Fetch Activities - Post comments (live) recovered
Timeline · 1 update
- investigating Apr 30, 2026, 10:11 AM UTC
Fetch Activities - Post comments (live) went down
Reverse Contact had 34 outages in the last 2 years totaling 680h 57m of downtime — averaging 1.4 incidents per month.
There were 34 Reverse Contact outages since April 15, 2026 totaling 680h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
Fetch Activities - Post comments (live) went down
Fetch Activities - Company posts (live) went down
Fetch Activities - Persons comments (live) went down
Fetch Activities - Post details (live) went down
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.
Hey, after several days of intense work, our engineering team has managed to stabilize the endpoints that were causing issues. We're still actively monitoring things, so you might occasionally see some residual errors pop up. The team is continuing to track them and push fixes as fast as possible. Thanks so much for your patience!
We're currently refreshing our profile and company data along with optimizing all search indexes. During this process, which may take several days, you might experience slower response times on the Search API. We're running these operations carefully to keep the impact as low as possible and will update this page once everything is back to full speed. Thanks for your patience!
We’ve stabilized the Search API; behavior should finally be back to normal. We’re still monitoring latency and availability.
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.
Everything looks nominal.
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.
All API endpoints are back up and running normally. Thanks for your patience!