SPLRGE Status - Incident history https://status.splrge.dev SPLRGE Mon, 20 Jul 2026 10:54:56 +0000 fsn01 • Network issues Type: Incident Duration: 43 minutes Affected Components: S3 Storage, Hosting, Servers · FSN01, Docker Container Registry, Analytics Jul 20, 11:03:34 GMT+0 - Identified - A fix is currently being deployed by our supplier. We expect to have all services back in less than 30min. Sorry for the inconvenience. Jul 20, 11:19:21 GMT+0 - Monitoring - All our services are back to normal. We're still monitoring the situation. Jul 20, 10:54:56 GMT+0 - Identified - We're working with our supplier to fix a network issue on our infrastructure. We're sorry for the inconvenience. ETA > 30min Jul 20, 11:07:27 GMT+0 - Identified - S3 is partially back in service. There is still some issues with write operations. Jul 20, 11:37:49 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 43 minutes

Affected Components: , , , ,

<p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>11:03:34</var> GMT+0</small><br><strong>Identified</strong> - A fix is currently being deployed by our supplier. We expect to have all services back in less than 30min. Sorry for the inconvenience. .</p> <p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>11:19:21</var> GMT+0</small><br><strong>Monitoring</strong> - All our services are back to normal. We're still monitoring the situation. .</p> <p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>10:54:56</var> GMT+0</small><br><strong>Identified</strong> - We're working with our supplier to fix a network issue on our infrastructure. We're sorry for the inconvenience. ETA > 30min .</p> <p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>11:07:27</var> GMT+0</small><br><strong>Identified</strong> - S3 is partially back in service. There is still some issues with write operations. .</p> <p><small>Jul <var data-var='date'> 20</var>, <var data-var='time'>11:37:49</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 20 Jul 2026 10:54:56 +0000 https://status.splrge.dev/incident/cmrt3ye3m08oi0kmpif1j70ah https://status.splrge.dev/incident/cmrt3ye3m08oi0kmpif1j70ah Registry · Service disruptions Type: Incident Duration: 21 minutes Affected Components: Docker Container Registry Feb 15, 00:48:59 GMT+0 - Identified - We are continuing to work on a fix for this incident. Feb 15, 01:10:06 GMT+0 - Resolved - This incident has been resolved. Sorry for the inconvenience. Type: Incident

Duration: 21 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 15</var>, <var data-var='time'>00:48:59</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 15</var>, <var data-var='time'>01:10:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Sorry for the inconvenience. .</p> ]]> Sun, 15 Feb 2026 00:48:59 +0000 https://status.splrge.dev/incident/cmln124bf0cg083cser9c9ywa https://status.splrge.dev/incident/cmln124bf0cg083cser9c9ywa Registry · Difficulty with SSL connection establishment Type: Incident Duration: 10 minutes Affected Components: Docker Container Registry Feb 5, 19:56:36 GMT+0 - Investigating - We are currently investigating this incident. Feb 5, 20:02:16 GMT+0 - Identified - The problem has been identified. We are continuing to work on a fix for this incident. Feb 5, 20:06:10 GMT+0 - Monitoring - We implemented a fix, the registry is now online. Sorry for the inconvenience. Feb 5, 20:06:46 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>19:56:36</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>20:02:16</var> GMT+0</small><br><strong>Identified</strong> - The problem has been identified. We are continuing to work on a fix for this incident..</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>20:06:10</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix, the registry is now online. Sorry for the inconvenience. .</p> <p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>20:06:46</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 5 Feb 2026 19:56:36 +0000 https://status.splrge.dev/incident/cml9vnhin00w320o7qfwk1j1q https://status.splrge.dev/incident/cml9vnhin00w320o7qfwk1j1q Registry · Difficulty with SSL connection establishment Type: Incident Duration: 5 minutes Affected Components: Docker Container Registry Oct 27, 19:51:56 GMT+0 - Identified - We are continuing to work on a fix for this incident. Sorry for the inconvenience. It should be fixed in the next 10 minutes. Oct 27, 19:57:00 GMT+0 - Resolved - We resolved the issue. All connections to the registry are now fully operational. Type: Incident

Duration: 5 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>19:51:56</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. Sorry for the inconvenience. It should be fixed in the next 10 minutes. .</p> <p><small>Oct <var data-var='date'> 27</var>, <var data-var='time'>19:57:00</var> GMT+0</small><br><strong>Resolved</strong> - We resolved the issue. All connections to the registry are now fully operational. .</p> ]]> Mon, 27 Oct 2025 19:51:56 +0000 https://status.splrge.dev/incident/cmh9k0eka044r1qasc5h7wdwi https://status.splrge.dev/incident/cmh9k0eka044r1qasc5h7wdwi S3 · Connection to console is disrupted Type: Incident Duration: 2 minutes Affected Components: S3 Storage Oct 19, 14:15:08 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 19, 14:17:04 GMT+0 - Resolved - The incident has been resolved. Sorry for the inconvenience. Type: Incident

