<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:siffletdata-status.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com"/>
  <link rel="self" type="application/atom+xml" href="https://siffletdata-status.com/history.atom"/>
  <title>Sifflet Status - Incident history</title>
  <updated>2026-04-29T11:30:00.000+00:00</updated>
  <author>
    <name>Sifflet</name>
  </author>
  
<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmoirrfgj06wskatd8d8au9q9</id>
  <published>2026-04-29T11:30:00.000+00:00</published>
  <updated>2026-04-29T11:30:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmoirrfgj06wskatd8d8au9q9"/>
  <title>Database maintenance on aws-prod-eu-west-1-a, aws-prod-eu-west-1-b, aws-prod-eu-west-1-c, and aws-prod-us-east-1-a cells</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour and 36 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-b - Integrations, aws-prod-us-east-1-a- Datasource monitoring, aws-prod-us-east-1-a - API, aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-eu-west-1-a - Datasource monitoring, aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-c - API, aws-prod-eu-west-1-c - Web application, aws-prod-eu-west-1-c - Integrations, aws-prod-eu-west-1-a - Integrations, aws-prod-us-east-1-a - Integrations, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-b - API, aws-prod-eu-west-1-b - Web application, aws-prod-us-east-1-a - Web application, aws-prod-eu-west-1-c - Datasource monitoring</p>
    <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>11:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>13:05:36</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled database maintenance during that time. A short (\~few minutes) downtime will occur..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmobhyhx70014ufvykjocj99d</id>
  <published>2026-04-27T11:30:00.000+00:00</published>
  <updated>2026-04-27T11:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmobhyhx70014ufvykjocj99d"/>
  <title>Database maintenance on aws-prod-eu-west-1-d cell</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-d - API, aws-prod-eu-west-1-d - Web application, aws-prod-eu-west-1-d - Datasource monitoring, aws-prod-eu-west-1-d - Integrations</p>
    <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are planning for a scheduled database maintenance on aws-prod-eu-west-1-d cell during that time..</p>
<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>11:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmmta5orr000e10azsu4apmly</id>
  <published>2026-03-16T14:30:01.543+00:00</published>
  <updated>2026-03-16T14:30:01.543+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmmta5orr000e10azsu4apmly"/>
  <title>Email deliverability issues in us-east-1</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 hour and 18 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a - Web application</p>
    <p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>14:30:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Some emails (such as reset password emails) are not being delivered in the us-east-1 region. Alert notification emails are not affected and are properly delivered.

The cause of the incident has been identified and a fix is in progress..</p>
<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>14:41:40</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We deployed a fix and are currently monitoring the result..</p>
<p><small>Mar <var data-var='date'> 16</var>, <var data-var='time'>15:47:36</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmm1y4dm00b1u3w7ew7k297iv</id>
  <published>2026-02-26T09:00:00.000+00:00</published>
  <updated>2026-02-26T09:00:01.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmm1y4dm00b1u3w7ew7k297iv"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-c - Datasource monitoring, aws-prod-eu-west-1-c - Integrations</p>
    <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>09:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>10:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A short database maintenance on aws-prod-eu-west-1-c cell is planned due to ongoing incident on this cell. 

Expect a few minutes of downtime on the application and some missed runs for monitors and datasource refresh..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmlqprxwm01clmg0v51e5vj9h</id>
  <published>2026-02-17T14:44:12.910+00:00</published>
  <updated>2026-02-17T14:44:12.910+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmlqprxwm01clmg0v51e5vj9h"/>
  <title>Delay in ingestion and monitoring jobs</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 35 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-c - Integrations, aws-prod-eu-west-1-c - Datasource monitoring</p>
    <p><small>Feb <var data-var='date'> 17</var>, <var data-var='time'>14:44:12</var> GMT+0</small><br /><strong>Identified</strong> -
  On the aws-prod-eu-west-1-c cell, most jobs (including monitoring and catalog discovery jobs) are either not running or encountering delays. We identified the cause and deployed a fix..</p>
