Sifflet Status - Incident history https://siffletdata-status.com Sifflet Thu, 26 Feb 2026 09:00:00 +0000 Database maintenance Type: Maintenance Duration: 1 hour Affected Components: eu-west-1-c - Datasource monitoring, eu-west-1-c - Integrations Feb 26, 09:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 26, 10:00:00 GMT+0 - Completed - Maintenance has completed successfully Feb 26, 09:00:00 GMT+0 - Identified - 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. Type: Maintenance

Duration: 1 hour

Affected Components: ,

<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> ]]> Thu, 26 Feb 2026 09:00:00 +0000 https://siffletdata-status.com/maintenance/cmm1y4dm00b1u3w7ew7k297iv https://siffletdata-status.com/maintenance/cmm1y4dm00b1u3w7ew7k297iv Delay in ingestion and monitoring jobs Type: Incident Duration: 35 minutes Affected Components: eu-west-1-c - Integrations, eu-west-1-c - Datasource monitoring Feb 17, 14:44:12 GMT+0 - Identified - 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. Feb 17, 14:48:36 GMT+0 - Monitoring - Jobs are now running as expected. Feb 17, 15:19:25 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 35 minutes

Affected Components: ,

<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> ]]> Tue, 17 Feb 2026 14:44:12 +0000 https://siffletdata-status.com/incident/cmlqprxwm01clmg0v51e5vj9h https://siffletdata-status.com/incident/cmlqprxwm01clmg0v51e5vj9h Scheduled monitor orchestration disruption Type: Incident Duration: 10 days, 1 hour and 14 minutes Affected Components: eu-west-1-c - Datasource monitoring Feb 17, 09:00:00 GMT+0 - Investigating - 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 "hourly", "daily" or "weekly"). 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. Feb 25, 09:48:13 GMT+0 - Identified - 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: <https://siffletdata-status.com/cmlqprxwm01clmg0v51e5vj9h>. The fix for this issue will be deployed in production on Thursday 26th of February. We'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. Feb 27, 10:14:10 GMT+0 - Resolved - 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've implemented corrective measures on our alerting systems to improve our detection of such events. Feb 26, 13:25:06 GMT+0 - Monitoring - We deployed a fix of the issue, and are monitoring that the 7 monitors are now running according to their schedules. Type: Incident

Duration: 10 days, 1 hour and 14 minutes

Affected Components:

<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 "hourly", "daily" or "weekly"). 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: <https://siffletdata-status.com/cmlqprxwm01clmg0v51e5vj9h>. The fix for this issue will be deployed in production on Thursday 26th of February. We'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'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> ]]> Tue, 17 Feb 2026 09:00:00 +0000 https://siffletdata-status.com/incident/cmm1y12oy0b68qwjbzcb65v6h https://siffletdata-status.com/incident/cmm1y12oy0b68qwjbzcb65v6h Database Maintenance Type: Maintenance Duration: 1 hour Affected Components: eu-west-1-b - Datasource monitoring, eu-west-1-b - API, eu-west-1-b - Web application Jan 15, 09:15:00 GMT+0 - Identified - A short database maintenance on aws-prod-eu-west-1-b cell is planned due to ongoing incident on this cell. Jan 15, 09:15:01 GMT+0 - Identified - Maintenance is now in progress Jan 15, 10:15:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components: , ,

<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> ]]> Thu, 15 Jan 2026 09:15:00 +0000 https://siffletdata-status.com/maintenance/cmkemdyr108qhn8z8s45wzr6z https://siffletdata-status.com/maintenance/cmkemdyr108qhn8z8s45wzr6z Datasource scheduled refresh orchestration disruption Type: Incident Duration: 7 days, 17 hours and 44 minutes Affected Components: eu-west-1-b - Integrations Jan 14, 15:05:09 GMT+0 - Identified - 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. Jan 15, 10:44:24 GMT+0 - Resolved - This incident has been resolved. Jan 7, 17:00:00 GMT+0 - Investigating - 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 "hourly", "daily" or "weekly"). 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. Type: Incident

Duration: 7 days, 17 hours and 44 minutes

Affected Components:

