<?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>Sibylline Status - Incident history</title>
    <link>https://status.sibylline.com</link>
    <description>Sibylline</description>
    <pubDate>Tue, 3 Nov 2026 10:15:20 +0000</pubDate>
    
<item>
  <title>Email Notifications</title>
  <description>
    Type: Incident
    Duration: 1 hour and 10 minutes

    Affected Components: Global Alerts, Notifications
    Nov 3, 11:25:48 GMT+0 - Resolved - The email delivery issue has been resolved, and we have confirmed that all previously pending email notifications have now been sent. Normal email delivery has resumed.

We sincerely apologise for any inconvenience or disruption caused and thank you for your patience while we worked to restore the service. Nov 3, 10:55:31 GMT+0 - Monitoring - We have identified and addressed the issue affecting our upstream email delivery service. Email notifications are now being processed, although some may take additional time to arrive due to the backlog.

We sincerely apologise for any inconvenience or disruption caused. We will continue to monitor email delivery closely to ensure normal service is fully restored and provide further updates as necessary. Nov 3, 10:15:20 GMT+0 - Investigating - We are currently investigating an incident affecting the delivery of all email notifications from the Sibylline portal. Notifications may be delayed or not delivered during this time. We are working to identify the cause and restore normal service. Further updates will be provided as the investigation progresses. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>11:25:48</var> GMT+0</small><br><strong>Resolved</strong> -
  The email delivery issue has been resolved, and we have confirmed that all previously pending email notifications have now been sent. Normal email delivery has resumed.

We sincerely apologise for any inconvenience or disruption caused and thank you for your patience while we worked to restore the service..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>10:55:31</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have identified and addressed the issue affecting our upstream email delivery service. Email notifications are now being processed, although some may take additional time to arrive due to the backlog.

We sincerely apologise for any inconvenience or disruption caused. We will continue to monitor email delivery closely to ensure normal service is fully restored and provide further updates as necessary..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>10:15:20</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an incident affecting the delivery of all email notifications from the Sibylline portal. Notifications may be delayed or not delivered during this time. We are working to identify the cause and restore normal service. Further updates will be provided as the investigation progresses..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 3 Nov 2026 10:15:20 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmw0j7rtj089e1ns2y1ig1c6a</link>
  <guid>https://status.sibylline.com/incident/cmw0j7rtj089e1ns2y1ig1c6a</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Oct 30, 03:16:12 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Oct 30, 03:06:12 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>03:16:12</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>03:06:12</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 30 Oct 2026 03:06:12 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmvue4lmy003k07mlreo84yjx</link>
  <guid>https://status.sibylline.com/incident/cmvue4lmy003k07mlreo84yjx</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Oct 21, 19:28:30 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Oct 21, 16:27:59 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>19:28:30</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>16:27:59</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 21 Oct 2026 16:27:59 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmvibsznx009007nw9qrhx84u</link>
  <guid>https://status.sibylline.com/incident/cmvibsznx009007nw9qrhx84u</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Oct 12, 21:16:05 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Oct 12, 21:11:24 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>21:16:05</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 12</var>, <var data-var='time'>21:11:24</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 12 Oct 2026 21:11:24 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmv5qys6400gg07nq6igq0nw6</link>
  <guid>https://status.sibylline.com/incident/cmv5qys6400gg07nq6igq0nw6</guid>
</item>

<item>
  <title>Astramap is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Astramap
    Sep 7, 06:40:04 GMT+0 - Resolved - Astramap is back up. This incident was automatically resolved by Instatus monitoring. Sep 7, 06:20:02 GMT+0 - Investigating - Astramap is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>06:40:04</var> GMT+0</small><br><strong>Resolved</strong> -
  Astramap is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>06:20:02</var> GMT+0</small><br><strong>Investigating</strong> -
  Astramap is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 7 Sep 2026 06:20:02 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmtqupxmq009007mpcvfm0n9x</link>
  <guid>https://status.sibylline.com/incident/cmtqupxmq009007mpcvfm0n9x</guid>
</item>