<p><small>Feb <var data-var='date'> 17</var>, <var data-var='time'>14:48:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Jobs are now running as expected..</p>
<p><small>Feb <var data-var='date'> 17</var>, <var data-var='time'>15:19:25</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmm1y12oy0b68qwjbzcb65v6h</id>
  <published>2026-02-17T09:00:00.000+00:00</published>
  <updated>2026-02-17T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmm1y12oy0b68qwjbzcb65v6h"/>
  <title>Scheduled monitor orchestration disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days, 1 hour and 14 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-c - Datasource monitoring</p>
    <p><small>Feb <var data-var='date'> 17</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’re currently experiencing an issue with the orchestration of some scheduled monitors on the eu-west-1-c cell. Some of them might no longer be running according to their configured schedules (for instance &quot;hourly&quot;, &quot;daily&quot; or &quot;weekly&quot;).

Manual runs of monitors through the UI or the API is not impacted and works as expected.

Our team is currently investigating the issue. We’ll provide updates here as the situation progresses..</p>
<p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>09:48:13</var> GMT+0</small><br /><strong>Identified</strong> -
  We identified the cause of the issue, caused by a failure in the behavior of our orchestration framework that happens in some very specific situations, created by the incident that occurred on the 17th of February: &lt;https://siffletdata-status.com/cmlqprxwm01clmg0v51e5vj9h&gt;.

The fix for this issue will be deployed in production on Thursday 26th of February.

We&#039;ve also clarified the impact of the incident: only one of the tenants of the cell is impacted, and only 7 scheduled monitors of this tenant are impacted (meaning they are no longer running according to their schedules). The customer associated with this tenant has already been contacted by our team..</p>
<p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>10:14:10</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.

As previously stated, the current incident was an aftermath of the incident that occurred on the 17th of February (and that was resolved on that day). The detection of this residual impact was delayed by the low volume of impacted monitors compared with the total volume of monitors orchestrated by our platform. We&#039;ve implemented corrective measures on our alerting systems to improve our detection of such events..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>13:25:06</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We deployed a fix of the issue, and are monitoring that the 7 monitors are now running according to their schedules..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmkemdyr108qhn8z8s45wzr6z</id>
  <published>2026-01-15T09:15:00.000+00:00</published>
  <updated>2026-01-15T09:15:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmkemdyr108qhn8z8s45wzr6z"/>
  <title>Database Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-eu-west-1-b - API, aws-prod-eu-west-1-b - Web application</p>
    <p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>09:15:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A short database maintenance on aws-prod-eu-west-1-b cell is planned due to ongoing incident on this cell..</p>
<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>09:15:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>10:15:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmkcw4xv50bn1ss436fi6xgzf</id>
  <published>2026-01-07T17:00:00.000+00:00</published>
  <updated>2026-01-14T15:05:09.057+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmkcw4xv50bn1ss436fi6xgzf"/>
  <title>Datasource scheduled refresh orchestration disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 days, 17 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-b - Integrations</p>
    <p><small>Jan <var data-var='date'> 14</var>, <var data-var='time'>15:05:09</var> GMT+0</small><br /><strong>Identified</strong> -
  We identified the cause of the issue, caused by a failure in the behavior of our orchestration framework in a very specific situation created by last week database maintenance.

The fix for this issue will be deployed in production on Thursday 15th of January..</p>
<p><small>Jan <var data-var='date'> 15</var>, <var data-var='time'>10:44:24</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>17:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’re currently experiencing an issue with the orchestration of the scheduled refresh operations of Sifflet data sources. Some sources might not get refreshed automatically according to their configured schedule (for instance &quot;hourly&quot;, &quot;daily&quot; or &quot;weekly&quot;). 

Manual refresh of data sources through the UI or the API is not impacted and works as expected. 