<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 "hourly", "daily" or "weekly"). 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> ]]> Wed, 7 Jan 2026 17:00:00 +0000 https://siffletdata-status.com/incident/cmkcw4xv50bn1ss436fi6xgzf https://siffletdata-status.com/incident/cmkcw4xv50bn1ss436fi6xgzf Database maintenance Type: Maintenance Duration: 2 hours Affected Components: us-east-1-a- Datasource monitoring, us-east-1-a - API, eu-west-1-c - Integrations, eu-west-1-a - Integrations, eu-west-1-b - Datasource monitoring, eu-west-1-a - Datasource monitoring, ap-southeast-1-a - Datasource monitoring, eu-west-1-a - Web application, eu-west-1-c - API, eu-west-1-c - Web application, eu-west-1-b - Integrations, ap-southeast-1-a - Web application, eu-west-1-b - Web application, ap-southeast-1-a - Integrations, us-east-1-a - Integrations, eu-west-1-c - Datasource monitoring, ap-southeast-1-a - API, eu-west-1-a - API, eu-west-1-b - API, us-east-1-a - Web application Jan 7, 13:00:00 GMT+0 - Identified - 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. Jan 7, 13:00:01 GMT+0 - Identified - Maintenance is now in progress Jan 7, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 2 hours

Affected Components: , , , , , , , , , , , , , , , , , , ,

<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> ]]> Wed, 7 Jan 2026 13:00:00 +0000 https://siffletdata-status.com/maintenance/cmjx0vnuh00e7r4yp4apnucho https://siffletdata-status.com/maintenance/cmjx0vnuh00e7r4yp4apnucho Database Maintenance Type: Maintenance Duration: 1 hour Affected Components: eu-west-1-c - Datasource monitoring, eu-west-1-c - API, eu-west-1-c - Web application Dec 22, 14:00:00 GMT+0 - Identified - 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). Dec 22, 14:00:01 GMT+0 - Identified - Maintenance is now in progress Dec 22, 15:00:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components: , ,

<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> ]]> Mon, 22 Dec 2025 14:00:00 +0000 https://siffletdata-status.com/maintenance/cmjban4qw00h351fq7wbsa118 https://siffletdata-status.com/maintenance/cmjban4qw00h351fq7wbsa118 Sifflet incident creation disruption Type: Incident Affected Components: us-east-1-a- Datasource monitoring, eu-west-1-b - Datasource monitoring, eu-west-1-c - Datasource monitoring, eu-west-1-a - Datasource monitoring, ap-southeast-1-a - Datasource monitoring Dec 1, 09:00:00 GMT+0 - Resolved - An issue is preventing Sifflet from creating incidents. Dec 3, 09:12:45 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components: , , , ,

<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> ]]> Mon, 1 Dec 2025 09:00:00 +0000 https://siffletdata-status.com/incident/cmiptp38900g44jt8qwsf0k0f https://siffletdata-status.com/incident/cmiptp38900g44jt8qwsf0k0f Email Delivery Disruption Type: Incident Duration: 2 days, 9 hours and 59 minutes Affected Components: eu-west-1-b - Datasource monitoring, eu-west-1-c - Datasource monitoring, eu-west-1-a - Datasource monitoring Nov 1, 00:00:00 GMT+0 - Investigating - 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. Nov 3, 08:42:58 GMT+0 - Identified - 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. Nov 3, 09:58:44 GMT+0 - Resolved - 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. Type: Incident

Duration: 2 days, 9 hours and 59 minutes

Affected Components: , ,

<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> ]]> Sat, 1 Nov 2025 00:00:00 +0000 https://siffletdata-status.com/incident/cmhixwe3g005ihobzbn6euzcn https://siffletdata-status.com/incident/cmhixwe3g005ihobzbn6euzcn Degraded performance on us-east-1 cell caused by AWS outage Type: Incident Duration: 1 day, 3 hours and 25 minutes Affected Components: us-east-1-a - Integrations, us-east-1-a- Datasource monitoring, us-east-1-a - API, us-east-1-a - Web application Oct 20, 09:30:00 GMT+0 - Identified - 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. Oct 21, 12:54:30 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 3 hours and 25 minutes

Affected Components: , , ,

<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> ]]> Mon, 20 Oct 2025 09:30:00 +0000 https://siffletdata-status.com/incident/cmgyzihsr048jyldjpc8bm367 https://siffletdata-status.com/incident/cmgyzihsr048jyldjpc8bm367 Database maintenance Type: Maintenance Duration: 30 minutes Affected Components: eu-west-1-c - Integrations, eu-west-1-c - Web application, eu-west-1-c - Datasource monitoring, eu-west-1-c - API Sep 9, 16:45:00 GMT+0 - Identified - 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). Sep 9, 17:15:00 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 30 minutes

