<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Awell Status - Incident history</title>
    <link>https://status.awellhealth.com</link>
    <description>Awell</description>
    <pubDate>Thu, 7 May 2026 07:00:00 +0000</pubDate>
    
<item>
  <title>Infrastructure maintenance in US</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 40 minutes

    Affected Components: [US] Awell Design, [US] Awell Platform - Web App, [US] Awell Operate
    May 7, 07:00:00 GMT+0 - Identified - We are performing a rolling infrastructure update in Sandbox to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts. May 7, 07:00:00 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing a rolling infrastructure update in Sandbox to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 7 May 2026 07:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmotporsm00ns71w19ihy7un9</link>
  <guid>https://status.awellhealth.com/maintenance/cmotporsm00ns71w19ihy7un9</guid>
</item>

<item>
  <title>Infrastructure maintenance in Production EU and UK</title>
  <description>
    Type: Maintenance
    

    Affected Components: [EU] Awell Design, [UK] Awell Operate, [EU] Awell Manage, [EU] Awell Operate, [EU] Mirth, [UK] Awell Design, [UK] Awell Manage
    May 7, 01:00:00 GMT+0 - Identified - We are performing a rolling infrastructure update in our production environments to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    
    <p><strong>Affected Components:</strong> , , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 7&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing a rolling infrastructure update in our production environments to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 7 May 2026 01:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmoti3qdq084lm10pxp6mx0xz</link>
  <guid>https://status.awellhealth.com/maintenance/cmoti3qdq084lm10pxp6mx0xz</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: [US] Awell Operate
    May 6, 12:50:19 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. May 6, 12:53:46 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:50:19&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:53:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 6 May 2026 12:50:19 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmou21wlh00hmxlbverp98527</link>
  <guid>https://status.awellhealth.com/incident/cmou21wlh00hmxlbverp98527</guid>
</item>

<item>
  <title>Infrastructure maintenance in Sandbox</title>
  <description>
    Type: Maintenance
    Duration: 20 minutes

    Affected Components: [Sandbox] Awell Design, [Sandbox] Awell Manage, [Sandbox] Awell Operate
    May 6, 03:30:00 GMT+0 - Identified - We are performing a rolling infrastructure update in Sandbox to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts. May 6, 03:30:01 GMT+0 - Identified - Maintenance is now in progress May 6, 03:49:31 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 20 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing a rolling infrastructure update in Sandbox to improve capacity and stability. Services are expected to remain available, with brief periods of reduced redundancy during component restarts..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 6&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:49:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 6 May 2026 03:30:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmoti1j6k03grt2xk4gmrwjsp</link>
  <guid>https://status.awellhealth.com/maintenance/cmoti1j6k03grt2xk4gmrwjsp</guid>
</item>

<item>
  <title>Updating database configurations</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 30 minutes

    Affected Components: [US] Awell Design, [US] Awell Platform - Web App, [US] Awell Operate
    May 5, 07:40:00 GMT+0 - Identified - We are performing a scheduled maintenance that will cause brief downtime as we refresh and further harden our databases. May 5, 10:15:54 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 30 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;07:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing a scheduled maintenance that will cause brief downtime as we refresh and further harden our databases..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:15:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 5 May 2026 07:40:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmosbmu1b007j9wfuc9ktpd1r</link>
  <guid>https://status.awellhealth.com/maintenance/cmosbmu1b007j9wfuc9ktpd1r</guid>
</item>

<item>
  <title>Updating our database configurations</title>
  <description>
    Type: Maintenance
    Duration: 4 days and 9 hours

    Affected Components: [EU] Awell Design, [UK] Awell Operate, [EU] Awell Manage, [EU] Awell Operate, [EU] Mirth, [UK] Awell Design, [UK] Awell Manage
    May 5, 02:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance that will cause brief downtime as we refresh and further harden our databases. May 5, 02:00:01 GMT+0 - Identified - Maintenance is now in progress May 5, 02:10:31 GMT+0 - Identified - Maintenance has completed successfully in EU May 5, 03:45:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 4 days and 9 hours</p>
    <p><strong>Affected Components:</strong> , , , , , , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance that will cause brief downtime as we refresh and further harden our databases..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:10:31&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance has completed successfully in EU.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 5 May 2026 02:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmorz5x3506ae11962rkaxhdh</link>
  <guid>https://status.awellhealth.com/maintenance/cmorz5x3506ae11962rkaxhdh</guid>
</item>