Duration: 2 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>14:15:08</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Oct <var data-var='date'> 19</var>, <var data-var='time'>14:17:04</var> GMT+0</small><br><strong>Resolved</strong> - The incident has been resolved. Sorry for the inconvenience. .</p> ]]> Sun, 19 Oct 2025 14:15:08 +0000 https://status.splrge.dev/incident/cmgxsggyn00kgcj5vdgfoggkb https://status.splrge.dev/incident/cmgxsggyn00kgcj5vdgfoggkb IDENTITY • Disrupted service Type: Incident Duration: 52 minutes Affected Components: Docker Container Registry, S3 Storage Aug 10, 08:47:19 GMT+0 - Identified - We have found the issue and are now working on fixing it. Aug 10, 08:44:46 GMT+0 - Investigating - We are aware of connection issues with our identity service that may cause problems accessing some of our services. Aug 10, 08:57:11 GMT+0 - Monitoring - The issue has been fixed and everything is back to normal. Sorry for the inconvenience. Aug 10, 09:36:29 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 52 minutes

Affected Components: ,

<p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>08:47:19</var> GMT+0</small><br><strong>Identified</strong> - We have found the issue and are now working on fixing it..</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>08:44:46</var> GMT+0</small><br><strong>Investigating</strong> - We are aware of connection issues with our identity service that may cause problems accessing some of our services..</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>08:57:11</var> GMT+0</small><br><strong>Monitoring</strong> - The issue has been fixed and everything is back to normal. Sorry for the inconvenience. .</p> <p><small>Aug <var data-var='date'> 10</var>, <var data-var='time'>09:36:29</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 10 Aug 2025 08:44:46 +0000 https://status.splrge.dev/incident/cme5fu0e203zr12g2p62d09fq https://status.splrge.dev/incident/cme5fu0e203zr12g2p62d09fq Maintenance · Improve registry CDN Type: Maintenance Duration: 2 hours and 13 minutes Affected Components: Docker Container Registry Jul 29, 19:00:16 GMT+0 - Completed - Maintenance has completed successfully. Jul 29, 16:47:37 GMT+0 - Identified - Maintenance has been rescheduled and is starting now. Jul 29, 19:00:00 GMT+0 - Identified - A maintenance is required on our infrastructure to improve our service quality. We apologise for the inconvenience. Type: Maintenance

Duration: 2 hours and 13 minutes

Affected Components:

<p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>19:00:16</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>16:47:37</var> GMT+0</small><br><strong>Identified</strong> - Maintenance has been rescheduled and is starting now..</p> <p><small>Jul <var data-var='date'> 29</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Identified</strong> - A maintenance is required on our infrastructure to improve our service quality. We apologise for the inconvenience. .</p> ]]> Tue, 29 Jul 2025 19:00:00 +0000 https://status.splrge.dev/maintenance/cmdogxhtk00404n64xelvlqla https://status.splrge.dev/maintenance/cmdogxhtk00404n64xelvlqla Services unavailable Type: Incident Duration: 12 minutes Affected Components: Analytics, S3 Storage, Servers · FSN01, URL Shortner, Docker Container Registry Apr 7, 19:23:40 GMT+0 - Identified - We are continuing to work on a fix for this incident. ETA: 1 to 2 hours Apr 7, 19:35:57 GMT+0 - Resolved - This incident has been resolved. Apr 7, 19:28:37 GMT+0 - Monitoring - Problem solved. Services restarted. Type: Incident

Duration: 12 minutes

Affected Components: , , , ,

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:23:40</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident. ETA: 1 to 2 hours.</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:35:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>19:28:37</var> GMT+0</small><br><strong>Monitoring</strong> - Problem solved. Services restarted..</p> ]]> Mon, 7 Apr 2025 19:23:40 +0000 https://status.splrge.dev/incident/cm97gm5ba0002swpnhphwfetk https://status.splrge.dev/incident/cm97gm5ba0002swpnhphwfetk ALL • Unavailable service. Type: Incident Duration: 4 hours and 7 minutes Affected Components: Analytics, S3 Storage, Servers · FSN01 Mar 27, 23:00:00 GMT+0 - Resolved - This incident has been resolved. Mar 27, 20:29:12 GMT+0 - Monitoring - Problem has been solved. We'll monitor the situation until tomorrow. Mar 27, 19:08:37 GMT+0 - Identified - The problem has been identified. We're working with our provider to get everything back to normal. Sorry for the inconvenience. Mar 27, 18:52:42 GMT+0 - Investigating - We are currently investigating on an incident with our services. Type: Incident

Duration: 4 hours and 7 minutes

Affected Components: , ,