Affected Components: , , ,

<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> ]]> Tue, 9 Sep 2025 16:45:00 +0000 https://siffletdata-status.com/maintenance/cmfdq5spy0094134ihyxyxo3g https://siffletdata-status.com/maintenance/cmfdq5spy0094134ihyxyxo3g Downtime on eu-west-1-a cell Type: Incident Duration: 3 days, 20 hours and 18 minutes Affected Components: eu-west-1-a - Datasource monitoring, eu-west-1-a - API, eu-west-1-a - Web application, eu-west-1-a - Integrations Aug 8, 12:25:00 GMT+0 - Monitoring - 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. Aug 8, 12:10:00 GMT+0 - Investigating - We're investigating reports of degraded performance across the Sifflet web applications. Aug 8, 12:15:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Remediation is being applied. Aug 12, 08:27:31 GMT+0 - Resolved - 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'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. Type: Incident

Duration: 3 days, 20 hours and 18 minutes

Affected Components: , , ,

<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'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'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> ]]> Fri, 8 Aug 2025 12:10:00 +0000 https://siffletdata-status.com/incident/cme2tg4aw00647pbn98b0r474 https://siffletdata-status.com/incident/cme2tg4aw00647pbn98b0r474 Downtime on eu-west-1-a cell Type: Incident Duration: 9 hours and 18 minutes Affected Components: eu-west-1-a - Datasource monitoring, eu-west-1-a - Web application, eu-west-1-a - Integrations, eu-west-1-a - API Jun 27, 07:40:21 GMT+0 - Monitoring - We solved the cause of the downtime. We're monitoring the situation to ensure all services stay available. Jun 27, 07:31:23 GMT+0 - Investigating - All tenants in the eu-west-1-a cell are experiencing high error rates. We're investigating. Jun 27, 08:38:43 GMT+0 - Monitoring - We'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't happen again. We apologize for the impact caused by this incident. Such a long downtime is not acceptable and we'll implement measures to prevent this from occuring in the future. Jun 27, 16:49:35 GMT+0 - Resolved - 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're implemeting mitigations to prevent this incident from occuring again. Type: Incident

Duration: 9 hours and 18 minutes

Affected Components: , , ,

<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'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'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'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't happen again. We apologize for the impact caused by this incident. Such a long downtime is not acceptable and we'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're implemeting mitigations to prevent this incident from occuring again..</p> ]]> Fri, 27 Jun 2025 07:31:23 +0000 https://siffletdata-status.com/incident/cmcehu4x300idyb62zmd17kmz https://siffletdata-status.com/incident/cmcehu4x300idyb62zmd17kmz Data sharing to Snowflake contains stale or no data Type: Incident Duration: 22 days, 22 hours and 27 minutes Affected Components: , eu-west-1-b - API, ap-southeast-1-a - API, us-east-1-a - API, eu-west-1-c - API, eu-west-1-a - API, API → Jun 4, 09:11:30 GMT+0 - Monitoring - While our monitoring is still reporting anomalies, these anomalies should not affect data freshness or completeness. Jun 27, 07:38:59 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 22 days, 22 hours and 27 minutes

Affected Components: , , , , ,

<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> ]]> Wed, 4 Jun 2025 09:11:30 +0000 https://siffletdata-status.com/incident/cmbhqaa9s000cqtdw96xiuke8 https://siffletdata-status.com/incident/cmbhqaa9s000cqtdw96xiuke8 Data sharing contains incomplete data Type: Incident Duration: 20 days, 2 hours and 27 minutes Affected Components: us-east-1-a - API, eu-west-1-a - API, eu-west-1-b - API, ap-southeast-1-a - API, eu-west-1-c - API Feb 6, 09:00:00 GMT+0 - Identified - Some data exported with the "data sharing" feature (<https://docs.siffletdata.com/docs/data-sharing>) 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. Feb 10, 09:08:41 GMT+0 - Monitoring - AWS support confirmed that there's an issue with the AWS service we rely on to export data from our databases. The resolution is pending actions on their side. Feb 20, 10:58:10 GMT+0 - Monitoring - AWS support is still investigating the issue. We're implementing mitigation measures in the meantime. Feb 26, 11:26:44 GMT+0 - Resolved - We migrated from the AWS tool we were using affected by the issue. This incident is now resolved. Type: Incident