<item>
  <title>API is back up</title>
  <description>
    Type: Incident
    

    Affected Components: API
    Sep 7, 06:40:05 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. Sep 7, 06:20:00 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>06:40:05</var> GMT+0</small><br><strong>Resolved</strong> -
  API is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>06:20:00</var> GMT+0</small><br><strong>Investigating</strong> -
  API is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 7 Sep 2026 06:20:00 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmtquplgl005n07qy476vnlvp</link>
  <guid>https://status.sibylline.com/incident/cmtquplgl005n07qy476vnlvp</guid>
</item>

<item>
  <title>Service Disruption</title>
  <description>
    Type: Incident
    Duration: 41 minutes

    Affected Components: App
    Aug 11, 09:41:51 GMT+0 - Resolved - On 11 August 2026, `app.sibylline.com` experienced a service interruption caused by an issue with the TLS certificate associated with the service&#039;s custom domain.

The underlying application and infrastructure remained healthy throughout the incident. The issue was isolated to the certificate and custom domain routing layer and normal service was restored following a refresh.

We are reviewing the certificate lifecycle and monitoring configuration to reduce the risk of a similar interruption occurring in future. Aug 11, 09:00:51 GMT+0 - Identified - We are currently investigating an issue that is causing a disruption to service. Our team is working to identify the root cause and will provide updates as soon as more information is available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>09:41:51</var> GMT+0</small><br><strong>Resolved</strong> -
  On 11 August 2026, `app.sibylline.com` experienced a service interruption caused by an issue with the TLS certificate associated with the service&#039;s custom domain.

The underlying application and infrastructure remained healthy throughout the incident. The issue was isolated to the certificate and custom domain routing layer and normal service was restored following a refresh.

We are reviewing the certificate lifecycle and monitoring configuration to reduce the risk of a similar interruption occurring in future..</p>
<p><small>Aug <var data-var='date'> 11</var>, <var data-var='time'>09:00:51</var> GMT+0</small><br><strong>Identified</strong> -
  We are currently investigating an issue that is causing a disruption to service. Our team is working to identify the root cause and will provide updates as soon as more information is available..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 11 Aug 2026 09:00:51 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmsoi50zc07gz0zloij90npic</link>
  <guid>https://status.sibylline.com/incident/cmsoi50zc07gz0zloij90npic</guid>
</item>

<item>
  <title>Email Notification</title>
  <description>
    Type: Incident
    Duration: 26 days, 1 hour and 8 minutes

    Affected Components: Notifications
    Oct 28, 11:07:33 GMT+0 - Resolved - Notifications through the new Sibylline Intelligence 3.0 platform are now fully operational and switching over from the World Risk Register platform.  Aug 4, 13:56:19 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Aug 4, 10:00:00 GMT+0 - Identified - We are currently investigating an issue affecting email delivery. To avoid disruption while we work toward a resolution, emails have temporarily been reinstated through the original delivery platform.

Access to the application remains unaffected, and no action is required from users.

Once the issue has been resolved and the fix has been fully validated, we will complete a seamless changeover and provide a further update. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 26 days, 1 hour and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 28</var>, <var data-var='time'>11:07:33</var> GMT+0</small><br><strong>Resolved</strong> -
  Notifications through the new Sibylline Intelligence 3.0 platform are now fully operational and switching over from the World Risk Register platform. .</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>13:56:19</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are currently investigating an issue affecting email delivery. To avoid disruption while we work toward a resolution, emails have temporarily been reinstated through the original delivery platform.

Access to the application remains unaffected, and no action is required from users.

Once the issue has been resolved and the fix has been fully validated, we will complete a seamless changeover and provide a further update..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 4 Aug 2026 10:00:00 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmserjkgm0fyd0zpp7jk2pwai</link>
  <guid>https://status.sibylline.com/incident/cmserjkgm0fyd0zpp7jk2pwai</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Jul 22, 16:07:24 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Jul 22, 15:57:41 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>16:07:24</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jul <var data-var='date'> 22</var>, <var data-var='time'>15:57:41</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 22 Jul 2026 15:57:41 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmrw9nijz00db0ko69qpprlcf</link>
  <guid>https://status.sibylline.com/incident/cmrw9nijz00db0ko69qpprlcf</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Jul 13, 14:46:46 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Jul 13, 14:37:08 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>14:46:46</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>14:37:08</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 13 Jul 2026 14:37:07 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmrjbt6tn000a0kqul8n3kyfu</link>
  <guid>https://status.sibylline.com/incident/cmrjbt6tn000a0kqul8n3kyfu</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Jul 10, 10:15:34 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Jul 10, 10:05:50 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>10:15:34</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>10:05:50</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 10 Jul 2026 10:05:50 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmrersqlv00fh0kmk1wbawmj6</link>
  <guid>https://status.sibylline.com/incident/cmrersqlv00fh0kmk1wbawmj6</guid>
