<?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>KABI Automotive Status - Incident history</title>
    <link>https://status.kabillc.com</link>
    <description>KABI Automotive</description>
    <pubDate>Mon, 20 Oct 2025 18:12:06 +0000</pubDate>
    
<item>
  <title>Widespread AWS outage is causing service interruption</title>
  <description>
    Type: Incident
    Duration: 5 hours and 42 minutes

    Affected Components: WorksTiming, ShopLoader
    Oct 20, 23:53:45 GMT+0 - Resolved - All upstream services providers impacted by the AWS outage affecting our systems have recovered and are operating as intended. This incident has been resolved. Oct 20, 21:44:08 GMT+0 - Monitoring - Upstream providers are reporting improvements but have not yet given the all clear.

We are continuing to monitor. Oct 20, 18:12:06 GMT+0 - Monitoring - Service disruption on Amazon Web Services is causing widespread internet outages and service disruptions.

ShopLoader and WorksTiming are up and running despite the interruptions.

However, we have observed some delivery failure for SMS messages to customers including appointment reminders and confirmations. Most messages are still being delivered, however a small percentage have failed.

We are continuing to monitor and will update when we have additional information. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours and 42 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>23:53:45</var> GMT+0</small><br><strong>Resolved</strong> -
  All upstream services providers impacted by the AWS outage affecting our systems have recovered and are operating as intended. This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>21:44:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  Upstream providers are reporting improvements but have not yet given the all clear.

We are continuing to monitor..</p>
<p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>18:12:06</var> GMT+0</small><br><strong>Monitoring</strong> -
  Service disruption on Amazon Web Services is causing widespread internet outages and service disruptions.

ShopLoader and WorksTiming are up and running despite the interruptions.

However, we have observed some delivery failure for SMS messages to customers including appointment reminders and confirmations. Most messages are still being delivered, however a small percentage have failed.

We are continuing to monitor and will update when we have additional information..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 20 Oct 2025 18:12:06 +0000</pubDate>
  <link>https://status.kabillc.com/incident/cmgzgd23q03hg2ycy4e6wscz3</link>
  <guid>https://status.kabillc.com/incident/cmgzgd23q03hg2ycy4e6wscz3</guid>
</item>

<item>
  <title>ShopLoader is Unresponsive</title>
  <description>
    Type: Incident
    Duration: 32 minutes

    Affected Components: ShopLoader
    Mar 7, 15:17:42 GMT+0 - Resolved - This incident has been resolved.  We are seeing response rates and speeds have returned to normal operating range.  Please reach out if you are still having trouble reaching ShopLoader. Mar 7, 15:10:17 GMT+0 - Monitoring - We corrected instances where ShopLoader servers failed to start up for their scheduled morning service.

ShopLoader should be accessible again to all users.  We are continuing to monitor for all clear.

 Mar 7, 14:45:38 GMT+0 - Investigating - ShopLoader is unresponsive. We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>15:17:42</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved.  We are seeing response rates and speeds have returned to normal operating range.  Please reach out if you are still having trouble reaching ShopLoader..</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>15:10:17</var> GMT+0</small><br><strong>Monitoring</strong> -
  We corrected instances where ShopLoader servers failed to start up for their scheduled morning service.

ShopLoader should be accessible again to all users.  We are continuing to monitor for all clear.

.</p>
<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>14:45:38</var> GMT+0</small><br><strong>Investigating</strong> -
  ShopLoader is unresponsive. We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 7 Mar 2023 14:45:38 +0000</pubDate>
  <link>https://status.kabillc.com/incident/cleyd5h77177008hjojyt6mavcf</link>
  <guid>https://status.kabillc.com/incident/cleyd5h77177008hjojyt6mavcf</guid>
</item>

