Chain.io Outage History

Started Apr 27, 2026, 05:17 PM UTC· resolved Apr 27, 2026, 06:05 PM UTC

1. identified Apr 27, 2026, 05:17 PM UTC

   We are experiencing an outage with our SFTP authorization service.

2. resolved Apr 27, 2026, 06:05 PM UTC

   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.

Read the full incident report →

Started Apr 03, 2026, 07:01 PM UTC· resolved Apr 03, 2026, 08:02 PM UTC

1. investigating Apr 03, 2026, 07:01 PM UTC

   Some users are experiencing issues loading the dashboard and search pages. We are diagnosing the problem. We do not have an indication that this is impacting flow processing at this time.

2. monitoring Apr 03, 2026, 07:57 PM UTC

   We've fixed the core issue, and are waiting for things to recover.

3. resolved Apr 03, 2026, 08:02 PM UTC

   We've now resolved the incident. It was a screen error only and did not impact flow processing. Thanks for your patience.

Read the full incident report →

Started Apr 03, 2026, 03:39 PM UTC· resolved Apr 03, 2026, 04:40 PM UTC

1. investigating Apr 03, 2026, 03:39 PM UTC

   We are investigating slowness in some high volume flows. No data is being lost. We are working to resolve issue and report back as progress made.

2. resolved Apr 03, 2026, 04:40 PM UTC

   This was a false alarm, thanks for your patience.

Read the full incident report →

Started Mar 19, 2026, 07:14 PM UTC· resolved Mar 19, 2026, 07:55 PM UTC

1. investigating Mar 19, 2026, 07:14 PM UTC

   Flows running on schedule are currently being investigated. We will provide an update as further details identified. Thanks for your patience.

2. identified Mar 19, 2026, 07:41 PM UTC

   We have confirmed there is an issue with Scheduled Job Host Systems & Connections. This **does not impact SFTP** polling jobs. All other APIs and flow types remain functional. We are preparing a fix at this time.

3. resolved Mar 19, 2026, 07:55 PM UTC

   We've now resolved the incident. Thanks for your patience. All scheduled jobs are now runnning properly.

Read the full incident report →

Started Feb 10, 2026, 09:52 PM UTC· resolved Feb 10, 2026, 10:48 PM UTC

1. investigating Feb 10, 2026, 09:52 PM UTC

   Some users are experiencing errors accessing the portal. We are currently investigating this issue and will provide an update when we have more information.

2. investigating Feb 10, 2026, 10:10 PM UTC

   An underlying service provider has confirmed that they are having issues that may be impacting the portal, AS2, and SFTP services. We are carefully testing these services and have not observed any impact on our systems at this time.

3. resolved Feb 10, 2026, 10:48 PM UTC

   Our underlying service provider has indicated that the root issue has been resolved and service restored. Thank you for your patience.

Read the full incident report →

Started Nov 13, 2025, 07:50 PM UTC· resolved Nov 13, 2025, 08:49 PM UTC

1. identified Nov 13, 2025, 07:50 PM UTC

   A small percentage of flow executions are not showing complete but rather in progress in portal. Processing is not affected. Log messages can be viewed for accuracy. Flow notifications on the affected exections will not be sent. We will monitor and update when fully resolved.

2. resolved Nov 13, 2025, 08:49 PM UTC

   This false alarm was isolated to a single transaction.

Read the full incident report →

Started Nov 05, 2025, 09:41 PM UTC· resolved Nov 05, 2025, 09:42 PM UTC

1. identified Nov 05, 2025, 09:41 PM UTC

   We are currently experiencing an outage related only to viewing flow executions in portal.chain.io. It is not impacting other screens, including search or the processing of any data. You can view your flow statuses via the search screen while we apply the hotfix. We expect this to be resolved within a few minutes.

2. resolved Nov 05, 2025, 09:42 PM UTC

   We've now resolved the incident. Thanks for your patience.

Read the full incident report →

Started Oct 20, 2025, 04:10 PM UTC· resolved Oct 20, 2025, 08:02 PM UTC

1. investigating Oct 20, 2025, 04:10 PM UTC

   We are experiencing slighly increased processing and error rates related to previous incident with our service provider. We will monitor any Technical Errors and resubmit flow executions where it is appropriate for us to do so. and will provide updates on progress. Thank you for your patience.

2. investigating Oct 20, 2025, 05:15 PM UTC

   We are continuing to evaluate the impact of the ongoing issues with our underlying service provider in order to determine the best course of action.

3. investigating Oct 20, 2025, 06:22 PM UTC

   We are continuing to experience latency and confirmed that we are not losing data. We are still monitoring impact and will provide regular updates.