Duration: 20 days, 2 hours and 27 minutes

Affected Components: , , , ,

<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 "data sharing" feature (<https://docs.siffletdata.com/docs/data-sharing>) 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'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'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> ]]> Thu, 6 Feb 2025 09:00:00 +0000 https://siffletdata-status.com/incident/cm6uk9nne00727f2fi80y6ev8 https://siffletdata-status.com/incident/cm6uk9nne00727f2fi80y6ev8 Database maintenance Type: Maintenance Duration: 7 minutes Affected Components: eu-west-1-a - Web application, eu-west-1-a - Integrations, eu-west-1-a - API, eu-west-1-a - Datasource monitoring Jan 7, 20:07:08 GMT+0 - Completed - The maintenance is complete. Jan 7, 20:00:00 GMT+0 - Identified - We'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. Jan 7, 20:00:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 7 minutes

Affected Components: , , ,

<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'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> ]]> Tue, 7 Jan 2025 20:00:00 +0000 https://siffletdata-status.com/maintenance/cm5mdaoj4000d11o4gif6vm0x https://siffletdata-status.com/maintenance/cm5mdaoj4000d11o4gif6vm0x Database issues on eu-west-1-a cell Type: Incident Duration: 12 hours and 54 minutes Affected Components: eu-west-1-a - Web application, eu-west-1-a - Integrations, eu-west-1-a - API, eu-west-1-a - Datasource monitoring Oct 2, 11:41:14 GMT+0 - Resolved - This incident has been resolved. Oct 1, 22:46:46 GMT+0 - Investigating - Monitors and sources may not correctly run for tenants on the eu-west-1-a-cell due to a database connectivity issue. We're investigating. Oct 2, 00:04:36 GMT+0 - Monitoring - We're monitoring the situation. Type: Incident

Duration: 12 hours and 54 minutes

Affected Components: , , ,

<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'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're monitoring the situation..</p> ]]> Tue, 1 Oct 2024 22:46:46 +0000 https://siffletdata-status.com/incident/cm1r135v80021p98us265peb8 https://siffletdata-status.com/incident/cm1r135v80021p98us265peb8 Downtime on API and web UI in US region Type: Incident Duration: 3 hours and 23 minutes Affected Components: us-east-1-a - Web application Sep 26, 17:36:19 GMT+0 - Identified - 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. Sep 26, 18:44:04 GMT+0 - Monitoring - We're no longer observing any impact on our customers. As the AWS outage is not marked as resolved, we're keeping this incident open for now. Sep 26, 20:59:47 GMT+0 - Resolved - 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. Type: Incident

Duration: 3 hours and 23 minutes

Affected Components:

<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're no longer observing any impact on our customers. As the AWS outage is not marked as resolved, we'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> ]]> Thu, 26 Sep 2024 17:36:19 +0000 https://siffletdata-status.com/incident/cm1jksoki00os12ltikiyz4y1 https://siffletdata-status.com/incident/cm1jksoki00os12ltikiyz4y1 Technical error on monitor execution Type: Incident Duration: 2 hours and 44 minutes Affected Components: ap-southeast-1-a - Datasource monitoring, eu-west-1-b - Datasource monitoring, us-east-1-a- Datasource monitoring, eu-west-1-a - Datasource monitoring Sep 4, 14:00:00 GMT+0 - Identified - Some monitors may fail with Technical error. We have identified the issue and are working on a fix for this incident. Sep 4, 15:24:04 GMT+0 - Monitoring - A fix has been implemented and is being deployed. Sep 4, 16:44:04 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 2 hours and 44 minutes

Affected Components: , , ,

<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> ]]> Wed, 4 Sep 2024 14:00:00 +0000 https://siffletdata-status.com/incident/cm0nz04aa000crutrtqay5ace https://siffletdata-status.com/incident/cm0nz04aa000crutrtqay5ace No new lineage for Snowflake, Redshift, and BigQuery Type: Incident Duration: 2 hours and 18 minutes Affected Components: us-east-1-a - Integrations, eu-west-1-b - Integrations, eu-west-1-b - Web application, eu-west-1-a - Web application, eu-west-1-a - Integrations, us-east-1-a - API, eu-west-1-a - API, eu-west-1-b - API, ap-southeast-1-a - API, ap-southeast-1-a - Datasource monitoring, eu-west-1-b - Datasource monitoring, us-east-1-a - Web application, ap-southeast-1-a - Integrations, us-east-1-a- Datasource monitoring, eu-west-1-a - Datasource monitoring, ap-southeast-1-a - Web application Aug 14, 14:16:49 GMT+0 - Investigating - We are currently investigating this incident. Aug 14, 16:35:12 GMT+0 - Resolved - * 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 Type: Incident

