<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:status.ellby.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://status.ellby.com"/>
  <link rel="self" type="application/atom+xml" href="https://status.ellby.com/history.atom"/>
  <title>Ellby Cloud Platform Status - Incident history</title>
  <updated>2026-08-25T10:00:00.000+00:00</updated>
  <author>
    <name>Ellby Cloud Platform</name>
  </author>
  
<entry>
  <id>tag:status.ellby.com,2005:Maintenance/cmt7dbi5k1ub90zme4pja153k</id>
  <published>2026-08-25T10:00:00.000+00:00</published>
  <updated>2026-08-25T14:16:58.525+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/maintenance/cmt7dbi5k1ub90zme4pja153k"/>
  <title>Filebound Cloud</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 hours and 17 minutes</p>
    <p><strong>Affected Components:</strong> FileBound Cloud</p>
    <p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>14:16:58</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance for this window has completed..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>15:05:32</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be conducting critical system maintenance during the following times:

 Maintenance Windows (AEST):

* Tuesday, 25 August 2026, 8:00 PM to Wednesday, 26 August 2026, 2:00 AM
* Wednesday, 26 August 2026, 8:00 PM to Thursday, 27 August 2026, 2:00 AM

During these maintenance periods, there is a possibility of service interruptions of up to 1 hour or slowdowns as we complete the necessary work. We apologise for any inconvenience this may cause and are committed to minimising the impact as much as possible.

If you have any questions or concerns, please contact your customer success manager or the support team via &lt;https://support.ellby.com/&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Maintenance/cmt6ivi9f17or1aplyasfd3nm</id>
  <published>2026-08-24T10:00:00.000+00:00</published>
  <updated>2026-08-24T15:01:07.856+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/maintenance/cmt6ivi9f17or1aplyasfd3nm"/>
  <title>FileBound Cloud</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 hours and 1 minute</p>
    <p><strong>Affected Components:</strong> FileBound Cloud</p>
    <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>15:01:07</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance for this window has completed..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>10:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>00:53:18</var> GMT+0</small><br /><strong>Identified</strong> -
  We will be conducting critical system maintenance during the following times:

Maintenance Windows (AEST):

* Monday, 24 August 2026, 8:00 PM to Tuesday, 25 August 2026, 2:00 AM
* Tuesday, 25 August 2026, 8:00 PM to Wednesday, 26 August 2026, 2:00 AM
* Wednesday, 26 August 2026, 8:00 PM to Thursday, 27 August 2026, 2:00 AM

During these maintenance periods, there is a possibility of service interruptions of up to 1 hour or slowdowns as we complete the necessary work. We apologise for any inconvenience this may cause and are committed to minimising the impact as much as possible.

If you have any questions or concerns, please contact your customer success manager or the support team via &lt;https://support.ellby.com/&gt;.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/cmrcwdgqy02xt0klh8e0gihld</id>
  <published>2026-07-09T01:40:00.000+00:00</published>
  <updated>2026-07-09T02:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/cmrcwdgqy02xt0klh8e0gihld"/>
  <title>FileBound Access Issues</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    <p><strong>Affected Components:</strong> FileBound Cloud</p>
    <p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>02:15:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  The resource issue has now been resolved and access restored. We will continue to monitor to ensure this has no further impacts..</p>
<p><small>Jul <var data-var='date'> 9</var>, <var data-var='time'>01:40:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Due to an underlying resource issue, access to several FileBound sites was impacted. We have identified the resource and are in the process of correcting the issue..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/cmqovp9lo0f452ipkcn8ym48v</id>
  <published>2026-06-22T07:13:05.062+00:00</published>
  <updated>2026-06-22T07:24:31.833+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/cmqovp9lo0f452ipkcn8ym48v"/>
  <title>Datajourney.com.au FileBound Sites</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> FileBound Cloud</p>
    <p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>07:24:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. All sites are accessible..</p>
<p><small>Jun <var data-var='date'> 22</var>, <var data-var='time'>07:13:05</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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/cmpbxxt7105y3qk0tt0gy9n83</id>
  <published>2026-05-19T01:15:00.576+00:00</published>
  <updated>2026-05-20T00:12:51.569+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/cmpbxxt7105y3qk0tt0gy9n83"/>
  <title>Connection Timeout Issues in EllbyConnect</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 hours and 58 minutes</p>
    <p><strong>Affected Components:</strong> EllbyConnect Service</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'>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>
<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'>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'>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'>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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/cmotay0c802qfhp16jx74oggs</id>
  <published>2026-05-06T00:11:26.991+00:00</published>
  <updated>2026-05-06T11:25:50.379+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/cmotay0c802qfhp16jx74oggs"/>
  <title>Intermittent Connectivity Issues with EllbyConnect</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 hours and 14 minutes</p>
    <p><strong>Affected Components:</strong> EllbyConnect Service</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>
<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:  
  
_&quot;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&quot;_.</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'>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'>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'>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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/cmerqzq1g002rmj1qk3uqshck</id>
  <published>2025-08-25T23:28:04.494+00:00</published>
  <updated>2025-08-26T00:58:53.707+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/cmerqzq1g002rmj1qk3uqshck"/>
  <title>Datajourney.com.au FileBound Sites</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 31 minutes</p>
    <p><strong>Affected Components:</strong> FileBound Cloud</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>
<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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Maintenance/cm41vtwko008e10rnmw9d9g2t</id>
  <published>2024-12-07T15:30:00.000+00:00</published>
  <updated>2024-12-07T15:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/maintenance/cm41vtwko008e10rnmw9d9g2t"/>
  <title>Scheduled Maintenance - Sunday December 8 @ 1:30am AEST</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> EllbyExtract Service, EllbyConnect Service</p>
    <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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/clxk0ywpt16778bkn1h2ibn8bh</id>
  <published>2024-06-18T06:30:12.381+00:00</published>
  <updated>2024-06-18T06:42:20.672+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/clxk0ywpt16778bkn1h2ibn8bh"/>
  <title>Datajourney.com.au FileBound sites</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> FileBound Cloud</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>
<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>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:status.ellby.com,2005:Incident/clmq15ipe78011bfmza4y1n0i4</id>
  <published>2023-09-19T08:05:13.587+00:00</published>
  <updated>2023-09-19T11:52:46.803+00:00</updated>
  <link rel="alternate" type="text/html" href="https://status.ellby.com/incident/clmq15ipe78011bfmza4y1n0i4"/>
  <title>RPA - intermittent service issue</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> Robotic Process Automation</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>
<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'>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'>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>

        ]]>
  </content>
</entry>

</feed>