<p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>23:00:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>20:29:12</var> GMT+0</small><br><strong>Monitoring</strong> - Problem has been solved. We'll monitor the situation until tomorrow. .</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>19:08:37</var> GMT+0</small><br><strong>Identified</strong> - The problem has been identified. We're working with our provider to get everything back to normal. Sorry for the inconvenience. .</p> <p><small>Mar <var data-var='date'> 27</var>, <var data-var='time'>18:52:42</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating on an incident with our services..</p> ]]> Thu, 27 Mar 2025 18:52:42 +0000 https://status.splrge.dev/incident/cm8rpny2p001iyzqqw7lpjiak https://status.splrge.dev/incident/cm8rpny2p001iyzqqw7lpjiak Investigation into network slowness Type: Maintenance Duration: 1 hour Affected Components: Analytics, S3 Storage, Servers · FSN01 Mar 5, 21:20:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. Mar 5, 21:20:01 GMT+0 - Identified - Maintenance is now in progress Mar 5, 22:20:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 1 hour

Affected Components: , ,

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>21:20:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during that time..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>21:20:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>22:20:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Wed, 5 Mar 2025 21:20:00 +0000 https://status.splrge.dev/maintenance/cm7wc6q9y001911aj1xsvcwb6 https://status.splrge.dev/maintenance/cm7wc6q9y001911aj1xsvcwb6 Maintenance · Internal tool upgrade Type: Maintenance Duration: 11 minutes Affected Components: Servers · FSN01 Feb 2, 19:10:25 GMT+0 - Identified - We update an internal tool on our infrastructure, public tools should not be affected and no downtime should occur. Feb 2, 19:21:41 GMT+0 - Completed - Maintenance is complete Type: Maintenance

Duration: 11 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:10:25</var> GMT+0</small><br><strong>Identified</strong> - We update an internal tool on our infrastructure, public tools should not be affected and no downtime should occur..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:21:41</var> GMT+0</small><br><strong>Completed</strong> - Maintenance is complete.</p> ]]> Sun, 2 Feb 2025 19:10:25 +0000 https://status.splrge.dev/maintenance/cm6o01473000wr823gj7vlgn1 https://status.splrge.dev/maintenance/cm6o01473000wr823gj7vlgn1 Maintenance · Disk change on our S3 storage Type: Maintenance Duration: 20 minutes Affected Components: S3 Storage Jun 21, 16:08:00 GMT+0 - Identified - A maintenance is required on our infrastructure to improve our service quality. We apologise for the inconvenience. Jun 21, 16:27:57 GMT+0 - Completed - The maintenance is successfully completed. Jun 21, 16:08:01 GMT+0 - Identified - Maintenance is now in progress Type: Maintenance

Duration: 20 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>16:08:00</var> GMT+0</small><br><strong>Identified</strong> - A maintenance is required on our infrastructure to improve our service quality. We apologise for the inconvenience. .</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>16:27:57</var> GMT+0</small><br><strong>Completed</strong> - The maintenance is successfully completed. .</p> <p><small>Jun <var data-var='date'> 21</var>, <var data-var='time'>16:08:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> ]]> Fri, 21 Jun 2024 16:08:00 +0000 https://status.splrge.dev/maintenance/clxovwfka95700bloge9ke8crg https://status.splrge.dev/maintenance/clxovwfka95700bloge9ke8crg Maintenance · Main node migration Type: Maintenance Duration: 6 hours and 57 minutes Affected Components: Analytics, S3 Storage Jun 18, 17:47:28 GMT+0 - Identified - Our analytics platform is successfully migrated. We're working on the migration of our S3 platform. Jun 18, 19:27:13 GMT+0 - Completed - Our S3 platform is successfully migrated. All our production websites are operationnal. We're still migrating some of our internal tools. Jun 18, 15:38:25 GMT+0 - Identified - We are experiencing some difficulties, and the maintenance period has been extended. Jun 18, 12:30:00 GMT+0 - Identified - We are starting maintenance Jun 17, 16:30:00 GMT+0 - Identified - Due to the difficulties we encountered with our service provider, maintenance will be performed later. Jun 17, 12:30:00 GMT+0 - Identified - A maintenance is required on our infrastructure to improve our service quality. We will migrate some of our services to a more powerful server. We apologise for the inconvenience. Type: Maintenance

Duration: 6 hours and 57 minutes

Affected Components: ,

<p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>17:47:28</var> GMT+0</small><br><strong>Identified</strong> - Our analytics platform is successfully migrated. We're working on the migration of our S3 platform. .</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>19:27:13</var> GMT+0</small><br><strong>Completed</strong> - Our S3 platform is successfully migrated. All our production websites are operationnal. We're still migrating some of our internal tools. .</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>15:38:25</var> GMT+0</small><br><strong>Identified</strong> - We are experiencing some difficulties, and the maintenance period has been extended..</p> <p><small>Jun <var data-var='date'> 18</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are starting maintenance.</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>16:30:00</var> GMT+0</small><br><strong>Identified</strong> - Due to the difficulties we encountered with our service provider, maintenance will be performed later. .</p> <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Identified</strong> - A maintenance is required on our infrastructure to improve our service quality. We will migrate some of our services to a more powerful server. We apologise for the inconvenience..</p> ]]> Mon, 17 Jun 2024 12:30:00 +0000 https://status.splrge.dev/maintenance/clxhznymd598538c8ofe2ovn0b0 https://status.splrge.dev/maintenance/clxhznymd598538c8ofe2ovn0b0