Ellby Cloud Platform Status - Incident history https://status.ellby.com Ellby Cloud Platform Tue, 19 May 2026 01:15:00 +0000 Connection Timeout Issues in EllbyConnect Type: Incident Duration: 22 hours and 58 minutes Affected Components: EllbyConnect Service May 19, 01:15:00 GMT+0 - Investigating - We are seeing increased Timeout errors in executions within EllbyConnect, we are currently working with Microsoft support to determine the source of the issue. We will update further as we make progress. May 20, 00:12:51 GMT+0 - Resolved - We are no longer seeing Timeout issues in the EllbyConnect platform. We are continuing to work with Microsoft engineering to minimise the risk of future platform changes such as these. This incident is now resolved. May 19, 03:13:45 GMT+0 - Identified - We are continuing to work with Microsoft support for a resolution to this issue. We will advise when we have an ETA for resolution. May 19, 05:53:59 GMT+0 - Identified - Microsoft have escalated this to the internal engineering team as a likely platform issue, we will advise once we have further updates. May 19, 09:39:30 GMT+0 - Monitoring - We have been informed by Microsoft that a background update to a component of their execution platform that correlates to the timing of our issue is the likely cause of the degraded performance. This change is in the process of being reverted and we expect normal operations to resume once that is completed over the next hour. We will monitor operations post this rollback and resolve the issue once we are seeing normal operational performance. May 19, 21:23:13 GMT+0 - Monitoring - The EllbyConnect service is operating normally after the Microsoft changes were reverted. We will continue to monitor under load and resolve the issue after further monitoring shows no further issues. Type: Incident

Duration: 22 hours and 58 minutes

Affected Components:

<p><small>May <var data-var='date'> 19</var>, <var data-var='time'>01:15:00</var> GMT+0</small><br><strong>Investigating</strong> - We are seeing increased Timeout errors in executions within EllbyConnect, we are currently working with Microsoft support to determine the source of the issue. We will update further as we make progress..</p> <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>00:12:51</var> GMT+0</small><br><strong>Resolved</strong> - We are no longer seeing Timeout issues in the EllbyConnect platform. We are continuing to work with Microsoft engineering to minimise the risk of future platform changes such as these. This incident is now resolved. .</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>03:13:45</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work with Microsoft support for a resolution to this issue. We will advise when we have an ETA for resolution..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>05:53:59</var> GMT+0</small><br><strong>Identified</strong> - Microsoft have escalated this to the internal engineering team as a likely platform issue, we will advise once we have further updates..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>09:39:30</var> GMT+0</small><br><strong>Monitoring</strong> - We have been informed by Microsoft that a background update to a component of their execution platform that correlates to the timing of our issue is the likely cause of the degraded performance. This change is in the process of being reverted and we expect normal operations to resume once that is completed over the next hour. We will monitor operations post this rollback and resolve the issue once we are seeing normal operational performance..</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>21:23:13</var> GMT+0</small><br><strong>Monitoring</strong> - The EllbyConnect service is operating normally after the Microsoft changes were reverted. We will continue to monitor under load and resolve the issue after further monitoring shows no further issues. .</p> ]]> Tue, 19 May 2026 01:15:00 +0000 https://status.ellby.com/incident/cmpbxxt7105y3qk0tt0gy9n83 https://status.ellby.com/incident/cmpbxxt7105y3qk0tt0gy9n83 Intermittent Connectivity Issues with EllbyConnect Type: Incident Duration: 11 hours and 14 minutes Affected Components: EllbyConnect Service May 6, 00:11:26 GMT+0 - Investigating - We are currently investigating this issue and will update further as we make progress. May 6, 02:46:02 GMT+0 - Investigating - We are currently working with Microsoft Support to determine the source of the issue. We will update further as we make progress. May 6, 06:55:49 GMT+0 - Identified - We are continuing to work with Microsoft on a fix for this. The issue has been escalated to their engineering team for further investigation. We will update once we have more information from them on the issue. May 6, 08:13:09 GMT+0 - Identified - Microsoft engineering have informed us that this is a global issue with a connector for SQL. They are currently working on a fix and will let us know when they have an ETA for resolution. We will update when we have further information from them on a fix. May 6, 09:34:05 GMT+0 - Monitoring - We have been advised by Microsoft that this incident has now been resolved. We will monitor the fix to ensure this is the case and will close this incident once we are satisfied with the resolution. Microsoft tracking ID 5Y3C-MLZ: _"Between 18:36 UTC on 5 May 2026 and 07:42 UTC on 6 May 2026, a platform issue resulted in an impact to the Logic Apps service in the Australia region. Customers may have experienced failures when running workflows that connect to SQL through On-Premises Data Gateway, preventing workflows from completing as expected. This issue is now mitigated"_ May 6, 11:25:50 GMT+0 - Resolved - This incident has been resolved, all systems are functioning as normal. Microsoft provided Root Cause Analysis : | TRACKING ID:5Y3C-MLZ | TYPE:**Incident** | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | | STATUS:**Root Cause Analysis** | | | COMMUNICATION:**What happened?**Between 18:36 UTC 05 May 2026 and 07:42 UTC on 06 May 2026, a platform issue resulted in an impact to the Logic Apps service in the Australia region. Impacted customers experienced failures when running workflows that connect to SQL through On-Premises Data Gateway, preventing workflows from completing as expected.**What went wrong, and why?**During the deployment of SQL Connector service, an issue was introduced on the backend service that caused connection failures for Logic Apps workflows using SQL connections via Gateway. This issue occurred within the service following the deployment and prevented workflows from establishing or using connections as expected. The problem was identified and addressed by reverting the affected deployment, which restored normal service behavior.**How did we respond?**18:36 UTC on 05 May 2026 – Customer impact began.07:18 UTC on 06 May 2026 – Correlation with a recent SQL Connector deployment was identified.07:30 UTC on 06 May 2026 – Rollback of the recent deployment was initiated as the mitigation workstream.07:42 UTC on 06 May 2026 – Service restored, and customer impact mitigated. | | Type: Incident