As a result and unless you trigger manual a refresh of your sources, your data catalog on the application might not represent the most recent state of the metadata of your data assets in your integrated platforms (for instance, the most recent tables, fields, tags, or lineage relationships might be absent).

Our team is currently investigating the issue. We’ll provide updates here as the situation progresses..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmjx0vnuh00e7r4yp4apnucho</id>
  <published>2026-01-07T13:00:00.000+00:00</published>
  <updated>2026-01-07T13:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmjx0vnuh00e7r4yp4apnucho"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a- Datasource monitoring, aws-prod-us-east-1-a - API, aws-prod-eu-west-1-c - Integrations, aws-prod-eu-west-1-a - Integrations, aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-eu-west-1-a - Datasource monitoring, aws-prod-ap-southeast-1-a - Datasource monitoring, aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-c - API, aws-prod-eu-west-1-c - Web application, aws-prod-eu-west-1-b - Integrations, aws-prod-ap-southeast-1-a - Web application, aws-prod-eu-west-1-b - Web application, aws-prod-ap-southeast-1-a - Integrations, aws-prod-us-east-1-a - Integrations, aws-prod-eu-west-1-c - Datasource monitoring, aws-prod-ap-southeast-1-a - API, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-b - API, aws-prod-us-east-1-a - Web application</p>
    <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>13:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A short database maintenance on aws-prod-eu-west-1-a / aws-prod-eu-west-1-b / aws-prod-us-east-1-a cells is planned. Tenants on these cells may experience elevated error rates during a short time window..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>13:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmjban4qw00h351fq7wbsa118</id>
  <published>2025-12-22T14:00:00.000+00:00</published>
  <updated>2025-12-22T14:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmjban4qw00h351fq7wbsa118"/>
  <title>Database Maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-c - Datasource monitoring, aws-prod-eu-west-1-c - API, aws-prod-eu-west-1-c - Web application</p>
    <p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A short database maintenance on the aws-prod-eu-west-1-c cell is planned. Tenants on this cell may experience elevated error rates during a short window (less than 5 minutes)..</p>
<p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>14:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>
<p><small>Dec <var data-var='date'> 22</var>, <var data-var='time'>15:00:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmiptp38900g44jt8qwsf0k0f</id>
  <published>2025-12-01T09:00:00.000+00:00</published>
  <updated>2025-12-01T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmiptp38900g44jt8qwsf0k0f"/>
  <title>Sifflet incident creation disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a- Datasource monitoring, aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-eu-west-1-c - Datasource monitoring, aws-prod-eu-west-1-a - Datasource monitoring, aws-prod-ap-southeast-1-a - Datasource monitoring</p>
    <p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  An issue is preventing Sifflet from creating incidents..</p>
<p><small>Dec <var data-var='date'> 3</var>, <var data-var='time'>09:12:45</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmhixwe3g005ihobzbn6euzcn</id>
  <published>2025-11-01T00:00:00.000+00:00</published>
  <updated>2025-11-01T00:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmhixwe3g005ihobzbn6euzcn"/>
  <title>Email Delivery Disruption</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 9 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-eu-west-1-c - Datasource monitoring, aws-prod-eu-west-1-a - Datasource monitoring</p>
    <p><small>Nov <var data-var='date'> 1</var>, <var data-var='time'>00:00:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We’re currently experiencing an issue with our email delivery system. As a result, monitor failure alerts and other email notifications may not be sent as expected.  
  
We’ll provide updates here as the situation progresses..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>08:42:58</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. We identified the root cause and have reached AWS support to restore normal email delivery as soon as possible..</p>
<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>09:58:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved.  
  
Our email sending capabilities have been fully restored following confirmation from AWS Support.