<item>
  <title>Intermittent Infrastructure Failures</title>
  <description>
    Type: Incident
    Duration: 37 minutes

    Affected Components: [US] Awell Operate
    May 4, 14:58:00 GMT+0 - Investigating - We experienced infrastructure issues impacting Orchestration activities for a subset of activities. Some users experienced degraded performance. May 4, 15:35:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 37 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:58:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We experienced infrastructure issues impacting Orchestration activities for a subset of activities. Some users experienced degraded performance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 4&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 4 May 2026 14:58:00 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmosx041x00tgfdax78i4q5bz</link>
  <guid>https://status.awellhealth.com/incident/cmosx041x00tgfdax78i4q5bz</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: [US] Awell Operate
    May 2, 12:49:54 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. May 2, 12:53:16 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:49:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:53:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 2 May 2026 12:49:54 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmooc9ypn08g9q021ooqi2ubj</link>
  <guid>https://status.awellhealth.com/incident/cmooc9ypn08g9q021ooqi2ubj</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 11 minutes

    Affected Components: [US] Awell Operate
    May 1, 12:49:54 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. May 1, 13:00:24 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:49:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 1&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:24&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 1 May 2026 12:49:53 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmomwu3io03dqmmx60xetm9ua</link>
  <guid>https://status.awellhealth.com/incident/cmomwu3io03dqmmx60xetm9ua</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: [US] Awell Operate
    Apr 29, 12:50:13 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Apr 29, 12:52:12 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:50:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:52:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 29 Apr 2026 12:50:13 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmok1ytec0cbsp47dl8b6ez5j</link>
  <guid>https://status.awellhealth.com/incident/cmok1ytec0cbsp47dl8b6ez5j</guid>
</item>

<item>
  <title>Intermittent Infrastructure Failures</title>
  <description>
    Type: Incident
    Duration: 36 minutes

    Affected Components: [US] Awell Operate
    Apr 28, 22:29:00 GMT+0 - Resolved - We experienced infrastructure issues impacting Awell Hosted Pages and initiating care flows via our API. Core orchestration remained operational, but some users experienced degraded performance. Starting care flows through incoming webhooks and bulk uploads were not impacted. The issue is resolved. Apr 28, 20:06:00 GMT+0 - Identified - Intermittent Redis restarts caused unreliable calls from Awell Hosted Pages and other non-core services. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 36 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:29:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We experienced infrastructure issues impacting Awell Hosted Pages and initiating care flows via our API. Core orchestration remained operational, but some users experienced degraded performance. Starting care flows through incoming webhooks and bulk uploads were not impacted. The issue is resolved..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:06:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Intermittent Redis restarts caused unreliable calls from Awell Hosted Pages and other non-core services..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 28 Apr 2026 20:06:00 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmoj3vb7403flz9uxlrfir6kv</link>
  <guid>https://status.awellhealth.com/incident/cmoj3vb7403flz9uxlrfir6kv</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: [US] Awell Operate
    Apr 26, 12:50:16 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Apr 26, 12:52:56 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:50:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:52:56&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 26 Apr 2026 12:50:16 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmofrnbod0nzf11w5mvtweabj</link>
  <guid>https://status.awellhealth.com/incident/cmofrnbod0nzf11w5mvtweabj</guid>
</item>

<item>
  <title>Infrastructure Failure</title>
  <description>
    Type: Incident
    Duration: 1 day, 11 hours and 56 minutes

    Affected Components: [US] Awell Operate
    Apr 25, 20:35:00 GMT+0 - Investigating - We are currently investigating an incident causing Orchestration activities to fail during creation and completion. Apr 27, 08:31:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 11 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 25&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:35:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident causing Orchestration activities to fail during creation and completion..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:31:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 25 Apr 2026 20:35:00 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmot1gkgs0174l0b2jzvy1lnj</link>
  <guid>https://status.awellhealth.com/incident/cmot1gkgs0174l0b2jzvy1lnj</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 4 minutes

    Affected Components: [US] Awell Operate
    Apr 24, 12:50:20 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Apr 24, 12:54:12 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:50:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:54:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 24 Apr 2026 12:50:20 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmocwrpeh003bvlz2wixzdqxm</link>
  <guid>https://status.awellhealth.com/incident/cmocwrpeh003bvlz2wixzdqxm</guid>
</item>

<item>
  <title>Brief service upgrade</title>
  <description>
    Type: Maintenance
    Duration: 15 minutes

    Affected Components: [US] Awell Design, [EU] Awell Design, [EU] Awell Manage, [EU] Awell Operate, [UK] Awell Operate, [EU] Mirth, [US] Awell Platform - Web App, [US] Awell Operate, [UK] Awell Design, [UK] Awell Manage
    Apr 20, 01:00:00 GMT+0 - Identified - We will perform a brief service upgrade across all environments, which will improve the throughput of our systems Apr 20, 01:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 20, 01:15:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 15 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will perform a brief service upgrade across all environments, which will improve the throughput of our systems.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;01:15:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 20 Apr 2026 01:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmo5qd4td038aqwicjqvnc6dp</link>
  <guid>https://status.awellhealth.com/maintenance/cmo5qd4td038aqwicjqvnc6dp</guid>