4. monitoring Oct 20, 2025, 07:18 PM UTC

   AWS has begun recovering from the most recent delays. We expect to see processing latency improvements shortly and will continue to monitor and advise here.

5. resolved Oct 20, 2025, 08:02 PM UTC

   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.

Read the full incident report →

Started Oct 20, 2025, 07:45 AM UTC· resolved Oct 20, 2025, 12:02 PM UTC

1. identified Oct 20, 2025, 07:45 AM UTC

   We are currently investigating and underlying outage with AWS which is impacting the ability to log into portal.chain.io and may also be impacting data processing. Per Chain.io BC/DR processes, we will monitor and advise during this outage. If the incident extends several more hours we may activate a business continuity response.

2. identified Oct 20, 2025, 08:05 AM UTC

   AWS has confirmed the incident and that they are working on a resolution. At this time, Chain.io will continue to wait for AWS resolution. We will also continue to post updates here as we have them. If you would like to follow the AWS status page directly it is available here: https://health.aws.amazon.com/health/status

3. identified Oct 20, 2025, 08:34 AM UTC

   AWS Engineers have informed us that they are engaged and are working to identfiy the root cause. There will be another update at the top of the hour.

4. identified Oct 20, 2025, 09:04 AM UTC

   AWS has identified a potential root cause related to domain name resolution and are working to implement a fix. We will continue to provide updates here as they become available.

5. monitoring Oct 20, 2025, 09:24 AM UTC

   AWS is begining to see recovery and we are also seeing some services become available again. We are carefully monitoring to ensure a clean recovery and will provide further updates here once service is fully restored.

6. monitoring Oct 20, 2025, 09:31 AM UTC

   Access to portal.chain.io has been restored. We are researching the impact on other services and will post an update closing the incident as soon as we are fully confident that all services are restored.

7. monitoring Oct 20, 2025, 09:47 AM UTC

   We are seeing data processing and are working through a backlog of previous submissions. When the backlog clears we will notify any impacted customers of any irregular processes that may need to be addressed manually. **IMPORTANT NOTE**: During the outage, systems sending to Chain.io likely received SFTP or HTTP connection failures. In those cases, the impacted systems should use their normal retry or requeue mechanisms.

8. monitoring Oct 20, 2025, 10:08 AM UTC

   For Cargowise users, we are successfully collecting and queuing data for eAdaptor messages to Chain.io, however there is a processing delay. You many not see results while the queue processes, but as of 9:21 UTC we are receiving the data. Between approximately 7:05 UTC and 9:21 UTC eAdaptor would have received error messages and would have held for reprocessing. We will continue to post updates here as the queue size resolves.

9. monitoring Oct 20, 2025, 11:17 AM UTC

   We have received further communication from Amazon that the specific service that we use to manage flow message queues continues to experience delays. These delays are impacting flow processing. All data received since our HTTP & eAdaptor services recovered is queued and properly saved. When the service performance returns to normal, your data will be processed. At this time, any service that has receieved a successful response from a Chain.io endpoint does not need to resend data.

10. identified Oct 20, 2025, 11:27 AM UTC

    As we continue to monitor the queue issue, we are moving our status back to Identified. All data continues to be captured and we will provide updates as the queues begin to clear.

11. resolved Oct 20, 2025, 12:02 PM UTC

    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].

Read the full incident report →

Started Sep 23, 2025, 06:34 PM UTC· resolved Sep 23, 2025, 06:50 PM UTC

1. investigating Sep 23, 2025, 06:34 PM UTC

   Some users are experiencing issues deploying flows. We are investigating now. This does not impact any live data processing.

2. resolved Sep 23, 2025, 06:50 PM UTC

   We've now resolved the incident. Thanks for your patience. No data processing was impacted by this incident.

Read the full incident report →

Started Sep 23, 2025, 03:45 PM UTC· resolved Sep 23, 2025, 04:13 PM UTC

1. monitoring Sep 23, 2025, 03:45 PM UTC

   Loading some flow executions in portal.chain.io are failing when the flows have certain notifier configurations on them. This is **not impacting processing of data.** We are currently in the process of resolving the underlying issue.

2. resolved Sep 23, 2025, 04:13 PM UTC

   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.

Read the full incident report →

Started Sep 09, 2025, 01:29 PM UTC· resolved Sep 09, 2025, 02:43 PM UTC

1. identified Sep 09, 2025, 01:29 PM UTC

   We are currently experiencing an issue related to reflecting the correct status of flows in portal.chain.io. **Flows are still executing normally and this is limited to visibility in the portal and notifications.** You may not find records in search or see the correct status for recent flows. Data is processing and statuses will update when the issue is resolved.

