Chain.io had 13 outages in the last 2 years totaling 16h 7m of downtime — averaging 0.5 incidents per month.
There were 13 Chain.io outages since June 25, 2025 totaling 16h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.
We've now resolved the incident. Any 3rd party connections that failed to connect can be retried. The Chain.io team is reviewing internal failed connections over the timeframe and will advise customers on retries individually.
We've now resolved the incident. It was a screen error only and did not impact flow processing. Thanks for your patience.
This was a false alarm, thanks for your patience.
We've now resolved the incident. Thanks for your patience. All scheduled jobs are now runnning properly.
Our underlying service provider has indicated that the root issue has been resolved and service restored. Thank you for your patience.
This false alarm was isolated to a single transaction.
We've now resolved the incident. Thanks for your patience.
We are currently seeing all traffic moving at normal speeds and will continue to monitor for abberations. We will not be providing further updates via this channel unless we encounter degraded service again.
The queues are now processing and you will see accurate status updates in the portal. We will continue to monitor for any actions needed related to data from the 07:00 - 07:05 AM UTC time. We will inform any impacted customers directly. At this point, we are closing the incident. If you have noticed any other behavior which may be a problem, please contact [email protected].
We've now resolved the incident. Thanks for your patience. No data processing was impacted by this incident.
We've now resolved the incident. Thanks for your patience. This was a **display only** issue for flows that had notifiers with log or data tag filtering enabled. There were no problems with data processing during this incident.
We've now resolved the incident. Thanks for your patience. All flows have completed as expected and statuses are reflected properly in the portal.
We've now resolved the incident and latency has ended. Thanks for your patience.