Duration: 11 hours and 14 minutes

Affected Components:

<p><small>May <var data-var='date'> 6</var>, <var data-var='time'>00:11:26</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this issue and will update further as we make progress..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>02:46:02</var> GMT+0</small><br><strong>Investigating</strong> - We are currently working with Microsoft Support to determine the source of the issue. We will update further as we make progress..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>06:55:49</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work with Microsoft on a fix for this. The issue has been escalated to their engineering team for further investigation. We will update once we have more information from them on the issue..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>08:13:09</var> GMT+0</small><br><strong>Identified</strong> - Microsoft engineering have informed us that this is a global issue with a connector for SQL. They are currently working on a fix and will let us know when they have an ETA for resolution. We will update when we have further information from them on a fix..</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>09:34:05</var> GMT+0</small><br><strong>Monitoring</strong> - We have been advised by Microsoft that this incident has now been resolved. We will monitor the fix to ensure this is the case and will close this incident once we are satisfied with the resolution. Microsoft tracking ID 5Y3C-MLZ: _"Between 18:36 UTC on 5 May 2026 and 07:42 UTC on 6 May 2026, a platform issue resulted in an impact to the Logic Apps service in the Australia region. Customers may have experienced failures when running workflows that connect to SQL through On-Premises Data Gateway, preventing workflows from completing as expected. This issue is now mitigated"_.</p> <p><small>May <var data-var='date'> 6</var>, <var data-var='time'>11:25:50</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, all systems are functioning as normal. Microsoft provided Root Cause Analysis : | TRACKING ID:5Y3C-MLZ | TYPE:**Incident** | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------- | | STATUS:**Root Cause Analysis** | | | COMMUNICATION:**What happened?**Between 18:36 UTC 05 May 2026 and 07:42 UTC on 06 May 2026, a platform issue resulted in an impact to the Logic Apps service in the Australia region. Impacted customers experienced failures when running workflows that connect to SQL through On-Premises Data Gateway, preventing workflows from completing as expected.**What went wrong, and why?**During the deployment of SQL Connector service, an issue was introduced on the backend service that caused connection failures for Logic Apps workflows using SQL connections via Gateway. This issue occurred within the service following the deployment and prevented workflows from establishing or using connections as expected. The problem was identified and addressed by reverting the affected deployment, which restored normal service behavior.**How did we respond?**18:36 UTC on 05 May 2026 – Customer impact began.07:18 UTC on 06 May 2026 – Correlation with a recent SQL Connector deployment was identified.07:30 UTC on 06 May 2026 – Rollback of the recent deployment was initiated as the mitigation workstream.07:42 UTC on 06 May 2026 – Service restored, and customer impact mitigated. | |.</p> ]]> Wed, 6 May 2026 00:11:26 +0000 https://status.ellby.com/incident/cmotay0c802qfhp16jx74oggs https://status.ellby.com/incident/cmotay0c802qfhp16jx74oggs Datajourney.com.au FileBound Sites Type: Incident Duration: 1 hour and 31 minutes Affected Components: FileBound Cloud Aug 25, 23:28:04 GMT+0 - Identified - All FileBound sites in the [datajourney.com.au](http://datajourney.com.au) domain are currently not accessible due to a external DNS provider issue. We are currently working with the provider to have access restored. Aug 26, 00:58:53 GMT+0 - Resolved - This incident has been resolved. DNS services have been restored by the external provider for [Datajourney.com.au](http://Datajourney.com.au) FileBound Sites. Type: Incident