</item>

<item>
  <title>Scheduled Maintenance — Internal Messaging Infrastructure (US)</title>
  <description>
    Type: Maintenance
    Duration: 11 minutes

    Affected Components: [US] Awell Design, [US] Awell Platform - Web App, [US] Awell Operate
    Apr 19, 11:00:00 GMT+0 - Identified - ```markdown
We will be performing a scheduled upgrade of our internal messaging
infrastructure in the US region.

During this one-hour window, you may experience:

- A brief interruption (~30 seconds) where API requests may time out
- Delayed message processing for up to 5 minutes as services reconnect
- Temporary delays in real-time notifications and care flow progression

Active care flows will automatically resume. No data loss is expected.

The actual disruption is expected to be brief. The one-hour window provides
buffer if additional remediation is needed.
``` Apr 19, 11:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 19, 11:11:21 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  ```markdown
We will be performing a scheduled upgrade of our internal messaging
infrastructure in the US region.

During this one-hour window, you may experience:

- A brief interruption (~30 seconds) where API requests may time out
- Delayed message processing for up to 5 minutes as services reconnect
- Temporary delays in real-time notifications and care flow progression

Active care flows will automatically resume. No data loss is expected.

The actual disruption is expected to be brief. The one-hour window provides
buffer if additional remediation is needed.
```.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 19&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:11:21&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sun, 19 Apr 2026 11:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmo4m11990h80113v67bygs9z</link>
  <guid>https://status.awellhealth.com/maintenance/cmo4m11990h80113v67bygs9z</guid>
</item>

<item>
  <title>Scheduled Maintenance — Internal Messaging Infrastructure (EU &amp; UK)</title>
  <description>
    Type: Maintenance
    Duration: 22 minutes

    Affected Components: [US] Awell Design, [Sandbox] Awell Design, [EU] Awell Design, [EU] Awell Manage, [EU] Awell Operate, [UK] Awell Operate, [EU] Mirth, [US] Awell Platform - Web App, [US] Awell Operate, [Sandbox] Awell Manage, [UK] Awell Design, [UK] Awell Manage, [Sandbox] Awell Operate
    Apr 18, 22:00:00 GMT+0 - Identified - ```markdown
We will be performing scheduled upgrades of our internal messaging
infrastructure in the EU and UK regions.

During this one-hour window, you may experience:

- A brief interruption (~30 seconds per region) where API requests may time out
- Delayed message processing for up to 5 minutes per region as services reconnect
- Temporary delays in real-time notifications and care flow progression

Active care flows will automatically resume. No data loss is expected.

The actual disruption in each region is expected to be brief. The one-hour
window provides buffer if additional remediation is needed. We will post
updates as each region completes.
``` Apr 18, 22:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 18, 22:14:34 GMT+0 - Identified - UK maintenance is complete. Apr 18, 22:21:37 GMT+0 - Completed - Maintenance in EU is complete. All maintenance has been completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 22 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  ```markdown
We will be performing scheduled upgrades of our internal messaging
infrastructure in the EU and UK regions.

During this one-hour window, you may experience:

- A brief interruption (~30 seconds per region) where API requests may time out
- Delayed message processing for up to 5 minutes per region as services reconnect
- Temporary delays in real-time notifications and care flow progression

Active care flows will automatically resume. No data loss is expected.

The actual disruption in each region is expected to be brief. The one-hour
window provides buffer if additional remediation is needed. We will post
updates as each region completes.
```.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:14:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  UK maintenance is complete..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 18&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;22:21:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance in EU is complete. All maintenance has been completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 18 Apr 2026 22:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmo4lzkh60h7m113vxddgwcby</link>
  <guid>https://status.awellhealth.com/maintenance/cmo4lzkh60h7m113vxddgwcby</guid>
</item>

<item>
  <title>Infrastructure Failure</title>
  <description>
    Type: Incident
    Duration: 4 hours and 55 minutes

    Affected Components: [US] Awell Operate
    Apr 14, 09:05:00 GMT+0 - Investigating - We are currently investigating an incident causing Orchestration activities to fail. Apr 14, 14:00:00 GMT+0 - Resolved - This incident has been resolved. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:05:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  We are currently investigating an incident causing Orchestration activities to fail..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  This incident has been resolved..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 14 Apr 2026 09:05:00 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmosydmh40083ob8mecgbhkdo</link>
  <guid>https://status.awellhealth.com/incident/cmosydmh40083ob8mecgbhkdo</guid>
</item>