All monitor failure alerts and other email notifications are now being delivered as expected..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmgyzihsr048jyldjpc8bm367</id>
  <published>2025-10-20T09:30:00.000+00:00</published>
  <updated>2025-10-20T09:30:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmgyzihsr048jyldjpc8bm367"/>
  <title>Degraded performance on us-east-1 cell caused by AWS outage</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 3 hours and 25 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a - Integrations, aws-prod-us-east-1-a- Datasource monitoring, aws-prod-us-east-1-a - API, aws-prod-us-east-1-a - Web application</p>
    <p><small>Oct <var data-var='date'> 20</var>, <var data-var='time'>09:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  This morning AWS outage has impacted all our tenants hosted on the us-east-1 region.

Impact is limited as the application remains mostly available, but integration syncs and datasource monitoring might not be running properly. 

The issue is currently being mitigated by AWS..</p>
<p><small>Oct <var data-var='date'> 21</var>, <var data-var='time'>12:54:30</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cmfdq5spy0094134ihyxyxo3g</id>
  <published>2025-09-09T16:45:00.000+00:00</published>
  <updated>2025-09-09T16:45:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cmfdq5spy0094134ihyxyxo3g"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 30 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-c - Integrations, aws-prod-eu-west-1-c - Web application, aws-prod-eu-west-1-c - Datasource monitoring, aws-prod-eu-west-1-c - API</p>
    <p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>16:45:00</var> GMT+0</small><br /><strong>Identified</strong> -
  A short database maintenance on the aws-prod-eu-west-1-c cell is planned. Tenants on this cell may experience elevated error rates during a short window (less than 5 minutes)..</p>
<p><small>Sep <var data-var='date'> 9</var>, <var data-var='time'>17:15:00</var> GMT+0</small><br /><strong>Completed</strong> -
  Maintenance has completed successfully..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cme2tg4aw00647pbn98b0r474</id>
  <published>2025-08-08T12:10:00.000+00:00</published>
  <updated>2025-08-08T12:25:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cme2tg4aw00647pbn98b0r474"/>
  <title>Downtime on eu-west-1-a cell</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 20 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-a - Datasource monitoring, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-a - Integrations</p>
    <p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:25:00</var> GMT+0</small><br /><strong>Monitoring</strong> -
  Remediation has been successfully applied. We are closely monitoring the status of the cell and investigating its root cause to prevent it from happening again..</p>
<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:10:00</var> GMT+0</small><br /><strong>Investigating</strong> -
  We&#039;re investigating reports of degraded performance across the Sifflet web applications..</p>
<p><small>Aug <var data-var='date'> 8</var>, <var data-var='time'>12:15:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are continuing to work on a fix for this incident. Remediation is being applied..</p>
<p><small>Aug <var data-var='date'> 12</var>, <var data-var='time'>08:27:31</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. 

Downtime started at 2:10pm CEST on Friday the 8th of August and was over by 2:35pm CEST on the same day, and only affected our eu-west-1-a tenants.

The cause of the downtime was an unavailability of the database caused by a sudden surge in the database usage, that occurred at an unexpected speed and magnitude. Our auto-scaling and monitoring systems failed to react in time.

We&#039;re improving our monitoring and auto-scaling to prevent such downtime to happen again and investigating the component that might be responsible for this unnecessary database load. .</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmcehu4x300idyb62zmd17kmz</id>
  <published>2025-06-27T07:31:23.905+00:00</published>
  <updated>2025-06-27T07:40:21.430+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmcehu4x300idyb62zmd17kmz"/>
  <title>Downtime on eu-west-1-a cell</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-a - Datasource monitoring, aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-a - Integrations, aws-prod-eu-west-1-a - API</p>
    <p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>07:40:21</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We solved the cause of the downtime. We&#039;re monitoring the situation to ensure all services stay available..</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>07:31:23</var> GMT+0</small><br /><strong>Investigating</strong> -
  All tenants in the eu-west-1-a cell are experiencing high error rates. We&#039;re investigating..</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>08:38:43</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We&#039;re still performing a complete assessment and postmortem for this incident, but we can share a few preliminary pieces of information.