<item>
  <title>ShopLoader is not accessible</title>
  <description>
    Type: Incident
    Duration: 28 minutes

    Affected Components: ShopLoader
    Feb 26, 17:36:00 GMT+0 - Resolved - This incident has been resolved. Feb 26, 17:31:48 GMT+0 - Monitoring - ShopLoader application instances returned to service. We are monitoring for additional impact. Feb 26, 17:16:26 GMT+0 - Identified - An error in configuration let all ShopLoader application instances apply system updates simultaneously. We are working to restore service as soon as possible. Feb 26, 17:08:00 GMT+0 - Investigating - We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>17:36:00</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>17:31:48</var> GMT+0</small><br><strong>Monitoring</strong> -
  ShopLoader application instances returned to service. We are monitoring for additional impact..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>17:16:26</var> GMT+0</small><br><strong>Identified</strong> -
  An error in configuration let all ShopLoader application instances apply system updates simultaneously. We are working to restore service as soon as possible..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>17:08:00</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 26 Feb 2023 17:08:00 +0000</pubDate>
  <link>https://status.kabillc.com/incident/clelnh2l2343740taotk1alt7it</link>
  <guid>https://status.kabillc.com/incident/clelnh2l2343740taotk1alt7it</guid>
</item>

<item>
  <title>WorksTiming is slow or unresponsive</title>
  <description>
    Type: Incident
    Duration: 32 minutes

    Affected Components: WorksTiming
    Nov 8, 23:17:00 GMT+0 - Resolved - Response times have returned to normal levels and the application is loading normally again. The database became slow due to an abnormal amount of traffic to the advisor dashboard page. We identified an improvement to ensure the database can handle the load during spikes to this page. Nov 8, 22:45:00 GMT+0 - Investigating - WorksTiming is currently unresponsive or very slow to load. We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 32 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>23:17:00</var> GMT+0</small><br><strong>Resolved</strong> -
  Response times have returned to normal levels and the application is loading normally again. The database became slow due to an abnormal amount of traffic to the advisor dashboard page. We identified an improvement to ensure the database can handle the load during spikes to this page..</p>
<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>22:45:00</var> GMT+0</small><br><strong>Investigating</strong> -
  WorksTiming is currently unresponsive or very slow to load. We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 8 Nov 2022 22:45:00 +0000</pubDate>
  <link>https://status.kabillc.com/incident/clacwwm7v1815j8ll1plpm70g</link>
  <guid>https://status.kabillc.com/incident/clacwwm7v1815j8ll1plpm70g</guid>
</item>

<item>
  <title>Slow or failed page loads</title>
  <description>
    Type: Incident
    Duration: 5 hours

    Affected Components: ShopLoader
    Sep 19, 14:16:00 GMT+0 - Resolved - The issue was resolved when a code deploy was completed and the system returned to 100% availability.  The deploy was necessary to fix a bug which effected a small number of appointment updates to DMS systems. Sep 19, 14:11:00 GMT+0 - Identified - For approximately five minutes beginning at 7:11 am PDT, ShopLoader users experienced degraded performance which resulted in longer than usual page load time and in some cases, failed page loads. We observed 90 total requests that failed completely. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>14:16:00</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue was resolved when a code deploy was completed and the system returned to 100% availability.  The deploy was necessary to fix a bug which effected a small number of appointment updates to DMS systems..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>14:11:00</var> GMT+0</small><br><strong>Identified</strong> -
  For approximately five minutes beginning at 7:11 am PDT, ShopLoader users experienced degraded performance which resulted in longer than usual page load time and in some cases, failed page loads. We observed 90 total requests that failed completely..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 19 Sep 2022 14:11:00 +0000</pubDate>
  <link>https://status.kabillc.com/incident/cl8900kdd18990hbln4axylinf</link>
  <guid>https://status.kabillc.com/incident/cl8900kdd18990hbln4axylinf</guid>
</item>