<item>
  <title>[UK] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 11 minutes

    Affected Components: [UK] Awell Operate
    Mar 10, 06:22:02 GMT+0 - Investigating - \[UK\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Mar 10, 06:32:54 GMT+0 - Resolved - \[UK\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:22:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[UK\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Mar &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:32:54&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[UK\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 10 Mar 2026 06:22:02 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmmk830jw07ovedsgpg00kswa</link>
  <guid>https://status.awellhealth.com/incident/cmmk830jw07ovedsgpg00kswa</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 3 minutes

    Affected Components: [US] Awell Operate
    Feb 3, 14:17:29 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Feb 3, 14:20:51 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:20:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 3 Feb 2026 14:17:29 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cml6onmw2072fh0phlwawt962</link>
  <guid>https://status.awellhealth.com/incident/cml6onmw2072fh0phlwawt962</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 5 minutes

    Affected Components: [US] Awell Operate
    Feb 2, 14:47:20 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Feb 2, 14:52:45 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:47:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:52:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Feb 2026 14:47:20 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cml5aa66i02g9gdavhkextcz9</link>
  <guid>https://status.awellhealth.com/incident/cml5aa66i02g9gdavhkextcz9</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 9 minutes

    Affected Components: [US] Awell Operate
    Feb 2, 14:17:34 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Feb 2, 14:26:44 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:34&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Feb &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:26:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 2 Feb 2026 14:17:34 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cml597vkl04hz1m5096qupqyb</link>
  <guid>https://status.awellhealth.com/incident/cml597vkl04hz1m5096qupqyb</guid>
</item>

<item>
  <title>Database cluster version upgrade</title>
  <description>
    Type: Maintenance
    Duration: 2 hours

    Affected Components: , [Sandbox] Awell Design, [Sandbox] Awell Manage, [Sandbox] Awell Operate, 
Sandbox →
    Jan 30, 08:30:00 GMT+0 - Identified - We are upgrading our database cluster to the latest version. This will be done as a zero downtime operation. Jan 30, 08:30:01 GMT+0 - Identified - Maintenance is now in progress Jan 30, 10:30:00 GMT+0 - Completed - Maintenance has completed successfully 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are upgrading our database cluster to the latest version. This will be done as a zero downtime operation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 30 Jan 2026 08:30:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cml0md6e80fc6vibrntkl0ict</link>
  <guid>https://status.awellhealth.com/maintenance/cml0md6e80fc6vibrntkl0ict</guid>
</item>

<item>
  <title>[Sandbox] Database outage</title>
  <description>
    Type: Incident
    Duration: 1 hour and 20 minutes

    Affected Components: , [Sandbox] Awell Design, [Sandbox] Awell Manage, [Sandbox] Awell Operate, 
Sandbox →
    Jan 29, 12:20:00 GMT+0 - Investigating - One of the servers in our database cluster went down unexpectedly and is not able to start back up. We are investigating how to get it back up and running as soon as possible. Jan 29, 13:40:00 GMT+0 - Resolved - We have found the right procedure to restart the database server. The database cluster is now back in a healthy state. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 20 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;12:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  One of the servers in our database cluster went down unexpectedly and is not able to start back up. We are investigating how to get it back up and running as soon as possible..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 29&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:40:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  We have found the right procedure to restart the database server. The database cluster is now back in a healthy state..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 29 Jan 2026 12:20:00 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkzj2no2000ie77zzvcyhy3n</link>
  <guid>https://status.awellhealth.com/incident/cmkzj2no2000ie77zzvcyhy3n</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: [US] Awell Operate
    Jan 28, 14:17:46 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 28, 14:20:00 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 28&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 28 Jan 2026 14:17:46 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmky40vwc023o13vdggn4lm3n</link>
  <guid>https://status.awellhealth.com/incident/cmky40vwc023o13vdggn4lm3n</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: [US] Awell Operate
    Jan 27, 14:17:49 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 27, 14:19:45 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:49&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:19:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 27 Jan 2026 14:17:49 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkwol3jd0005rldhaodi27t9</link>
  <guid>https://status.awellhealth.com/incident/cmkwol3jd0005rldhaodi27t9</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 36 minutes

    Affected Components: [US] Awell Operate
    Jan 26, 14:17:53 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 26, 14:53:42 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 36 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:53&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:53:42&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 26 Jan 2026 14:17:53 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkv95bjb01ejm8ksis6dxjky</link>
  <guid>https://status.awellhealth.com/incident/cmkv95bjb01ejm8ksis6dxjky</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 29 minutes

    Affected Components: [US] Awell Operate
    Jan 24, 00:20:39 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 24, 00:49:16 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:20:39&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:49:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 24 Jan 2026 00:20:39 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkrkcxej0nzl109y7s29d400</link>
  <guid>https://status.awellhealth.com/incident/cmkrkcxej0nzl109y7s29d400</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 12 minutes

    Affected Components: [US] Awell Operate
    Jan 23, 23:48:18 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 24, 00:00:17 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 23&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;23:48:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 24&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;00:00:17&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 23 Jan 2026 23:48:18 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkrj7bxe0ngq109ymu5360mi</link>
  <guid>https://status.awellhealth.com/incident/cmkrj7bxe0ngq109ymu5360mi</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 2 minutes

    Affected Components: [US] Awell Operate
    Jan 22, 16:35:02 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 22, 16:36:55 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:35:02&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:36:55&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 22 Jan 2026 16:35:02 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkpoaajf002alxk76eo782ze</link>
  <guid>https://status.awellhealth.com/incident/cmkpoaajf002alxk76eo782ze</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 42 minutes

    Affected Components: [US] Awell Operate
    Jan 20, 14:17:13 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 20, 14:59:14 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:17:13&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:59:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 20 Jan 2026 14:17:13 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkmohd2l0d9petvcqm0app4s</link>
  <guid>https://status.awellhealth.com/incident/cmkmohd2l0d9petvcqm0app4s</guid>
</item>

<item>
  <title>[EU] Orchestration API Experiencing Issues</title>
  <description>
    Type: Incident
    Duration: 13 minutes

    Affected Components: [EU] Awell Operate
    Jan 20, 08:06:41 GMT+0 - Investigating - \[EU\] We&#039;ve detected that the Orchestration API is currently experiencing availability issues. Our engineering team has been automatically notified and is monitoring the situation.

If the service doesn&#039;t recover automatically, we&#039;ll investigate to identify and resolve the root cause. This incident was created automatically by our monitoring system. Jan 20, 08:19:37 GMT+0 - Resolved - \[EU\] The Orchestration API has automatically recovered and is now functioning normally. Our monitoring system has verified that all services are operating as expected.

This incident has been automatically resolved. We apologize for any inconvenience and thank you for your patience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:06:41&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[EU\] We&#039;ve detected that the Orchestration API is currently experiencing availability issues. Our engineering team has been automatically notified and is monitoring the situation.

If the service doesn&#039;t recover automatically, we&#039;ll investigate to identify and resolve the root cause. This incident was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 20&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:19:37&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[EU\] The Orchestration API has automatically recovered and is now functioning normally. Our monitoring system has verified that all services are operating as expected.

This incident has been automatically resolved. We apologize for any inconvenience and thank you for your patience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 20 Jan 2026 08:06:41 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkmb8uia000bu4jd0oau1k74</link>
  <guid>https://status.awellhealth.com/incident/cmkmb8uia000bu4jd0oau1k74</guid>
</item>

<item>
  <title>[US] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 5 minutes

    Affected Components: [US] Awell Operate
    Jan 17, 14:24:16 GMT+0 - Investigating - \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 17, 14:29:43 GMT+0 - Resolved - \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:24:16&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[US\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 17&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:29:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[US\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Sat, 17 Jan 2026 14:24:16 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkieev5a09pmir8p4adc20an</link>
  <guid>https://status.awellhealth.com/incident/cmkieev5a09pmir8p4adc20an</guid>
</item>

<item>
  <title>[Sandbox] Orchestration Platform Experiencing Degraded Performance</title>
  <description>
    Type: Incident
    Duration: 52 minutes

    Affected Components: [Sandbox] Awell Operate
    Jan 15, 13:22:44 GMT+0 - Investigating - \[Sandbox\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system. Jan 15, 14:14:46 GMT+0 - Resolved - \[Sandbox\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 52 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:22:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Investigating&lt;/strong&gt; -
  \[Sandbox\] We&#039;re currently observing higher than normal latency in the Orchestration Platform. This is likely due to temporary high load. Our engineering team has been automatically notified and is monitoring the situation.

The performance degradation is likely limited to specific care flows experiencing high load, but it could have a knock-on effect on other care flows if the situation is sustained. The system remains operational, though you may experience delays. If performance doesn&#039;t improve shortly, we&#039;ll take additional actions to reduce the impact of this temporary load.

This notice was created automatically by our monitoring system..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;14:14:46&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Resolved&lt;/strong&gt; -
  \[Sandbox\] The Orchestration Platform performance has returned to normal levels. Our monitoring system has confirmed that response times are back within expected ranges.

The temporary performance degradation has been automatically resolved. Thank you for your understanding during this period of increased system load..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 15 Jan 2026 13:22:44 +0000</pubDate>
  <link>https://status.awellhealth.com/incident/cmkfhc1f605gl1435fwmwwpyo</link>
  <guid>https://status.awellhealth.com/incident/cmkfhc1f605gl1435fwmwwpyo</guid>
</item>

<item>
  <title>[US environment] Increase datastore resilience</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: [US] Awell Operate
    May 14, 09:30:00 GMT+0 - Completed - Maintenance has completed successfully May 14, 08:30:01 GMT+0 - Identified - Maintenance is now in progress May 14, 08:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance to further improve our orchestration data store resilience. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance to further improve our orchestration data store resilience..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 14 May 2025 08:30:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmacazea9004p2aoe4359vr6c</link>
  <guid>https://status.awellhealth.com/maintenance/cmacazea9004p2aoe4359vr6c</guid>
</item>

<item>
  <title>[UK and EU environments] Increase datastore resilience</title>
  <description>
    Type: Maintenance
    Duration: 1 hour and 17 minutes

    Affected Components: [UK] Awell Operate, [EU] Awell Operate
    May 14, 05:46:44 GMT+0 - Completed - Maintenance has completed successfully. May 14, 04:30:01 GMT+0 - Identified - Maintenance is now in progress May 14, 04:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance to further improve our orchestration data store resilience. May 14, 04:46:43 GMT+0 - Identified - We are observing degraded performance on orchestration as a result of the maintenance we are performing - that is expected and should be automatically solved until the end of the maintenance. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 17 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:46:44&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for a scheduled maintenance to further improve our orchestration data store resilience..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;May &lt;var data-var=&#039;date&#039;&gt; 14&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:46:43&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are observing degraded performance on orchestration as a result of the maintenance we are performing - that is expected and should be automatically solved until the end of the maintenance..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 14 May 2025 04:30:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cmac9na7f000b2aoenxog2jnt</link>
  <guid>https://status.awellhealth.com/maintenance/cmac9na7f000b2aoenxog2jnt</guid>
</item>

<item>
  <title>[ALL ENVIRONMENTS] - Retool Scheduled Downtime</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Third Party: Retool → Infrastructure, Third Party: Retool → Web Application and APIs, Third Party: Retool → Source Control, Third Party: Retool → Resource Queries
    Sep 5, 20:00:00 GMT+0 - Completed - Maintenance has completed successfully Sep 5, 19:00:00 GMT+0 - Identified - We are planning for scheduled maintenance during that time to facilitate upgrading Retool. Retool application cannot be used during this time and dashboards should not be edited. Sep 5, 19:00:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;20:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning for scheduled maintenance during that time to facilitate upgrading Retool. Retool application cannot be used during this time and dashboards should not be edited..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Sep &lt;var data-var=&#039;date&#039;&gt; 5&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;19:00:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 5 Sep 2024 19:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cm0pmbd5y000110izf5t0uhqy</link>
  <guid>https://status.awellhealth.com/maintenance/cm0pmbd5y000110izf5t0uhqy</guid>
</item>

<item>
  <title>Infrastructure security and stability improvements</title>
  <description>
    Type: Maintenance
    Duration: 9 minutes

    Affected Components: [US] Awell Design, [US] Awell Operate, [US] Awell Platform - Web App
    Jul 3, 08:45:00 GMT+0 - Identified - We are performing planned maintenance to improve infrastructure security and stability. We don&#039;t expect any downtime, but we do expect small periods of time with degraded performance. Jul 3, 09:01:18 GMT+0 - Completed - Maintenance operations have been successfully completed with no impact on system uptime, ensuring enhanced stability and security. Jul 3, 08:52:47 GMT+0 - Identified - Maintenance is now in progress. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:45:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing planned maintenance to improve infrastructure security and stability. We don&#039;t expect any downtime, but we do expect small periods of time with degraded performance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;09:01:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance operations have been successfully completed with no impact on system uptime, ensuring enhanced stability and security..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;08:52:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jul 2024 08:45:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cly4o8ojt94545hbn4aumznefz</link>
  <guid>https://status.awellhealth.com/maintenance/cly4o8ojt94545hbn4aumznefz</guid>
</item>

<item>
  <title>Infrastructure security and stability improvements</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 12 minutes

    Affected Components: [Sandbox] Awell Operate, [EU] Awell Design, [EU] Awell Operate, [UK] Awell Operate, [EU] Awell Manage, [UK] Awell Manage, [Sandbox] Awell Manage, [Sandbox] Awell Design, [UK] Awell Design
    Jul 3, 05:32:05 GMT+0 - Identified - Both Production EU and Production UK are finished and shouldn&#039;t experience any downgraded performance.   
  
Sandbox is still ongoing. Jul 3, 04:30:00 GMT+0 - Identified - We are performing planned maintenance to improve infrastructure security and stability. We don&#039;t expect any downtime, but we do expect small periods of time with degraded performance. Jul 3, 06:42:14 GMT+0 - Completed - Maintenance operations have been successfully completed with no impact on system uptime, ensuring enhanced stability and security. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 12 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;05:32:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Both Production EU and Production UK are finished and shouldn&#039;t experience any downgraded performance.   
  
Sandbox is still ongoing..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;04:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are performing planned maintenance to improve infrastructure security and stability. We don&#039;t expect any downtime, but we do expect small periods of time with degraded performance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jul &lt;var data-var=&#039;date&#039;&gt; 3&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;06:42:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance operations have been successfully completed with no impact on system uptime, ensuring enhanced stability and security..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jul 2024 04:30:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/cly4o6emr95093g6n470lsa57m</link>
  <guid>https://status.awellhealth.com/maintenance/cly4o6emr95093g6n470lsa57m</guid>
</item>

<item>
  <title>Maintenance on API proxy</title>
  <description>
    Type: Maintenance
    Duration: 21 minutes

    Affected Components: [Sandbox] Awell Operate, [EU] Awell Operate, [UK] Awell Operate, [US] Awell Operate
    Jan 16, 10:28:12 GMT+0 - Identified - We are updating the deployment configuration of the API proxy to improve its Quality-of-Service class and make it guaranteed. There is no expected impact on the availability of the orchestration API during the maintenance. Jan 16, 10:49:09 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 21 minutes</p>
    <p><strong>Affected Components:</strong> , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:28:12&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are updating the deployment configuration of the API proxy to improve its Quality-of-Service class and make it guaranteed. There is no expected impact on the availability of the orchestration API during the maintenance..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 16&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:49:09&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 16 Jan 2024 10:28:12 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clrg7qrc863164den9wi85kj22</link>
  <guid>https://status.awellhealth.com/maintenance/clrg7qrc863164den9wi85kj22</guid>
</item>

<item>
  <title>[Sandbox] Maintenance on metrics collection platform</title>
  <description>
    Type: Maintenance
    Duration: 1 day, 2 hours and 55 minutes

    Affected Components: [EU] Awell Design, [EU] Awell Operate, [UK] Awell Operate, [US] Awell Design, [US] Awell Operate, [UK] Awell Design
    Jan 15, 11:00:00 GMT+0 - Completed - The maintenance has been successfully executed in all environments. Jan 15, 10:11:05 GMT+0 - Identified - We are planning a migration to the managed prometheus metrics collection feature. While this requires a change to the kubernetes cluster configuration we expect no availability or performances impact while the maintenance is ongoing.

We will perform the maintenance in the Sandbox environment first, then apply it in all production environments when confirmed that availability and performances are not impacted. Jan 15, 10:38:00 GMT+0 - Completed - Sandbox environment has been updated. No impact on availability or performances detected. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 day, 2 hours and 55 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The maintenance has been successfully executed in all environments..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:11:05&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We are planning a migration to the managed prometheus metrics collection feature. While this requires a change to the kubernetes cluster configuration we expect no availability or performances impact while the maintenance is ongoing.

We will perform the maintenance in the Sandbox environment first, then apply it in all production environments when confirmed that availability and performances are not impacted..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 15&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Sandbox environment has been updated. No impact on availability or performances detected..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Mon, 15 Jan 2024 10:11:05 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clrerru5t422212bkn5z5i2f3qw</link>
  <guid>https://status.awellhealth.com/maintenance/clrerru5t422212bkn5z5i2f3qw</guid>
</item>

<item>
  <title>Brief maintenance for system upgrade</title>
  <description>
    Type: Maintenance
    Duration: 13 minutes

    Affected Components: [US] Awell Design, [US] Awell Operate, [US] Awell Platform - Web App
    Jan 2, 10:30:20 GMT+0 - Identified - Maintenance is now in progress. Jan 2, 10:42:45 GMT+0 - Completed - Maintenance has completed successfully. Jan 2, 10:30:00 GMT+0 - Identified - We&#039;ll be applying a patch upgrade to our database and some intermittent downtime is expected during the upgrade. Jan 2, 10:30:01 GMT+0 - Identified - Maintenance is now in progress 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 13 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:30:20&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:42:45&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:30:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ll be applying a patch upgrade to our database and some intermittent downtime is expected during the upgrade..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:30:01&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Maintenance is now in progress.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 2 Jan 2024 10:30:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clqw7akp535770ben8d8e5qu5q</link>
  <guid>https://status.awellhealth.com/maintenance/clqw7akp535770ben8d8e5qu5q</guid>
</item>

<item>
  <title>Brief maintenance for system upgrade</title>
  <description>
    Type: Maintenance
    Duration: 29 minutes

    Affected Components: [Sandbox] Awell Design, [Sandbox] Awell Operate, [EU] Awell Design, [UK] Awell Design, [EU] Awell Operate, [UK] Awell Operate, [EU] Awell Manage, [UK] Awell Manage, [Sandbox] Awell Manage
    Jan 2, 03:30:23 GMT+0 - Identified - UK upgrade was completed successfully.

Moving on to EU Jan 2, 03:41:57 GMT+0 - Completed - Maintenance has completed successfully. Jan 2, 03:00:00 GMT+0 - Identified - We&#039;ll be applying a patch upgrade to our database and some intermittent downtime is expected during the upgrade. Jan 2, 03:13:00 GMT+0 - Identified - Sandbox migration was successful. Jan 2, 03:18:48 GMT+0 - Identified - Proceeding with UK server 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 29 minutes</p>
    <p><strong>Affected Components:</strong> , , , , , , , , </p>
    &lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:30:23&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  UK upgrade was completed successfully.

Moving on to EU.&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:41:57&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;ll be applying a patch upgrade to our database and some intermittent downtime is expected during the upgrade..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:13:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Sandbox migration was successful..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Jan &lt;var data-var=&#039;date&#039;&gt; 2&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;03:18:48&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  Proceeding with UK server.&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 2 Jan 2024 03:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clqr6lov471990bin5ti029ufk</link>
  <guid>https://status.awellhealth.com/maintenance/clqr6lov471990bin5ti029ufk</guid>
</item>

<item>
  <title>[Production EU] Explicit resource allocation for primary application DB and message broker</title>
  <description>
    Type: Maintenance
    Duration: 3 minutes

    Affected Components: [EU] Awell Design, [EU] Awell Operate, [EU] Awell Manage
    Dec 26, 11:40:59 GMT+0 - Identified - We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed. Dec 26, 11:44:38 GMT+0 - Identified - The DB cluster is restarting with the updated configuration. Dec 26, 11:47:51 GMT+0 - Completed - The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:40:59&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:44:38&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The DB cluster is restarting with the updated configuration..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:47:51&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 Dec 2023 11:40:59 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clqma1gr0221864bpn5dbu6rwsi</link>
  <guid>https://status.awellhealth.com/maintenance/clqma1gr0221864bpn5dbu6rwsi</guid>
</item>

<item>
  <title>[Production UK] Explicit resource allocation for primary application DB and message broker</title>
  <description>
    Type: Maintenance
    Duration: 2 minutes

    Affected Components: [UK] Awell Design, [UK] Awell Operate
    Dec 26, 11:34:04 GMT+0 - Identified - We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed. Dec 26, 11:39:10 GMT+0 - Completed - The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation. Dec 26, 11:36:47 GMT+0 - Identified - The DB cluster and message brokers are restarting with the updated configuration. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:34:04&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:39:10&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:36:47&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The DB cluster and message brokers are restarting with the updated configuration..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 Dec 2023 11:34:04 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clqm9skhz218593bpn5ep7sygxm</link>
  <guid>https://status.awellhealth.com/maintenance/clqm9skhz218593bpn5ep7sygxm</guid>
</item>

<item>
  <title>[Production US] Explicit resource allocation for primary application DB and message broker</title>
  <description>
    Type: Maintenance
    Duration: 7 minutes

    Affected Components: [US] Awell Design, [US] Awell Operate, [US] Awell Platform - Web App
    Dec 26, 11:31:18 GMT+0 - Completed - The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation. Dec 26, 11:24:22 GMT+0 - Identified - The DB cluster and message brokers are restarting with the updated configuration. Dec 26, 11:20:00 GMT+0 - Identified - We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:31:18&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:24:22&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The DB cluster and message brokers are restarting with the updated configuration..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:20:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 Dec 2023 11:24:22 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clqm9gih0206169bin50hs0quf6</link>
  <guid>https://status.awellhealth.com/maintenance/clqm9gih0206169bin50hs0quf6</guid>
</item>

<item>
  <title>[Sandbox] Explicit resource allocation for primary application DB and message broker</title>
  <description>
    Type: Maintenance
    Duration: 5 minutes

    Affected Components: [Sandbox] Awell Design, [Sandbox] Awell Operate, [Sandbox] Awell Manage
    Dec 26, 11:15:14 GMT+0 - Identified - The DB cluster is restarting with the updated configuration. Dec 26, 11:20:29 GMT+0 - Completed - The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation. Dec 26, 11:00:00 GMT+0 - Identified - We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 5 minutes</p>
    <p><strong>Affected Components:</strong> , , </p>
    &lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:15:14&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The DB cluster is restarting with the updated configuration..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:20:29&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The database cluster and message broker are back up. No incident or service degradation were detected during the maintenance operation..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Dec &lt;var data-var=&#039;date&#039;&gt; 26&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We&#039;re updating the k8s manifests of the primary application database and message broker to include explicit resource requests and limits. This will improve the stability of our platform as k8s will be able to make better scheduling decisions.

This maintenance operation is not expected to cause any downtime. Care flow orchestration will be briefly paused as the database and the message broker restart, then will resume automatically once the update is completed..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Tue, 26 Dec 2023 11:00:00 +0000</pubDate>
  <link>https://status.awellhealth.com/maintenance/clqm8v2v5187617bin53802v8hb</link>
  <guid>https://status.awellhealth.com/maintenance/clqm8v2v5187617bin53802v8hb</guid>
</item>

  </channel>
  </rss>