Duration: 2 hours and 18 minutes

Affected Components: , , , , , , , , , , , , , , ,

<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> ]]> Wed, 14 Aug 2024 14:16:49 +0000 https://siffletdata-status.com/incident/clztxqi28227285hboc2z3nqbq9 https://siffletdata-status.com/incident/clztxqi28227285hboc2z3nqbq9 Downtime on web UI and the API Type: Incident Duration: 9 minutes Affected Components: eu-west-1-b - Web application Jul 3, 11:50:00 GMT+0 - Identified - The web UI and API of all tenants on eu-west-1-b is unavailable. Jul 3, 11:59:00 GMT+0 - Resolved - This incident was caused by insufficient cluster capacity and is now resolved. Type: Incident

Duration: 9 minutes

Affected Components:

<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> ]]> Wed, 3 Jul 2024 11:50:00 +0000 https://siffletdata-status.com/incident/cly5srk0g53910hyn5fm3679tf https://siffletdata-status.com/incident/cly5srk0g53910hyn5fm3679tf Business Glossary unavailable Type: Incident Duration: 52 minutes Affected Components: eu-west-1-b - Web application, eu-west-1-a - Web application, us-east-1-a - Web application, ap-southeast-1-a - Web application Feb 6, 16:22:29 GMT+0 - Resolved - This incident has been resolved. Feb 6, 15:30:00 GMT+0 - Identified - 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. Type: Incident

Duration: 52 minutes

Affected Components: , , ,

<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> ]]> Tue, 6 Feb 2024 15:30:00 +0000 https://siffletdata-status.com/incident/clsaj4wsg0393bcosobelkvfa https://siffletdata-status.com/incident/clsaj4wsg0393bcosobelkvfa Delay in executing monitoring rules or ingestion jobs Type: Incident Duration: 7 hours and 50 minutes Affected Components: us-east-1-a - Integrations, eu-west-1-b - Integrations, us-east-1-a- Datasource monitoring, eu-west-1-a - Integrations, ap-southeast-1-a - Datasource monitoring, eu-west-1-b - Datasource monitoring, ap-southeast-1-a - Integrations, eu-west-1-a - Datasource monitoring Dec 8, 16:51:25 GMT+0 - Resolved - This incident has been resolved. Dec 8, 09:01:08 GMT+0 - Investigating - Monitors and metatadata ingestion jobs are experiencing delays. Some monitors may not be run in a timely manner. We're investigating this issue. (a previous version of this message mentioned only the eu-west-1-a cell) Dec 8, 09:42:22 GMT+0 - Investigating - Monitors are now running as usual. Some metadata ingestion jobs may still be delayed for a few customers. Dec 8, 11:44:14 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Type: Incident

Duration: 7 hours and 50 minutes

Affected Components: , , , , , , ,

<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'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> ]]> Fri, 8 Dec 2023 09:01:08 +0000 https://siffletdata-status.com/incident/clpwedk3f3967b5mwcthaolf1 https://siffletdata-status.com/incident/clpwedk3f3967b5mwcthaolf1 New users cannot log in to Sifflet when not assigned domain "All” Type: Incident Duration: 19 minutes Affected Components: ap-southeast-1-a - Web application, eu-west-1-b - Web application, eu-west-1-a - Web application, us-east-1-a - Web application Oct 30, 13:37:13 GMT+0 - Monitoring - New users (whatever the role) can be created but when logging in, they are instantly logged out if they do not have the "All" domain. If they have the "All domain", the log in works normally Oct 30, 13:56:04 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 19 minutes

Affected Components: , , ,

<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 "All" domain. If they have the "All domain", 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> ]]> Mon, 30 Oct 2023 13:37:13 +0000 https://siffletdata-status.com/incident/clocy2d8r44524b6mxv4zdi4br https://siffletdata-status.com/incident/clocy2d8r44524b6mxv4zdi4br