Duration: 1 hour and 31 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>23:28:04</var> GMT+0</small><br><strong>Identified</strong> - All FileBound sites in the [datajourney.com.au](http://datajourney.com.au) domain are currently not accessible due to a external DNS provider issue. We are currently working with the provider to have access restored..</p> <p><small>Aug <var data-var='date'> 26</var>, <var data-var='time'>00:58:53</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. DNS services have been restored by the external provider for [Datajourney.com.au](http://Datajourney.com.au) FileBound Sites..</p> ]]> Mon, 25 Aug 2025 23:28:04 +0000 https://status.ellby.com/incident/cmerqzq1g002rmj1qk3uqshck https://status.ellby.com/incident/cmerqzq1g002rmj1qk3uqshck Scheduled Maintenance - Sunday December 8 @ 1:30am AEST Type: Maintenance Affected Components: EllbyExtract Service, EllbyConnect Service Dec 7, 15:30:00 GMT+0 - Completed - Due to AWS infrastructure maintenance, there may be up to 30 mins of downtime for the Filetransfer and CloudCap services. This maintenance will not impact FileBound Cloud, all sites will remain available during this maintenance. Type: Maintenance

Affected Components: ,

<p><small>Dec <var data-var='date'> 7</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Completed</strong> - Due to AWS infrastructure maintenance, there may be up to 30 mins of downtime for the Filetransfer and CloudCap services. This maintenance will not impact FileBound Cloud, all sites will remain available during this maintenance..</p> ]]> Sat, 7 Dec 2024 15:30:00 +0000 https://status.ellby.com/maintenance/cm41vtwko008e10rnmw9d9g2t https://status.ellby.com/maintenance/cm41vtwko008e10rnmw9d9g2t Datajourney.com.au FileBound sites Type: Incident Duration: 12 minutes Affected Components: FileBound Cloud Jun 18, 06:30:12 GMT+0 - Identified - All FileBound sites in the [datajourney.com.au](http://datajourney.com.au) domain are currently not accessible due to a external DNS provider issue. We are currently working with the provider to have access restored. Jun 18, 06:42:20 GMT+0 - Resolved - This incident has been resolved. DNS services have been restored by the external provider for [Datajourney.com.au](http://Datajourney.com.au) FileBound Sites. Type: Incident

Duration: 12 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>06:30:12</var> GMT+0</small><br><strong>Identified</strong> - All FileBound sites in the [datajourney.com.au](http://datajourney.com.au) domain are currently not accessible due to a external DNS provider issue. We are currently working with the provider to have access restored..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>06:42:20</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. DNS services have been restored by the external provider for [Datajourney.com.au](http://Datajourney.com.au) FileBound Sites..</p> ]]> Tue, 18 Jun 2024 06:30:12 +0000 https://status.ellby.com/incident/clxk0ywpt16778bkn1h2ibn8bh https://status.ellby.com/incident/clxk0ywpt16778bkn1h2ibn8bh RPA - intermittent service issue Type: Incident Duration: 3 hours and 48 minutes Affected Components: Robotic Process Automation Sep 19, 08:05:13 GMT+0 - Identified - The RPA service is experiencing intermittent issues. We have raised a support case with the vendor and will continue to work with them to solve the issue. Sep 19, 08:24:03 GMT+0 - Monitoring - The RPA service is now up and running, we are monitoring to ensure it is stable. Sep 19, 09:43:50 GMT+0 - Monitoring - We are continuing to monitor the service while we work with the vendor to establish the cause of the issue. Sep 19, 11:52:46 GMT+0 - Resolved - This incident has been resolved. RPA is operational. Type: Incident

Duration: 3 hours and 48 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>08:05:13</var> GMT+0</small><br><strong>Identified</strong> - The RPA service is experiencing intermittent issues. We have raised a support case with the vendor and will continue to work with them to solve the issue..</p> <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>08:24:03</var> GMT+0</small><br><strong>Monitoring</strong> - The RPA service is now up and running, we are monitoring to ensure it is stable..</p> <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>09:43:50</var> GMT+0</small><br><strong>Monitoring</strong> - We are continuing to monitor the service while we work with the vendor to establish the cause of the issue..</p> <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>11:52:46</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. RPA is operational..</p> ]]> Tue, 19 Sep 2023 08:05:13 +0000 https://status.ellby.com/incident/clmq15ipe78011bfmza4y1n0i4 https://status.ellby.com/incident/clmq15ipe78011bfmza4y1n0i4