2. monitoring Sep 09, 2025, 01:57 PM UTC

   We've isolated the issue to a small number of flows which will have their statuses updated shortly. We will post a completion message here when all flows are properly reflecting their statuses.

3. resolved Sep 09, 2025, 02:43 PM UTC

   We've now resolved the incident. Thanks for your patience. All flows have completed as expected and statuses are reflected properly in the portal.

Read the full incident report →

Started Jun 25, 2025, 04:40 PM UTC· resolved Jun 25, 2025, 05:13 PM UTC

1. monitoring Jun 25, 2025, 04:40 PM UTC

   Please note some latency has been experienced in reporting data back to Portal. Thanks for your patience as we monitor to move status to resolved.

2. resolved Jun 25, 2025, 05:13 PM UTC

   We've now resolved the incident and latency has ended. Thanks for your patience.

Read the full incident report →

Started Jun 11, 2025, 03:15 PM UTC· resolved Jun 11, 2025, 03:56 PM UTC

1. monitoring Jun 11, 2025, 03:15 PM UTC

   We have identified an issue where we are triggering excess notification emails. The content of the emails is accurate, but you may receive notifications for flows you were not expecting. We have rolled back the code change, and you should not see additional messages once the outbound queues are cleared in the next several minutes.

2. resolved Jun 11, 2025, 03:56 PM UTC

   We've now resolved the incident. From the time period of 14:41 UTC - 15:14 UTC, you may have received additional notification emails. Those emails were accurate but may have been for statuses you did not subscribe to.

Read the full incident report →

Started Apr 16, 2025, 08:14 PM UTC· resolved Apr 16, 2025, 08:40 PM UTC

1. investigating Apr 16, 2025, 08:14 PM UTC

   We are currently experiencing intermittent issues related to loading configuration data on portal.chain.io. These issues do not appear to be impacting the processing of data or flows. We are currently investigating and will update here as information is available. No action is needed at this time.

2. resolved Apr 16, 2025, 08:40 PM UTC

   The problem is isolated to loading the main workspace page for workspaces with greater than approximately 20 integrations. All other functionality in the portal and flows is not impacted. We will continue to monitor offline and are closing the incident.

Read the full incident report →

Started Feb 18, 2025, 10:21 PM UTC· resolved Feb 19, 2025, 11:22 AM UTC

1. identified Feb 18, 2025, 10:21 PM UTC

   EDI messages utilizing Legacy Boomi connections are experiencing degraded performance due to a service provider outage. The service provider has identified the issue and is working on a fix. We are monitoring the situation and will advise when failed transactions can be reprocessed.

2. monitoring Feb 18, 2025, 11:11 PM UTC

   Our service provider is continuing to work to resolve the issue. You may experience sporadic failures for Boomi related transactions. We recommend waiting until the incident is fully resolved before reprocessing failed transactions.

3. monitoring Feb 18, 2025, 11:55 PM UTC

   No change in status: Our service provider is continuing to work to resolve the issue. You may experience sporadic failures for Boomi related transactions. We recommend waiting until the incident is fully resolved before reprocessing failed transactions.

4. monitoring Feb 19, 2025, 01:00 AM UTC

   No change in status: Our service provider is continuing to work to resolve the issue. You may experience sporadic failures for Boomi related transactions. We recommend waiting until the incident is fully resolved before reprocessing failed transactions.

5. monitoring Feb 19, 2025, 04:15 AM UTC

   No change in status: Our service provider is continuing to work to resolve the issue. You may experience sporadic failures for Boomi related transactions. We recommend waiting until the incident is fully resolved before reprocessing failed transactions.

6. monitoring Feb 19, 2025, 05:07 AM UTC

   Boomi continues to experience a transient issue. There will be no further updates until the issue is resolved. You can track the direct issue here: [https://status.boomi.com/incidents/xrjhk2pmp3l7](https://status.boomi.com/incidents/xrjhk2pmp3l7)

7. resolved Feb 19, 2025, 11:22 AM UTC

   Boomi has resolved the incident as of 3:26am EST. You may now reprocess any failed transactions Thanks for your patience.

Read the full incident report →

Started Jan 10, 2025, 12:00 AM UTC· resolved Jan 10, 2025, 12:06 AM UTC

1. identified Jan 10, 2025, 12:00 AM UTC

   We are aware of EDI error. Once addressed we will reprocess any failures. Thanks for your patience.

2. resolved Jan 10, 2025, 12:06 AM UTC

   We've now resolved the incident and any failed transactions will be reprocessed. Thanks for your patience.

Read the full incident report →