Only tenants hosted on the aws-prod-eu-west-1-a cell were affected. The incident started at 9:39 pm CEST on 2025-06-26 and was solved at 9:35 CEST on 2025-06-27\. Monitors and source ingestions scheduled during this time did not run. The web application was also unavailable.

Our monitoring systems were not configured to send a page for the events associated to this incident. As a result, the downtime (outside business hours) was unusually long. We are reviewing our alerting notifications to make sure this doesn&#039;t happen again.

We apologize for the impact caused by this incident. Such a long downtime is not acceptable and we&#039;ll implement measures to prevent this from occuring in the future..</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>16:49:35</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved. We updated our monitoring to trigger a page should this condition occurs again, and we identified the root cause of the issue. We&#039;re implemeting mitigations to prevent this incident from occuring again..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cmbhqaa9s000cqtdw96xiuke8</id>
  <published>2025-06-04T09:11:30.128+00:00</published>
  <updated>2025-06-04T09:11:30.128+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cmbhqaa9s000cqtdw96xiuke8"/>
  <title>Data sharing to Snowflake contains stale or no data</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 days, 22 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> , aws-prod-eu-west-1-b - API, aws-prod-ap-southeast-1-a - API, aws-prod-us-east-1-a - API, aws-prod-eu-west-1-c - API, aws-prod-eu-west-1-a - API, 
API →</p>
    <p><small>Jun <var data-var='date'> 4</var>, <var data-var='time'>09:11:30</var> GMT+0</small><br /><strong>Monitoring</strong> -
  While our monitoring is still reporting anomalies, these anomalies should not affect data freshness or completeness..</p>
