pingoru pingoru Reco had 5 outages in the last 2 years totaling 20h 59m of downtime, averaging 0.2 incidents per month.
There were 5 Reco outages since October 20, 2025 totaling 20h 59m of downtime. Each is summarised below. Incident details, duration, and resolution information.
One of our 3rd party vendors is experiencing an outage that is affecting our platform. We expect delayed data ingestions while they recover their system. No data is lost, just delayed.
A fix has been implemented and we are monitoring the results.
US region is fully operational.
One of our 3rd party vendors is experiencing an outage that is affecting our platform. We expect delayed data ingestions while they recover their system. No data is lost, just delayed.
We are continuing to monitor this issue.
We are continuing to monitor this issue.
We are seeing signs of improvement and expect full recovery within 30 minutes.
The issue has cleared and monitoring has concluded. All systems are operating normally, with no data loss.
This incident has been resolved.
Reco platform UI is currently unavailable to US customers due to an upstream provider recovering from the AWS outage. After logging to the platform, you may experience a blank page. Data ingestion, event processing, alerting and automations are working as usual and are not impacted.
Our upstream service provider is starting to recover. Some UI issues, such as blank pages, are still possible but should be temporary. Data ingestion could be slightly delayed.
The service provider updated that they are continuing their recovery efforts.
As their recovery efforts continue, UI errors in Reco platform should stop appearing. Data ingestion is still delayed.
The Reco platform is fully operational. Workarounds were put in place while the upstream provider returns to full capacity. Data ingestion pipeline is running and clearing up queued items Some integrations might still present errors as different upstream providers make a full recovery.
We are again observing intermittent issues authenticating to the Reco platform using social, SSO and OTP logins. This is caused by the AWS outage impacting global identity management providers and we're waiting for their updates.
This incident has been resolved.
The AWS outage impacted some of our upstream service providers, resulting in delayed or failed login attempts to the Reco platform. Once AWS recovered, so did our service providers and the login issue was resolved automatically.