Incidents reported on status page for SIBYL https://status.sibyl-system.net/ https://d1lppblt9t2x15.cloudfront.net/logos/c5f6f0600ffb1a55877e4ecd7d75cff4.png https://status.sibyl-system.net/ en https://status.sibyl-system.net/ Sat, 20 Dec 2025 21:31:36 +0000 https://status.sibyl-system.net/#9d98c25fde0556cffa4168bd1602c2b70947bd4a121b4caef0d5c25aea905cd3 SIBYL recovered https://status.sibyl-system.net/ Sat, 20 Dec 2025 19:57:09 +0000 https://status.sibyl-system.net/#9d98c25fde0556cffa4168bd1602c2b70947bd4a121b4caef0d5c25aea905cd3 SIBYL went down https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 21:00:00 -0000 https://status.sibyl-system.net/incident/751734#98f45e8cd24b5410664d42f9ac1e700d6fe4ef310fc29ded5f1f32c7b771e9d2 Maintenance completed https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 21:00:00 -0000 https://status.sibyl-system.net/incident/751734#98f45e8cd24b5410664d42f9ac1e700d6fe4ef310fc29ded5f1f32c7b771e9d2 Maintenance completed https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/incident/751734 Sun, 26 Oct 2025 19:08:00 -0000 https://status.sibyl-system.net/incident/751734#1c00ad6de6e9403b65d2da6e4c5442b5d3f0ff5996ca01eb55b6941c229d61cf Physical server will be undergoing a full reboot to apply updates. https://status.sibyl-system.net/ Tue, 07 Oct 2025 18:15:19 +0000 https://status.sibyl-system.net/#140581dfd2244d58b94719230108bd84c0ef97e8ebd53c1160196f2fe72e8337 SIBYL recovered https://status.sibyl-system.net/ Tue, 07 Oct 2025 12:30:25 +0000 https://status.sibyl-system.net/#140581dfd2244d58b94719230108bd84c0ef97e8ebd53c1160196f2fe72e8337 SIBYL went down https://status.sibyl-system.net/incident/724361 Mon, 15 Sep 2025 05:28:00 -0000 https://status.sibyl-system.net/incident/724361#4d9a45c28fa790190d8d3d40241b369fba10610e54216730a8fa9a96dcd652e3 Back online. https://status.sibyl-system.net/incident/724361 Mon, 15 Sep 2025 05:28:00 -0000 https://status.sibyl-system.net/incident/724361#4d9a45c28fa790190d8d3d40241b369fba10610e54216730a8fa9a96dcd652e3 Back online. https://status.sibyl-system.net/ Mon, 15 Sep 2025 05:27:28 +0000 https://status.sibyl-system.net/#cabdffb76e9270f570070c024917fa0feec7901f5df1d2ec13469579d1a38dfa SIBYL recovered https://status.sibyl-system.net/incident/724361 Mon, 15 Sep 2025 05:13:00 -0000 https://status.sibyl-system.net/incident/724361#b1bc74026f115c62710f2f893ce3e577349f5f56520a416fea0bc14c67783fc2 Startup in progress. https://status.sibyl-system.net/incident/724361 Mon, 15 Sep 2025 05:13:00 -0000 https://status.sibyl-system.net/incident/724361#b1bc74026f115c62710f2f893ce3e577349f5f56520a416fea0bc14c67783fc2 Startup in progress. https://status.sibyl-system.net/ Mon, 15 Sep 2025 05:02:45 +0000 https://status.sibyl-system.net/#cabdffb76e9270f570070c024917fa0feec7901f5df1d2ec13469579d1a38dfa SIBYL went down https://status.sibyl-system.net/incident/724361 Mon, 15 Sep 2025 04:54:00 -0000 https://status.sibyl-system.net/incident/724361#36fe63a78e98b3dd9dbd5bcc62d54587d6f8f1556dcc0a935f8eca3922f076a4 Should be back online within 2 hours. https://status.sibyl-system.net/incident/724361 Mon, 15 Sep 2025 04:54:00 -0000 https://status.sibyl-system.net/incident/724361#36fe63a78e98b3dd9dbd5bcc62d54587d6f8f1556dcc0a935f8eca3922f076a4 Should be back online within 2 hours. https://status.sibyl-system.net/ Tue, 29 Jul 2025 21:46:04 +0000 https://status.sibyl-system.net/#ca9dd6423d0a00e6d6ca8e28d26c8f38218ef77e6401397c8fc7f51bf8b6817d SIBYL recovered https://status.sibyl-system.net/ Tue, 29 Jul 2025 21:31:47 +0000 https://status.sibyl-system.net/#ca9dd6423d0a00e6d6ca8e28d26c8f38218ef77e6401397c8fc7f51bf8b6817d SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 08:08:46 +0000 https://status.sibyl-system.net/#9d97ad623ca2b19230182db4e31ad3b31aebe73b3f02c5c607119d5f40a601c4 SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 07:49:55 +0000 https://status.sibyl-system.net/#9d97ad623ca2b19230182db4e31ad3b31aebe73b3f02c5c607119d5f40a601c4 SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 07:00:55 +0000 https://status.sibyl-system.net/#a784f01682f9924b95a617d108f8f46251b52b1e2d92ba56e481a90137ec64da SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 06:46:13 +0000 https://status.sibyl-system.net/#a784f01682f9924b95a617d108f8f46251b52b1e2d92ba56e481a90137ec64da SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 06:00:33 +0000 https://status.sibyl-system.net/#00a98646bf062963179385fbe0958f93abd59e9224bb9a64cb11ecebc906194a SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 05:46:17 +0000 https://status.sibyl-system.net/#00a98646bf062963179385fbe0958f93abd59e9224bb9a64cb11ecebc906194a SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 05:00:06 +0000 https://status.sibyl-system.net/#938fafc9534155cdd6b0692934537d4872ad745d339f5b3cc6b19f800dad368a SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 04:45:31 +0000 https://status.sibyl-system.net/#938fafc9534155cdd6b0692934537d4872ad745d339f5b3cc6b19f800dad368a SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 03:59:46 +0000 https://status.sibyl-system.net/#34cddfc08c7d6b71a92601ee382085cf8bc5ea223c881d0d9000d571a3d39fca SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 03:45:13 +0000 https://status.sibyl-system.net/#34cddfc08c7d6b71a92601ee382085cf8bc5ea223c881d0d9000d571a3d39fca SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 03:01:28 +0000 https://status.sibyl-system.net/#9294a0500d71827a8be4510d60559e7cc84ccd1e3b191e826c32ed49ac5aae30 SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 02:46:58 +0000 https://status.sibyl-system.net/#9294a0500d71827a8be4510d60559e7cc84ccd1e3b191e826c32ed49ac5aae30 SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 02:04:17 +0000 https://status.sibyl-system.net/#b9e6db59290ed00e61e271d8e42c25f220021106d370a68d575daf127eb15370 SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 01:49:46 +0000 https://status.sibyl-system.net/#b9e6db59290ed00e61e271d8e42c25f220021106d370a68d575daf127eb15370 SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 01:00:14 +0000 https://status.sibyl-system.net/#472ba2dbfd40cbb6a8a5de7c559dda67379f3fcfcbff60240bd02d6bae68860b SIBYL recovered https://status.sibyl-system.net/ Tue, 22 Jul 2025 00:46:46 +0000 https://status.sibyl-system.net/#472ba2dbfd40cbb6a8a5de7c559dda67379f3fcfcbff60240bd02d6bae68860b SIBYL went down https://status.sibyl-system.net/ Tue, 22 Jul 2025 00:00:47 +0000 https://status.sibyl-system.net/#23ac8695cc477ba00b44acb9941d1375d9d80cc8385403e0bac542e3438a2ecb SIBYL recovered https://status.sibyl-system.net/ Mon, 21 Jul 2025 23:45:46 +0000 https://status.sibyl-system.net/#23ac8695cc477ba00b44acb9941d1375d9d80cc8385403e0bac542e3438a2ecb SIBYL went down https://status.sibyl-system.net/ Mon, 21 Jul 2025 11:29:53 +0000 https://status.sibyl-system.net/#3afb561e4f2c46098bacb9ef341f214597c3bd186ab1f4a5913895f74cf58c2f SIBYL recovered https://status.sibyl-system.net/incident/623205 Mon, 21 Jul 2025 11:28:00 -0000 https://status.sibyl-system.net/incident/623205#0adf0396fd8c501c9cd476e808b8ca5f770385cca1d40dfbc0216c1930c3376d Resolved https://status.sibyl-system.net/incident/623205 Mon, 21 Jul 2025 11:28:00 -0000 https://status.sibyl-system.net/incident/623205#0adf0396fd8c501c9cd476e808b8ca5f770385cca1d40dfbc0216c1930c3376d Resolved https://status.sibyl-system.net/ Mon, 21 Jul 2025 11:23:41 +0000 https://status.sibyl-system.net/#3afb561e4f2c46098bacb9ef341f214597c3bd186ab1f4a5913895f74cf58c2f SIBYL went down https://status.sibyl-system.net/incident/623205 Mon, 21 Jul 2025 10:15:00 -0000 https://status.sibyl-system.net/incident/623205#beba9a915580d8eeca3ff70cc5f83e475d419cac842f02f4c078547a3f9e3e77 Unknown crashing and failure. https://status.sibyl-system.net/incident/623205 Mon, 21 Jul 2025 10:15:00 -0000 https://status.sibyl-system.net/incident/623205#beba9a915580d8eeca3ff70cc5f83e475d419cac842f02f4c078547a3f9e3e77 Unknown crashing and failure. https://status.sibyl-system.net/ Sun, 20 Jul 2025 15:27:51 +0000 https://status.sibyl-system.net/#be94eb4719c911e1fa1c7fea2895a2dc6f388d21d811a1f2e00d24da6557b72e SIBYL recovered https://status.sibyl-system.net/ Sun, 20 Jul 2025 15:27:45 +0000 https://status.sibyl-system.net/#be94eb4719c911e1fa1c7fea2895a2dc6f388d21d811a1f2e00d24da6557b72e SIBYL went down https://status.sibyl-system.net/incident/613180 Wed, 02 Jul 2025 22:30:00 -0000 https://status.sibyl-system.net/incident/613180#f5ae0ff9368d4e2da6a1c83beb25065aac1d9eccd12e3234a9f10d3e536fbfc9 Maintenance completed https://status.sibyl-system.net/incident/613180 Wed, 02 Jul 2025 22:30:00 -0000 https://status.sibyl-system.net/incident/613180#f5ae0ff9368d4e2da6a1c83beb25065aac1d9eccd12e3234a9f10d3e536fbfc9 Maintenance completed https://status.sibyl-system.net/incident/613180 Wed, 02 Jul 2025 17:00:00 -0000 https://status.sibyl-system.net/incident/613180#7955e96accfebfdadc3103528f741e35a5cde883b3d5136bb5184533c145bebb This should hopefully be the last maintenance required to address power delivery issues. https://status.sibyl-system.net/incident/613180 Wed, 02 Jul 2025 17:00:00 -0000 https://status.sibyl-system.net/incident/613180#7955e96accfebfdadc3103528f741e35a5cde883b3d5136bb5184533c145bebb This should hopefully be the last maintenance required to address power delivery issues. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 02:59:46 -0000 https://status.sibyl-system.net/incident/611352#9e7ac64893153135cdaf56666d143a56bb3b12371790673873057483722c7fcb Maintenance completed https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 02:59:46 -0000 https://status.sibyl-system.net/incident/611352#9e7ac64893153135cdaf56666d143a56bb3b12371790673873057483722c7fcb Maintenance completed https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/611352 Mon, 30 Jun 2025 00:00:26 -0000 https://status.sibyl-system.net/incident/611352#68c481ff0690689690c3c5f378a623bfeb8cc6be016b3ef22df4de1532a905ed Physical server maintenance will be carried out in order to diagnose and resolve a particular issue regarding power. https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 21:00:00 -0000 https://status.sibyl-system.net/incident/578286#80c1baa1f1168067b1f37cd91c3179fba795235bd9bd985d089a4499c6e77140 Maintenance completed https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 21:00:00 -0000 https://status.sibyl-system.net/incident/578286#80c1baa1f1168067b1f37cd91c3179fba795235bd9bd985d089a4499c6e77140 Maintenance completed https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 19:00:00 -0000 https://status.sibyl-system.net/incident/578286#cdb1b97f508e69e0a232cc414a2df2e718f48c6e060ff25711fa74ef6381a96a Scheduled maintenance will be performed to resolve issues and perform upgrades. https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 19:00:00 -0000 https://status.sibyl-system.net/incident/578286#cdb1b97f508e69e0a232cc414a2df2e718f48c6e060ff25711fa74ef6381a96a Scheduled maintenance will be performed to resolve issues and perform upgrades. https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 19:00:00 -0000 https://status.sibyl-system.net/incident/578286#cdb1b97f508e69e0a232cc414a2df2e718f48c6e060ff25711fa74ef6381a96a Scheduled maintenance will be performed to resolve issues and perform upgrades. https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 19:00:00 -0000 https://status.sibyl-system.net/incident/578286#cdb1b97f508e69e0a232cc414a2df2e718f48c6e060ff25711fa74ef6381a96a Scheduled maintenance will be performed to resolve issues and perform upgrades. https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 19:00:00 -0000 https://status.sibyl-system.net/incident/578286#cdb1b97f508e69e0a232cc414a2df2e718f48c6e060ff25711fa74ef6381a96a Scheduled maintenance will be performed to resolve issues and perform upgrades. https://status.sibyl-system.net/incident/578286 Tue, 27 May 2025 19:00:00 -0000 https://status.sibyl-system.net/incident/578286#cdb1b97f508e69e0a232cc414a2df2e718f48c6e060ff25711fa74ef6381a96a Scheduled maintenance will be performed to resolve issues and perform upgrades. https://status.sibyl-system.net/incident/559765 Sat, 10 May 2025 21:21:00 -0000 https://status.sibyl-system.net/incident/559765#f83c5c05743e78e782ea7772d2572529e505aefdc7c820f1ea165c4b35c4f85e Startup complete, now working as expected. https://status.sibyl-system.net/incident/559765 Sat, 10 May 2025 21:21:00 -0000 https://status.sibyl-system.net/incident/559765#f83c5c05743e78e782ea7772d2572529e505aefdc7c820f1ea165c4b35c4f85e Startup complete, now working as expected. https://status.sibyl-system.net/incident/559765 Sat, 10 May 2025 20:19:00 -0000 https://status.sibyl-system.net/incident/559765#5a5f811be245591bf2fb4d6edb984a2cfdb6acc40c11a4d639f6a3fc721327e3 Physical server power restored, running full diagnostics and then will proceed with startup. https://status.sibyl-system.net/incident/559765 Sat, 10 May 2025 20:19:00 -0000 https://status.sibyl-system.net/incident/559765#5a5f811be245591bf2fb4d6edb984a2cfdb6acc40c11a4d639f6a3fc721327e3 Physical server power restored, running full diagnostics and then will proceed with startup. https://status.sibyl-system.net/incident/559765 Sat, 10 May 2025 16:39:00 -0000 https://status.sibyl-system.net/incident/559765#3ac74533d84c53b5156dc7351d3136fb41ceff865c02f8c9bb289f258aa44b49 Physical server shut down due to unknown reason, investigation underway. https://status.sibyl-system.net/incident/559765 Sat, 10 May 2025 16:39:00 -0000 https://status.sibyl-system.net/incident/559765#3ac74533d84c53b5156dc7351d3136fb41ceff865c02f8c9bb289f258aa44b49 Physical server shut down due to unknown reason, investigation underway. https://status.sibyl-system.net/incident/547443 Fri, 18 Apr 2025 19:52:25 -0000 https://status.sibyl-system.net/incident/547443#40f907107c2596dbb9b04293b883e219da0c6c392678f786b9a2cfc2b13ae2af Maintenance completed https://status.sibyl-system.net/incident/547443 Fri, 18 Apr 2025 19:52:25 -0000 https://status.sibyl-system.net/incident/547443#40f907107c2596dbb9b04293b883e219da0c6c392678f786b9a2cfc2b13ae2af Maintenance completed https://status.sibyl-system.net/incident/547443 Fri, 18 Apr 2025 18:30:00 -0000 https://status.sibyl-system.net/incident/547443#ac5d2fe71f9ff60c9369ae86f3aded8e68794bc6c95d61626bcd8ba56a64dc12 Various upgrades will be rolled out to the software and firmware for the physical hardware responsible for hosting SIBYL. All functions will be unavailable during this maintenance cycle, check back to this page regularly as additional updates may be posted. https://status.sibyl-system.net/incident/547443 Fri, 18 Apr 2025 18:30:00 -0000 https://status.sibyl-system.net/incident/547443#ac5d2fe71f9ff60c9369ae86f3aded8e68794bc6c95d61626bcd8ba56a64dc12 Various upgrades will be rolled out to the software and firmware for the physical hardware responsible for hosting SIBYL. All functions will be unavailable during this maintenance cycle, check back to this page regularly as additional updates may be posted. https://status.sibyl-system.net/incident/547443 Fri, 18 Apr 2025 18:30:00 -0000 https://status.sibyl-system.net/incident/547443#ac5d2fe71f9ff60c9369ae86f3aded8e68794bc6c95d61626bcd8ba56a64dc12 Various upgrades will be rolled out to the software and firmware for the physical hardware responsible for hosting SIBYL. All functions will be unavailable during this maintenance cycle, check back to this page regularly as additional updates may be posted. https://status.sibyl-system.net/incident/547443 Fri, 18 Apr 2025 18:30:00 -0000 https://status.sibyl-system.net/incident/547443#ac5d2fe71f9ff60c9369ae86f3aded8e68794bc6c95d61626bcd8ba56a64dc12 Various upgrades will be rolled out to the software and firmware for the physical hardware responsible for hosting SIBYL. All functions will be unavailable during this maintenance cycle, check back to this page regularly as additional updates may be posted. https://status.sibyl-system.net/incident/517566 Sun, 23 Feb 2025 17:10:31 -0000 https://status.sibyl-system.net/incident/517566#19d8abe9727f99985d9b70e9be2b4868de547fd484f5af16c17cffd1d4a0cd2d Maintenance completed https://status.sibyl-system.net/incident/517566 Sun, 23 Feb 2025 17:10:31 -0000 https://status.sibyl-system.net/incident/517566#19d8abe9727f99985d9b70e9be2b4868de547fd484f5af16c17cffd1d4a0cd2d Maintenance completed https://status.sibyl-system.net/incident/517566 Sun, 23 Feb 2025 08:10:31 -0000 https://status.sibyl-system.net/incident/517566#41d556bb106fabe698c353ebacb5be31cae3d40acf7265b9cbb5b457b51eb317 SIBYL will be undergoing upgrades to its backend infrastructure, all services will be offline until maintenance is complete. https://status.sibyl-system.net/incident/517566 Sun, 23 Feb 2025 08:10:31 -0000 https://status.sibyl-system.net/incident/517566#41d556bb106fabe698c353ebacb5be31cae3d40acf7265b9cbb5b457b51eb317 SIBYL will be undergoing upgrades to its backend infrastructure, all services will be offline until maintenance is complete. https://status.sibyl-system.net/incident/312976 Mon, 15 Jan 2024 18:00:00 -0000 https://status.sibyl-system.net/incident/312976#c65344a086a46ed1c605606a9b3dd27d3a4e6066a1744de23c89faffc7f6c153 Maintenance completed https://status.sibyl-system.net/incident/312976 Mon, 15 Jan 2024 18:00:00 -0000 https://status.sibyl-system.net/incident/312976#c65344a086a46ed1c605606a9b3dd27d3a4e6066a1744de23c89faffc7f6c153 Maintenance completed https://status.sibyl-system.net/incident/312976 Mon, 15 Jan 2024 12:00:00 -0000 https://status.sibyl-system.net/incident/312976#c41acef07fc77a34443f99f8bdcf96eaba28a1388ad861003f77abfcc9986112 An infrastructure overhaul will be taking place. SIBYL and it's databases will be offline, updates will be given on this page. 12:00 GMT - SIBYL taken offline, database spinning down. 12:01 GMT - Database offline, shutting down instance for re-enrollment. 12:06 GMT - Instance stopped, re-enrollment requested. 12:08 GMT - Re-enrollment complete, instance spinning up. 12:08 GMT - Provisioning second instance. 12:09 GMT - Platform out of capacity for DB2 instance, investigating. 12:32 GMT - DB2 instance unable to be provisioned, workaround will be applied for next maintenance. 12:38 GMT - Core instance provisioned, transferring SIBYL to core instance. Original instance now designated as DB1. 12:47 GMT - DB1 database start confirmed. 12:50 GMT - SIBYL transferred to dedicated core instance. 12:53 GMT - SIBYL startup command sent, waiting for heartbeat. 13:38 GMT - SIBYL heartbeat confirmed, database connection also confirmed. Monitoring throughput until SIBYL is stable. 14:07 GMT - Reported memory bottleneck on new core instance, average transaction time is not stabilising. 14:18 GMT - Average transaction time unsatisfactory, re-enrolling core instance. 15:04 GMT - New core instance enrolled, transferring SIBYL. 15:36 GMT - SIBYL transferred, waiting for heartbeat. 15:40 GMT - Heartbeat confirmed, database link confirmed. 15:52 GMT - Encountering odd network issues with core instance. 16:37 GMT - Odd network issues are still persisting. 17:55 GMT - Issue resolved, all systems operational. 17:57 GMT - Maintenance concluded. Conclusion: Dedicated DB1 instance was deployed, DB2 was unable to be deployed due to capacity errors. Dedicated SIBYL core was deployed. https://status.sibyl-system.net/incident/312976 Mon, 15 Jan 2024 12:00:00 -0000 https://status.sibyl-system.net/incident/312976#c41acef07fc77a34443f99f8bdcf96eaba28a1388ad861003f77abfcc9986112 An infrastructure overhaul will be taking place. SIBYL and it's databases will be offline, updates will be given on this page. 12:00 GMT - SIBYL taken offline, database spinning down. 12:01 GMT - Database offline, shutting down instance for re-enrollment. 12:06 GMT - Instance stopped, re-enrollment requested. 12:08 GMT - Re-enrollment complete, instance spinning up. 12:08 GMT - Provisioning second instance. 12:09 GMT - Platform out of capacity for DB2 instance, investigating. 12:32 GMT - DB2 instance unable to be provisioned, workaround will be applied for next maintenance. 12:38 GMT - Core instance provisioned, transferring SIBYL to core instance. Original instance now designated as DB1. 12:47 GMT - DB1 database start confirmed. 12:50 GMT - SIBYL transferred to dedicated core instance. 12:53 GMT - SIBYL startup command sent, waiting for heartbeat. 13:38 GMT - SIBYL heartbeat confirmed, database connection also confirmed. Monitoring throughput until SIBYL is stable. 14:07 GMT - Reported memory bottleneck on new core instance, average transaction time is not stabilising. 14:18 GMT - Average transaction time unsatisfactory, re-enrolling core instance. 15:04 GMT - New core instance enrolled, transferring SIBYL. 15:36 GMT - SIBYL transferred, waiting for heartbeat. 15:40 GMT - Heartbeat confirmed, database link confirmed. 15:52 GMT - Encountering odd network issues with core instance. 16:37 GMT - Odd network issues are still persisting. 17:55 GMT - Issue resolved, all systems operational. 17:57 GMT - Maintenance concluded. Conclusion: Dedicated DB1 instance was deployed, DB2 was unable to be deployed due to capacity errors. Dedicated SIBYL core was deployed. https://status.sibyl-system.net/incident/282829 Mon, 06 Nov 2023 19:46:36 -0000 https://status.sibyl-system.net/incident/282829#567ed940c190eb396f673e1b79877e91a37c6bef93b95912183126b96eeccf92 Maintenance completed https://status.sibyl-system.net/incident/282829 Mon, 06 Nov 2023 19:46:36 -0000 https://status.sibyl-system.net/incident/282829#567ed940c190eb396f673e1b79877e91a37c6bef93b95912183126b96eeccf92 Maintenance completed https://status.sibyl-system.net/incident/282829 Mon, 06 Nov 2023 11:30:00 -0000 https://status.sibyl-system.net/incident/282829#9e8968699dcb634b43d8265f4322353b2162e13383304fa28e5c1a0991a96d60 To improve the overall service of SIBYL, maintenance will be performed on both databases as well as the host itself. During the maintenance SIBYL will be unavailable as many of it's services rely on the database. As of this time the ETA is unknown but will be a few hours minimum. You will be able to see updates of the maintenance by checking back to this page regularly. https://status.sibyl-system.net/incident/282829 Mon, 06 Nov 2023 11:30:00 -0000 https://status.sibyl-system.net/incident/282829#9e8968699dcb634b43d8265f4322353b2162e13383304fa28e5c1a0991a96d60 To improve the overall service of SIBYL, maintenance will be performed on both databases as well as the host itself. During the maintenance SIBYL will be unavailable as many of it's services rely on the database. As of this time the ETA is unknown but will be a few hours minimum. You will be able to see updates of the maintenance by checking back to this page regularly. https://status.sibyl-system.net/incident/282829 Mon, 06 Nov 2023 11:30:00 -0000 https://status.sibyl-system.net/incident/282829#9e8968699dcb634b43d8265f4322353b2162e13383304fa28e5c1a0991a96d60 To improve the overall service of SIBYL, maintenance will be performed on both databases as well as the host itself. During the maintenance SIBYL will be unavailable as many of it's services rely on the database. As of this time the ETA is unknown but will be a few hours minimum. You will be able to see updates of the maintenance by checking back to this page regularly. https://status.sibyl-system.net/incident/282829 Mon, 06 Nov 2023 11:30:00 -0000 https://status.sibyl-system.net/incident/282829#9e8968699dcb634b43d8265f4322353b2162e13383304fa28e5c1a0991a96d60 To improve the overall service of SIBYL, maintenance will be performed on both databases as well as the host itself. During the maintenance SIBYL will be unavailable as many of it's services rely on the database. As of this time the ETA is unknown but will be a few hours minimum. You will be able to see updates of the maintenance by checking back to this page regularly.