<p><small>Jun <var data-var='date'> 27</var>, <var data-var='time'>07:38:59</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cm6uk9nne00727f2fi80y6ev8</id>
  <published>2025-02-06T09:00:00.000+00:00</published>
  <updated>2025-02-06T09:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cm6uk9nne00727f2fi80y6ev8"/>
  <title>Data sharing contains incomplete data</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 20 days, 2 hours and 27 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a - API, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-b - API, aws-prod-ap-southeast-1-a - API, aws-prod-eu-west-1-c - API</p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Some data exported with the &quot;data sharing&quot; feature (&lt;https://docs.siffletdata.com/docs/data-sharing&gt;) may be incomplete. Notably, some monitor executions and datasets may be absent from the exported data.

There is no impact on monitoring. However, if your company uses data sharing for reporting, then this reporting may be inacurate.

All data is present in the source systems (no data loss or data integrity issue). The Sifflet API and web UI return all the data. Only data sharing is impacted.

This incident is caused by an AWS RDS process not properly exporting data. We opened a support case with AWS, and are evaluating workarounds in the meantime..</p>
<p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>09:08:41</var> GMT+0</small><br /><strong>Monitoring</strong> -
  AWS support confirmed that there&#039;s an issue with the AWS service we rely on to export data from our databases. The resolution is pending actions on their side..</p>
<p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>10:58:10</var> GMT+0</small><br /><strong>Monitoring</strong> -
  AWS support is still investigating the issue. We&#039;re implementing mitigation measures in the meantime..</p>
<p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>11:26:44</var> GMT+0</small><br /><strong>Resolved</strong> -
  We migrated from the AWS tool we were using affected by the issue. This incident is now resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Maintenance/cm5mdaoj4000d11o4gif6vm0x</id>
  <published>2025-01-07T20:00:00.000+00:00</published>
  <updated>2025-01-07T20:07:08.133+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/maintenance/cm5mdaoj4000d11o4gif6vm0x"/>
  <title>Database maintenance</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-a - Integrations, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-a - Datasource monitoring</p>
    <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>20:07:08</var> GMT+0</small><br /><strong>Completed</strong> -
  The maintenance is complete..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>20:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We&#039;re going to perform a database maintenance to improve application performance on the eu-west-1-a cell.

During this maintenance, there may be elevated error rates during a short period (estimated to less than 5 minutes) on the web UI, API, monitors and integrations..</p>
<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>20:00:01</var> GMT+0</small><br /><strong>Identified</strong> -
  Maintenance is now in progress.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cm1r135v80021p98us265peb8</id>
  <published>2024-10-01T22:46:46.024+00:00</published>
  <updated>2024-10-02T11:41:14.559+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cm1r135v80021p98us265peb8"/>
  <title>Database issues on eu-west-1-a cell</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 12 hours and 54 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-a - Integrations, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-a - Datasource monitoring</p>
    <p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>11:41:14</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>22:46:46</var> GMT+0</small><br /><strong>Investigating</strong> -
  Monitors and sources may not correctly run for tenants on the eu-west-1-a-cell due to a database connectivity issue. We&#039;re investigating..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>00:04:36</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We&#039;re monitoring the situation..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cm1jksoki00os12ltikiyz4y1</id>
  <published>2024-09-26T17:36:19.986+00:00</published>
  <updated>2024-09-26T17:36:19.986+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cm1jksoki00os12ltikiyz4y1"/>
  <title>Downtime on API and web UI in US region</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 23 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a - Web application</p>
    <p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>17:36:19</var> GMT+0</small><br /><strong>Identified</strong> -
  Our hosting provider, AWS, is experiencing a partial outage in the us-east-1 region. We implemented mitigating measures, but some downtime may still occur on tenants in this region..</p>
<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>18:44:04</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We&#039;re no longer observing any impact on our customers.

As the AWS outage is not marked as resolved, we&#039;re keeping this incident open for now..</p>
<p><small>Sep <var data-var='date'> 26</var>, <var data-var='time'>20:59:47</var> GMT+0</small><br /><strong>Resolved</strong> -
  The AWS outage is now marked as resolved and we are no longer observing any issue for our customers in the us-east-1 region..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cm0nz04aa000crutrtqay5ace</id>
  <published>2024-09-04T14:00:00.000+00:00</published>
  <updated>2024-09-04T14:00:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cm0nz04aa000crutrtqay5ace"/>
  <title>Technical error on monitor execution </title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 44 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-ap-southeast-1-a - Datasource monitoring, aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-us-east-1-a- Datasource monitoring, aws-prod-eu-west-1-a - Datasource monitoring</p>
    <p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>14:00:00</var> GMT+0</small><br /><strong>Identified</strong> -
  Some monitors may fail with Technical error.

We have identified the issue and are working on a fix for this incident..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>15:24:04</var> GMT+0</small><br /><strong>Monitoring</strong> -
  A fix has been implemented and is being deployed..</p>
<p><small>Sep <var data-var='date'> 4</var>, <var data-var='time'>16:44:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/clztxqi28227285hboc2z3nqbq9</id>
  <published>2024-08-14T14:16:49.972+00:00</published>
  <updated>2024-08-14T14:16:49.972+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/clztxqi28227285hboc2z3nqbq9"/>
  <title>No new lineage for Snowflake, Redshift, and BigQuery</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 hours and 18 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a - Integrations, aws-prod-eu-west-1-b - Integrations, aws-prod-eu-west-1-b - Web application, aws-prod-eu-west-1-a - Web application, aws-prod-eu-west-1-a - Integrations, aws-prod-us-east-1-a - API, aws-prod-eu-west-1-a - API, aws-prod-eu-west-1-b - API, aws-prod-ap-southeast-1-a - API, aws-prod-ap-southeast-1-a - Datasource monitoring, aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-us-east-1-a - Web application, aws-prod-ap-southeast-1-a - Integrations, aws-prod-us-east-1-a- Datasource monitoring, aws-prod-eu-west-1-a - Datasource monitoring, aws-prod-ap-southeast-1-a - Web application</p>
    <p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>14:16:49</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are currently investigating this incident..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>16:35:12</var> GMT+0</small><br /><strong>Resolved</strong> -
  * We detected lineage discrepancies for the Snowflake Enterprise integration
* A fix is currently being deployed
* If you notice missing lineage, please rerun the source
* If the issues persist after rerunning the source, please reach out to us.</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/cly5srk0g53910hyn5fm3679tf</id>
  <published>2024-07-03T11:50:00.000+00:00</published>
  <updated>2024-07-03T11:50:00.000+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/cly5srk0g53910hyn5fm3679tf"/>
  <title>Downtime on web UI and the API</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 9 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-b - Web application</p>
    <p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:50:00</var> GMT+0</small><br /><strong>Identified</strong> -
  The web UI and API of all tenants on eu-west-1-b is unavailable..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>11:59:00</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident was caused by insufficient cluster capacity and is now resolved..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/clsaj4wsg0393bcosobelkvfa</id>
  <published>2024-02-06T15:30:00.000+00:00</published>
  <updated>2024-02-06T16:22:29.579+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/clsaj4wsg0393bcosobelkvfa"/>
  <title>Business Glossary unavailable</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 52 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-eu-west-1-b - Web application, aws-prod-eu-west-1-a - Web application, aws-prod-us-east-1-a - Web application, aws-prod-ap-southeast-1-a - Web application</p>
    <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>16:22:29</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br /><strong>Identified</strong> -
  We are aware of technical errors when going to the Business Glossary section of the Sifflet platform. We have identified the issue and are working on a fix for this incident..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/clpwedk3f3967b5mwcthaolf1</id>
  <published>2023-12-08T09:01:08.603+00:00</published>
  <updated>2023-12-08T16:51:25.375+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/clpwedk3f3967b5mwcthaolf1"/>
  <title>Delay in executing monitoring rules or ingestion jobs</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 7 hours and 50 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-us-east-1-a - Integrations, aws-prod-eu-west-1-b - Integrations, aws-prod-us-east-1-a- Datasource monitoring, aws-prod-eu-west-1-a - Integrations, aws-prod-ap-southeast-1-a - Datasource monitoring, aws-prod-eu-west-1-b - Datasource monitoring, aws-prod-ap-southeast-1-a - Integrations, aws-prod-eu-west-1-a - Datasource monitoring</p>
    <p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>16:51:25</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>09:01:08</var> GMT+0</small><br /><strong>Investigating</strong> -
  Monitors and metatadata ingestion jobs are experiencing delays.
Some monitors may not be run in a timely manner.

We&#039;re investigating this issue.

(a previous version of this message mentioned only the eu-west-1-a cell).</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>09:42:22</var> GMT+0</small><br /><strong>Investigating</strong> -
  Monitors are now running as usual.

Some metadata ingestion jobs may still be delayed for a few customers..</p>
<p><small>Dec <var data-var='date'> 8</var>, <var data-var='time'>11:44:14</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:siffletdata-status.com,2005:Incident/clocy2d8r44524b6mxv4zdi4br</id>
  <published>2023-10-30T13:37:13.267+00:00</published>
  <updated>2023-10-30T13:37:13.267+00:00</updated>
  <link rel="alternate" type="text/html" href="https://siffletdata-status.com/incident/clocy2d8r44524b6mxv4zdi4br"/>
  <title>New users cannot log in to Sifflet when not assigned domain &quot;All”</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> aws-prod-ap-southeast-1-a - Web application, aws-prod-eu-west-1-b - Web application, aws-prod-eu-west-1-a - Web application, aws-prod-us-east-1-a - Web application</p>
    <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>13:37:13</var> GMT+0</small><br /><strong>Monitoring</strong> -
  New users (whatever the role) can be created but when logging in, they are instantly logged out if they do not have the &quot;All&quot; domain. If they have the &quot;All domain&quot;, the log in works normally.</p>
<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>13:56:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

</feed>