<item>
  <title>ShopLoader briefly unavailable</title>
  <description>
    Type: Incident
    Duration: 4 hours

    Affected Components: ShopLoader
    Aug 31, 01:07:00 GMT+0 - Resolved - After updates were completed the service returned to normal operation. No other impact was observed. Aug 31, 01:03:00 GMT+0 - Identified - ShopLoader experienced a brief period of unavailability (approx. 4 minutes) while undergoing an update to its server configuration. A thorough restart was necessary for updates to be applied.  
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>01:07:00</var> GMT+0</small><br><strong>Resolved</strong> -
  After updates were completed the service returned to normal operation. No other impact was observed..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>01:03:00</var> GMT+0</small><br><strong>Identified</strong> -
  ShopLoader experienced a brief period of unavailability (approx. 4 minutes) while undergoing an update to its server configuration. A thorough restart was necessary for updates to be applied. .</p>
]]>
  </content:encoded>
  <pubDate>Wed, 31 Aug 2022 01:07:00 +0000</pubDate>
  <link>https://status.kabillc.com/incident/cl7gxg2pi41061kpoit7rpfq99</link>
  <guid>https://status.kabillc.com/incident/cl7gxg2pi41061kpoit7rpfq99</guid>
</item>

<item>
  <title>ShopLoader not accessible</title>
  <description>
    Type: Incident
    Duration: 2 days, 6 hours and 48 minutes

    Affected Components: ShopLoader
    Aug 28, 05:27:47 GMT+0 - Resolved - Regular service has been restored and we are not observing any additional impact. Aug 28, 05:14:25 GMT+0 - Monitoring - Service was restored after the database upgrade completed and we restarted the application servers. We are monitoring for additional impact. Aug 28, 04:49:12 GMT+0 - Identified - ShopLoader primary database became unavailable when an automated update was applied by our database vendor. The upgrade was applied during the scheduled maintenance period, however was not anticipated as it was not reported prior to the upgrade taking place. We&#039;re working with our vendor for more information. Aug 28, 04:33:00 GMT+0 - Investigating - ShopLoader is currently not accessible.  This includes the internal scheduling dashboard as well as customer online appointment portals.

We are currently investigating this incident. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 6 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>05:27:47</var> GMT+0</small><br><strong>Resolved</strong> -
  Regular service has been restored and we are not observing any additional impact..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>05:14:25</var> GMT+0</small><br><strong>Monitoring</strong> -
  Service was restored after the database upgrade completed and we restarted the application servers. We are monitoring for additional impact..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>04:49:12</var> GMT+0</small><br><strong>Identified</strong> -
  ShopLoader primary database became unavailable when an automated update was applied by our database vendor. The upgrade was applied during the scheduled maintenance period, however was not anticipated as it was not reported prior to the upgrade taking place. We&#039;re working with our vendor for more information..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>04:33:00</var> GMT+0</small><br><strong>Investigating</strong> -
  ShopLoader is currently not accessible.  This includes the internal scheduling dashboard as well as customer online appointment portals.

We are currently investigating this incident..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 28 Aug 2022 04:33:00 +0000</pubDate>
  <link>https://status.kabillc.com/incident/cl7cuqrfr7650j8ofrnes1tpz</link>
  <guid>https://status.kabillc.com/incident/cl7cuqrfr7650j8ofrnes1tpz</guid>
</item>

<item>
  <title>Database connectivity issues and failover </title>
  <description>
    Type: Incident
    Duration: -5 hours

    Affected Components: ShopLoader
    May 8, 04:23:00 GMT+0 - Resolved - An elevated number of background data fetches put unexpected load on the database sufficient to require failover. 

Failover was automatic and completed within a few minutes. 

We observed approximately 66 requests which failed due to timeout due to being unable to contact the database.   
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> -5 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 8</var>, <var data-var='time'>04:23:00</var> GMT+0</small><br><strong>Resolved</strong> -
  An elevated number of background data fetches put unexpected load on the database sufficient to require failover. 

Failover was automatic and completed within a few minutes. 

We observed approximately 66 requests which failed due to timeout due to being unable to contact the database.  .</p>
]]>
  </content:encoded>
  <pubDate>Sun, 8 May 2022 04:23:00 +0000</pubDate>
  <link>https://status.kabillc.com/incident/cl2y7qd5n543642j2ophti2ld0h</link>
  <guid>https://status.kabillc.com/incident/cl2y7qd5n543642j2ophti2ld0h</guid>
</item>

  </channel>
  </rss>