</item>

<item>
  <title>Sibylline Home is back up</title>
  <description>
    Type: Incident
    

    
    Jun 3, 17:11:12 GMT+0 - Resolved - Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring. Jun 3, 17:01:46 GMT+0 - Investigating - Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>17:11:12</var> GMT+0</small><br><strong>Resolved</strong> -
  Sibylline Home is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Jun <var data-var='date'> 3</var>, <var data-var='time'>17:01:46</var> GMT+0</small><br><strong>Investigating</strong> -
  Sibylline Home is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 3 Jun 2026 17:01:44 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmpybd38i003fms14np5y3gw7</link>
  <guid>https://status.sibylline.com/incident/cmpybd38i003fms14np5y3gw7</guid>
</item>

<item>
  <title>API is back up</title>
  <description>
    Type: Incident
    

    Affected Components: API
    May 21, 13:23:24 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. May 21, 13:12:58 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>May <var data-var='date'> 21</var>, <var data-var='time'>13:23:24</var> GMT+0</small><br><strong>Resolved</strong> -
  API is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>May <var data-var='date'> 21</var>, <var data-var='time'>13:12:58</var> GMT+0</small><br><strong>Investigating</strong> -
  API is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 21 May 2026 13:12:56 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmpfigrw000c6jz1577c53fwb</link>
  <guid>https://status.sibylline.com/incident/cmpfigrw000c6jz1577c53fwb</guid>
</item>

<item>
  <title>Astramap is back up</title>
  <description>
    Type: Incident
    

    Affected Components: Astramap
    Apr 5, 11:05:07 GMT+0 - Resolved - Astramap is back up. This incident was automatically resolved by Instatus monitoring. Apr 5, 10:55:02 GMT+0 - Investigating - Astramap is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>11:05:07</var> GMT+0</small><br><strong>Resolved</strong> -
  Astramap is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>10:55:02</var> GMT+0</small><br><strong>Investigating</strong> -
  Astramap is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 5 Apr 2026 10:55:02 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmnlna8fk077vjomav70rdki1</link>
  <guid>https://status.sibylline.com/incident/cmnlna8fk077vjomav70rdki1</guid>
</item>

<item>
  <title>API is back up</title>
  <description>
    Type: Incident
    

    Affected Components: API
    Apr 5, 11:02:27 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. Apr 5, 10:52:22 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> </p>
    <p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>11:02:27</var> GMT+0</small><br><strong>Resolved</strong> -
  API is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Apr <var data-var='date'> 5</var>, <var data-var='time'>10:52:22</var> GMT+0</small><br><strong>Investigating</strong> -
  API is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sun, 5 Apr 2026 10:52:22 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmnln6t8y0bi9byivz9wtth2c</link>
  <guid>https://status.sibylline.com/incident/cmnln6t8y0bi9byivz9wtth2c</guid>
</item>

<item>
  <title>Sibylline Home is down</title>
  <description>
    Type: Incident
    

    
    Oct 11, 01:41:54 GMT+0 - Resolved -  is back up. This incident was automatically resolved by Instatus monitoring. Oct 11, 01:31:15 GMT+0 - Investigating -  is down at the moment. This incident was automatically created by Instatus monitoring. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    
    
    <p><small>Oct <var data-var='date'> 11</var>, <var data-var='time'>01:41:54</var> GMT+0</small><br><strong>Resolved</strong> -
   is back up. This incident was automatically resolved by Instatus monitoring..</p>
<p><small>Oct <var data-var='date'> 11</var>, <var data-var='time'>01:31:15</var> GMT+0</small><br><strong>Investigating</strong> -
   is down at the moment. This incident was automatically created by Instatus monitoring..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 11 Oct 2025 01:31:15 +0000</pubDate>
  <link>https://status.sibylline.com/incident/cmgllna27005k6j9hdviesfus</link>
  <guid>https://status.sibylline.com/incident/cmgllna27005k6j9hdviesfus</guid>
</item>

  </channel>
  </rss>