Incidents reported on status page for AS205126 https://status.as205126.net/ en https://status.as205126.net/ Tue, 30 Jun 2026 00:44:48 +0000 https://status.as205126.net/#8f50294cffa81f860fdb911a77299d214102cc6ab5782219778719147851eb10 AS205126 - cha recovered https://status.as205126.net/ Tue, 30 Jun 2026 00:42:07 +0000 https://status.as205126.net/#8f50294cffa81f860fdb911a77299d214102cc6ab5782219778719147851eb10 AS205126 - cha went down https://status.as205126.net/incident/929988 Sun, 21 Jun 2026 00:38:00 -0000 https://status.as205126.net/incident/929988#29f7c4382b30114aa84c01d67510347a6c8e94cd6bb4b44012309a90e83f9b44 Resolved. https://status.as205126.net/ Sun, 21 Jun 2026 00:34:14 +0000 https://status.as205126.net/#eef6d08638db77c4c129dbc9be9c1067e32d4d8adcf6604fd38476a00020a7bd Load balancer recovered https://status.as205126.net/incident/929988 Sun, 21 Jun 2026 00:32:00 -0000 https://status.as205126.net/incident/929988#11326947552fba0f095ac6fe60bb6a4d7fb28fb3f6e27dc70cb6fda21e695ee0 We've implemented the fixed. Monitoring. https://status.as205126.net/incident/929988 Sun, 21 Jun 2026 00:30:00 -0000 https://status.as205126.net/incident/929988#9d78126140a9db2a8e969e2a56d89341de88f654944090ec6c3cee93a5c837b4 We noticed that our load balancer banned one of our node ip. We are working on a fix https://status.as205126.net/ Sun, 21 Jun 2026 00:28:41 +0000 https://status.as205126.net/#eef6d08638db77c4c129dbc9be9c1067e32d4d8adcf6604fd38476a00020a7bd Load balancer went down https://status.as205126.net/incident/929988 Sun, 21 Jun 2026 00:27:00 -0000 https://status.as205126.net/incident/929988#411ca8a7ae0eef3b6ab1339d17c0957f087debe60f69860c448a43f1100371e4 One of our node cannot contact the load balancer anymore. Services in this status page are not disturbed. https://status.as205126.net/incident/927089 Wed, 17 Jun 2026 21:36:36 -0000 https://status.as205126.net/incident/927089#cdc71d7821f32a538c68957ac409b271e324462d8e517f817c98479e25b00bc5 We are updating our VPN software https://status.as205126.net/ Sun, 14 Jun 2026 03:55:05 +0000 https://status.as205126.net/#c42bc3038c4ed25b9e40cffa77c80982f7c3058123de38d09b5e6b8a54489ace Load balancer recovered https://status.as205126.net/ Sun, 14 Jun 2026 03:49:38 +0000 https://status.as205126.net/#c42bc3038c4ed25b9e40cffa77c80982f7c3058123de38d09b5e6b8a54489ace Load balancer went down https://status.as205126.net/incident/919275 Wed, 10 Jun 2026 00:00:00 -0000 https://status.as205126.net/incident/919275#dabd161f8a78201e197f3b986b99bd895a3554bb7318332ad494a0641dccf429 Issue is now resolved. https://status.as205126.net/ Tue, 09 Jun 2026 23:59:55 +0000 https://status.as205126.net/#0f0f81c1d6ead42ae8555e85256841160872e70ea2b5c3475738cf0a62a79c04 AS205126 - cha recovered https://status.as205126.net/ Tue, 09 Jun 2026 23:56:42 +0000 https://status.as205126.net/#a6c58e67a8605c9f111f968cafa489b5fdb78b4d04b80a93c5d6cccec78abbf5 as205126.net recovered https://status.as205126.net/incident/919275 Tue, 09 Jun 2026 23:50:00 -0000 https://status.as205126.net/incident/919275#0326b6a8c2168376f4a43c9de0268489ca9325a21f4b4a33707563b52790747e the faulty node has been marked as unhealthy to lb. so the load balancer is now 'healthy' by touting the workflow to other nodes. https://status.as205126.net/ Tue, 09 Jun 2026 23:19:41 +0000 https://status.as205126.net/#481757ade33fe73b46b32ec7b80ba5f9ff75cfc38f619a212fdf76d05154bb0b Authentication service recovered https://status.as205126.net/incident/919275 Tue, 09 Jun 2026 23:18:00 -0000 https://status.as205126.net/incident/919275#e18964e7f24649ca6b5fef3d8aee7332e481cb109237136587ab4b99953871d7 Authentication system has been migrated to another node. https://status.as205126.net/incident/919275 Tue, 09 Jun 2026 23:06:00 -0000 https://status.as205126.net/incident/919275#120bad1701b466907ef91425389286356fba6049946fdb6c1dec80aade085749 It seems that the issue comes from the internet provider, which is not us. Registry is available, however it can be disturbed due to authentication server down. https://status.as205126.net/ Tue, 09 Jun 2026 22:54:57 +0000 https://status.as205126.net/#481757ade33fe73b46b32ec7b80ba5f9ff75cfc38f619a212fdf76d05154bb0b Authentication service went down https://status.as205126.net/ Tue, 09 Jun 2026 22:54:21 +0000 https://status.as205126.net/#a6c58e67a8605c9f111f968cafa489b5fdb78b4d04b80a93c5d6cccec78abbf5 as205126.net went down https://status.as205126.net/incident/919275 Tue, 09 Jun 2026 22:53:00 -0000 https://status.as205126.net/incident/919275#42710fda401bdf2661a401979ded64c1cd740b7adfe43b4a725d0e8f171574a6 One of our site is unreachable. We don't know what happens. https://status.as205126.net/ Tue, 09 Jun 2026 22:51:14 +0000 https://status.as205126.net/#0f0f81c1d6ead42ae8555e85256841160872e70ea2b5c3475738cf0a62a79c04 AS205126 - cha went down https://status.as205126.net/ Tue, 09 Jun 2026 22:42:33 +0000 https://status.as205126.net/#43d88eb0a1f65024204cc590cd8ecb2d4d18059a2333d5fbef26f2984a134331 AS205126 - par recovered https://status.as205126.net/ Tue, 09 Jun 2026 22:39:56 +0000 https://status.as205126.net/#43d88eb0a1f65024204cc590cd8ecb2d4d18059a2333d5fbef26f2984a134331 AS205126 - par went down https://status.as205126.net/ Fri, 05 Jun 2026 21:04:47 +0000 https://status.as205126.net/#d532ffd79665b440ce103d8e702b0a5e7f0cbb56707739552a47525bbdcf75e8 Authentication service recovered https://status.as205126.net/ Fri, 05 Jun 2026 20:58:37 +0000 https://status.as205126.net/#d532ffd79665b440ce103d8e702b0a5e7f0cbb56707739552a47525bbdcf75e8 Authentication service went down https://status.as205126.net/incident/914946 Fri, 05 Jun 2026 20:56:00 -0000 https://status.as205126.net/incident/914946#5d5db482a2fa31d83218e6a8a2b066d30a91d64a8791e30313acfe6c31e251f2 We are updating our authentication system. https://status.as205126.net/ Thu, 28 May 2026 15:02:27 +0000 https://status.as205126.net/#7886b31eeb7c9f40cbe1f499117ea4385f012cc716119c362967a7aec42dfeae VPN service recovered https://status.as205126.net/ Thu, 28 May 2026 13:30:30 +0000 https://status.as205126.net/#7886b31eeb7c9f40cbe1f499117ea4385f012cc716119c362967a7aec42dfeae VPN service went down https://status.as205126.net/ Tue, 26 May 2026 23:46:47 +0000 https://status.as205126.net/#49e80482d232f351c6c22ae6df52b0e4491f09fcbcf706096cd60f37c3bbaccc Authentication service recovered https://status.as205126.net/ Tue, 26 May 2026 23:34:09 +0000 https://status.as205126.net/#73f9073c6587ce292bad3083814d7fe989c4fef841851d7d443f54d1bfcb4341 Load balancer recovered https://status.as205126.net/ Tue, 26 May 2026 23:32:46 +0000 https://status.as205126.net/#cb2f6601ec6d84e8f7b1a5acaedb22e943ffb44c53cbe208e7f626f78a9ad6bc Docker&Helm registry recovered https://status.as205126.net/ Tue, 26 May 2026 23:32:44 +0000 https://status.as205126.net/#0e803f4b7d8c0e0299a3d85821b538a95c87c1607a3bde39c6404ba183e1828a AS205126 - cha recovered https://status.as205126.net/ Tue, 26 May 2026 23:32:15 +0000 https://status.as205126.net/#de27b35a6228cd3854666b1d3d77abd021d7338f2a588a7fd6fbad2758b5c3cb as205126.net recovered https://status.as205126.net/ Tue, 26 May 2026 23:31:34 +0000 https://status.as205126.net/#73f9073c6587ce292bad3083814d7fe989c4fef841851d7d443f54d1bfcb4341 Load balancer went down https://status.as205126.net/ Tue, 26 May 2026 23:23:30 +0000 https://status.as205126.net/#6627ab45ed56f3ee381676842e0b750c8b2bee676cde4171b8b21aba97f29705 Git server recovered https://status.as205126.net/ Tue, 26 May 2026 23:19:48 +0000 https://status.as205126.net/#cb2f6601ec6d84e8f7b1a5acaedb22e943ffb44c53cbe208e7f626f78a9ad6bc Docker&Helm registry went down https://status.as205126.net/ Tue, 26 May 2026 23:18:34 +0000 https://status.as205126.net/#49e80482d232f351c6c22ae6df52b0e4491f09fcbcf706096cd60f37c3bbaccc Authentication service went down https://status.as205126.net/ Tue, 26 May 2026 23:18:24 +0000 https://status.as205126.net/#de27b35a6228cd3854666b1d3d77abd021d7338f2a588a7fd6fbad2758b5c3cb as205126.net went down https://status.as205126.net/ Tue, 26 May 2026 23:18:12 +0000 https://status.as205126.net/#0e803f4b7d8c0e0299a3d85821b538a95c87c1607a3bde39c6404ba183e1828a AS205126 - cha went down https://status.as205126.net/ Tue, 26 May 2026 23:17:30 +0000 https://status.as205126.net/#6627ab45ed56f3ee381676842e0b750c8b2bee676cde4171b8b21aba97f29705 Git server went down https://status.as205126.net/ Tue, 26 May 2026 07:39:26 +0000 https://status.as205126.net/#09ec195c534c4e26ca21e41e2b1bc219d83fe4f03e649809b645de0297ac0689 AS205126 - par recovered https://status.as205126.net/ Tue, 26 May 2026 04:03:48 +0000 https://status.as205126.net/#09ec195c534c4e26ca21e41e2b1bc219d83fe4f03e649809b645de0297ac0689 AS205126 - par went down https://status.as205126.net/incident/903255 Sat, 23 May 2026 01:20:32 -0000 https://status.as205126.net/incident/903255#28d26212f80e0673870037118f1d5ec8d336c8bb7532d1ce0dca087cd6e3ff00 We are updating the authentication system https://status.as205126.net/incident/903254 Sat, 23 May 2026 01:20:06 -0000 https://status.as205126.net/incident/903254#c259e1fd5ef40e30314901cdb05540a87276ae280fe481d8094b9be80ee366f7 We are updating as205126.net server https://status.as205126.net/incident/903253 Sat, 23 May 2026 01:19:00 -0000 https://status.as205126.net/incident/903253#f234a0ea47e3ea852536a1b61fa4743a2a9f03678d8c9891971121034d30796b We are updating the load balancer system https://status.as205126.net/incident/903065 Fri, 22 May 2026 20:19:39 -0000 https://status.as205126.net/incident/903065#b6ebbb9cb02dc2d0c673029cece63052e38bb981fe83f913adbe40a8cbf44569 We are updating the git server. https://status.as205126.net/ Thu, 21 May 2026 18:18:28 +0000 https://status.as205126.net/#d7554de4fef361ec26e3b3fe8bd1ebc80d29a2530c1b2c684f76b98ccbf78e4d AS205126 - par recovered https://status.as205126.net/ Thu, 21 May 2026 18:15:49 +0000 https://status.as205126.net/#d7554de4fef361ec26e3b3fe8bd1ebc80d29a2530c1b2c684f76b98ccbf78e4d AS205126 - par went down https://status.as205126.net/incident/902118 Thu, 21 May 2026 18:13:38 -0000 https://status.as205126.net/incident/902118#ddf0c0419be05a07670839692b9952c92be76970b2fd02b308094d1ac511ea84 We are updating a router https://status.as205126.net/ Thu, 21 May 2026 12:32:34 +0000 https://status.as205126.net/#07c4753b21fcb8f8dc00ee1596e1df7505d82a768ed558125d9baf047487bf79 VPN service recovered https://status.as205126.net/ Thu, 21 May 2026 12:27:29 +0000 https://status.as205126.net/#07c4753b21fcb8f8dc00ee1596e1df7505d82a768ed558125d9baf047487bf79 VPN service went down https://status.as205126.net/ Wed, 20 May 2026 21:59:42 +0000 https://status.as205126.net/#93cb742212307ece648eb6134b704a01e8476e8f90906a418cfbd37e8387dafa Git server recovered https://status.as205126.net/ Wed, 20 May 2026 21:56:46 +0000 https://status.as205126.net/#7772cbde25d2831c29f564a14e8b3ed3716d303d6b1547409edb8c654550abb0 Docker&Helm registry recovered https://status.as205126.net/ Wed, 20 May 2026 21:56:31 +0000 https://status.as205126.net/#5c9493b155a7332f1f23f9d8863bfa89072d2358d9d40581616a71b5f4ab8b97 VPN service recovered https://status.as205126.net/ Wed, 20 May 2026 21:47:34 +0000 https://status.as205126.net/#5c9493b155a7332f1f23f9d8863bfa89072d2358d9d40581616a71b5f4ab8b97 VPN service went down https://status.as205126.net/ Wed, 20 May 2026 21:46:04 +0000 https://status.as205126.net/#93cb742212307ece648eb6134b704a01e8476e8f90906a418cfbd37e8387dafa Git server went down https://status.as205126.net/ Wed, 20 May 2026 21:45:54 +0000 https://status.as205126.net/#7772cbde25d2831c29f564a14e8b3ed3716d303d6b1547409edb8c654550abb0 Docker&Helm registry went down https://status.as205126.net/ Tue, 19 May 2026 10:46:08 +0000 https://status.as205126.net/#a2473e4210761b43a488b85c88a5393865c085f646d9952a066f1afcff203da7 Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 10:43:32 +0000 https://status.as205126.net/#a2473e4210761b43a488b85c88a5393865c085f646d9952a066f1afcff203da7 Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 08:58:07 +0000 https://status.as205126.net/#8af33267697a37d725bb46a70e457019c06cad2b3ca170e8b8295dcabd78debd Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 08:55:36 +0000 https://status.as205126.net/#8af33267697a37d725bb46a70e457019c06cad2b3ca170e8b8295dcabd78debd Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 08:46:10 +0000 https://status.as205126.net/#c60cb3a189644f33e1b140068832571a9bb278b3351504321f93cab0394570ca Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 08:37:33 +0000 https://status.as205126.net/#c60cb3a189644f33e1b140068832571a9bb278b3351504321f93cab0394570ca Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 07:55:07 +0000 https://status.as205126.net/#fdb648ab0fd8018c12c1a08dbe26dd618322c4ca03e888ba2504c64254128a41 Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 07:52:38 +0000 https://status.as205126.net/#fdb648ab0fd8018c12c1a08dbe26dd618322c4ca03e888ba2504c64254128a41 Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 07:19:07 +0000 https://status.as205126.net/#a4b83663ad0d99b20a795c5df9089446e5279455ac0fa1dd21247664ab400c5a Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 07:16:34 +0000 https://status.as205126.net/#a4b83663ad0d99b20a795c5df9089446e5279455ac0fa1dd21247664ab400c5a Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 05:31:08 +0000 https://status.as205126.net/#f4c3602e994061de5dbf1252e9674a1a1899f68b1d61f12b5f4f399c44c11ee4 Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 05:28:36 +0000 https://status.as205126.net/#f4c3602e994061de5dbf1252e9674a1a1899f68b1d61f12b5f4f399c44c11ee4 Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 04:55:08 +0000 https://status.as205126.net/#2bdc94b26f1b1f6b0c2623574ee66d531f8fe655c0d2ce398ceb84efa49dc74a Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 04:52:36 +0000 https://status.as205126.net/#2bdc94b26f1b1f6b0c2623574ee66d531f8fe655c0d2ce398ceb84efa49dc74a Load balancer went down https://status.as205126.net/ Tue, 19 May 2026 04:28:05 +0000 https://status.as205126.net/#47687e52ad67727aa235cd584ee10387c535847c22f98b5f4085b674bb8f48cb Load balancer recovered https://status.as205126.net/ Tue, 19 May 2026 04:25:35 +0000 https://status.as205126.net/#47687e52ad67727aa235cd584ee10387c535847c22f98b5f4085b674bb8f48cb Load balancer went down https://status.as205126.net/ Sun, 17 May 2026 12:16:57 +0000 https://status.as205126.net/#dcf88578e0091f961616a89b081645bb9af7dcc1ffad6d97bb53206b532b2122 Git server recovered https://status.as205126.net/ Sun, 17 May 2026 12:11:27 +0000 https://status.as205126.net/#dcf88578e0091f961616a89b081645bb9af7dcc1ffad6d97bb53206b532b2122 Git server went down https://status.as205126.net/incident/897955 Sun, 17 May 2026 12:07:08 -0000 https://status.as205126.net/incident/897955#4c0dc4088b9c051d813467e2913b9a43eb60f556a08fd158e61cd61292c6a76b We are updating the git server. https://status.as205126.net/incident/895868 Thu, 14 May 2026 12:52:00 -0000 https://status.as205126.net/incident/895868#b265a44752b13feb749517cc53a2c2afe7b2488499637691e485417f76000a83 The provider resolved the issue, they also are still investigating about the why. https://status.as205126.net/incident/895868 Thu, 14 May 2026 12:18:00 -0000 https://status.as205126.net/incident/895868#e754081472e651d73040e4014894cd91c7645bfe4693056f2437413dff5e64e2 The server is online, connection with the kubernetes cluster is ok. We are monitoring the statement from the provider. https://status.as205126.net/incident/895868 Thu, 14 May 2026 12:15:00 -0000 https://status.as205126.net/incident/895868#b4d519007ef3756833897c6cb922bb1a73f65cabb6bbaf42f895e7412c52076d The host seems to be back online as the monitoring gives no TO. https://status.as205126.net/ Thu, 14 May 2026 12:11:50 +0000 https://status.as205126.net/#2ffe4dd06c5f38433d7efd1350da0a3cf5eca7aa2c919b84ec66aa3930260121 Docker&Helm registry recovered https://status.as205126.net/ Thu, 14 May 2026 12:11:34 +0000 https://status.as205126.net/#75a6ca06d5eeba6b10d7de2c785d110fd6169a126ab1dd4e58e427550d670431 VPN service recovered https://status.as205126.net/ Thu, 14 May 2026 12:11:32 +0000 https://status.as205126.net/#ea35bcbf6b97c7fd078a8133159694c539161c39309715c8ae7ce3cc61426240 Git server recovered https://status.as205126.net/ Thu, 14 May 2026 12:10:43 +0000 https://status.as205126.net/#14401b8feb18c0ce7825570bdad6d9ebdfc455b64f075ecd013724c0614a504f Authentication service recovered https://status.as205126.net/ Thu, 14 May 2026 12:10:20 +0000 https://status.as205126.net/#3beef8dbe84a939b7176a87942e734cdb42cfd1802ab28aaaa60ef82a75bf2e8 Load balancer recovered https://status.as205126.net/ Thu, 14 May 2026 09:58:50 +0000 https://status.as205126.net/#2ffe4dd06c5f38433d7efd1350da0a3cf5eca7aa2c919b84ec66aa3930260121 Docker&Helm registry went down https://status.as205126.net/ Thu, 14 May 2026 09:58:27 +0000 https://status.as205126.net/#ea35bcbf6b97c7fd078a8133159694c539161c39309715c8ae7ce3cc61426240 Git server went down https://status.as205126.net/ Thu, 14 May 2026 09:57:44 +0000 https://status.as205126.net/#14401b8feb18c0ce7825570bdad6d9ebdfc455b64f075ecd013724c0614a504f Authentication service went down https://status.as205126.net/ Thu, 14 May 2026 09:57:34 +0000 https://status.as205126.net/#75a6ca06d5eeba6b10d7de2c785d110fd6169a126ab1dd4e58e427550d670431 VPN service went down https://status.as205126.net/ Thu, 14 May 2026 09:56:11 +0000 https://status.as205126.net/#3beef8dbe84a939b7176a87942e734cdb42cfd1802ab28aaaa60ef82a75bf2e8 Load balancer went down https://status.as205126.net/incident/895868 Thu, 14 May 2026 09:54:00 -0000 https://status.as205126.net/incident/895868#49382a5b2cd4a3f641a366d1eb49eff013c605a7f08a1150764113b59417f783 Our provider is in unplanned downtime. They are investigating. However, the cluster itself is not down, you can still have requests from us. https://status.as205126.net/incident/891715 Sat, 09 May 2026 14:00:00 -0000 https://status.as205126.net/incident/891715#6ea8430f168197bc549c90290f76ace7cb4d49d7c7adba8a7703736fcd5cd4fe Volumes are restored and apps functional https://status.as205126.net/incident/891715 Sat, 09 May 2026 13:10:00 -0000 https://status.as205126.net/incident/891715#607e71aefc7773cd455a2a6deff3f87a7b575aa5a753f6b0b71909b29b9a991a Kubernetes: 8 volumes are pending to recover properly https://status.as205126.net/incident/891715 Sat, 09 May 2026 12:40:00 -0000 https://status.as205126.net/incident/891715#a614a9c461da365c396b1cef2d56d3aa52ac7ce97306c967952a8d89df027654 The node is the Parisian premise is recovering the volumes https://status.as205126.net/ Sat, 09 May 2026 12:33:34 +0000 https://status.as205126.net/#2e56245b784ffcc49083ae8d315b819b54b6e46517058b26fc1c9cbc0b863afa AS205126 - par recovered https://status.as205126.net/incident/891715 Sat, 09 May 2026 12:33:00 -0000 https://status.as205126.net/incident/891715#cb2927b459c04ecfbbbf1efc79158455b113d9a1e1a03c823bb60855f17f2a8d Services are still recovering https://status.as205126.net/incident/891715 Sat, 09 May 2026 12:30:00 -0000 https://status.as205126.net/incident/891715#57869bbe402838192c42d2e1995b5959c0f234bcf2a585607cd707e5d20260d4 The power has been restored, services are starting to resume. https://status.as205126.net/ Sat, 09 May 2026 12:27:56 +0000 https://status.as205126.net/#2e56245b784ffcc49083ae8d315b819b54b6e46517058b26fc1c9cbc0b863afa AS205126 - par went down https://status.as205126.net/incident/891715 Sat, 09 May 2026 12:26:00 -0000 https://status.as205126.net/incident/891715#4e7253ba597289f6f5884e1750089bab92ccce4eb9cb7509bfdbac25e12fd34e We’ve lost power in Parisian site. https://status.as205126.net/ Wed, 06 May 2026 07:05:48 +0000 https://status.as205126.net/#0496cbe1ebe5f0a616ba09387d5ac31ab73bbbfd8d1c5ba7a6fc24b0c4903771 Docker&Helm registry recovered https://status.as205126.net/ Wed, 06 May 2026 01:40:53 +0000 https://status.as205126.net/#0496cbe1ebe5f0a616ba09387d5ac31ab73bbbfd8d1c5ba7a6fc24b0c4903771 Docker&Helm registry went down https://status.as205126.net/ Tue, 05 May 2026 19:14:02 +0000 https://status.as205126.net/#2ff9b023ce8737a2c5b62cfece9144d7b72530340249d39010e9a51504e17a28 Authentication service recovered https://status.as205126.net/ Tue, 05 May 2026 19:05:57 +0000 https://status.as205126.net/#1a4911e28a3a95b8bc7b4cb45508833b85965496033a156f530430db773b4a6b Docker&Helm registry recovered https://status.as205126.net/ Tue, 05 May 2026 18:59:45 +0000 https://status.as205126.net/#1a4911e28a3a95b8bc7b4cb45508833b85965496033a156f530430db773b4a6b Docker&Helm registry went down https://status.as205126.net/ Tue, 05 May 2026 18:59:35 +0000 https://status.as205126.net/#ac99dcf3d9d23643c66286aa2b7655f3629f5465354215862e05100d83643656 Git server recovered https://status.as205126.net/ Tue, 05 May 2026 18:58:45 +0000 https://status.as205126.net/#2ff9b023ce8737a2c5b62cfece9144d7b72530340249d39010e9a51504e17a28 Authentication service went down https://status.as205126.net/ Tue, 05 May 2026 18:41:34 +0000 https://status.as205126.net/#ac99dcf3d9d23643c66286aa2b7655f3629f5465354215862e05100d83643656 Git server went down https://status.as205126.net/incident/888297 Tue, 05 May 2026 18:38:32 -0000 https://status.as205126.net/incident/888297#fa34a86a638a270498d3b5d3b2f5753ca7f83b2ddef95183688b7bd041839f62 We are updating kubernetes cluster OS to fix CVE-2026-31431 https://status.as205126.net/ Mon, 04 May 2026 22:21:33 +0000 https://status.as205126.net/#f902bd34b66d27ab3940f4693bb6553291019ce2c1d5a635f9bc22f23ac194d5 AS205126 - par recovered https://status.as205126.net/ Mon, 04 May 2026 22:18:50 +0000 https://status.as205126.net/#f902bd34b66d27ab3940f4693bb6553291019ce2c1d5a635f9bc22f23ac194d5 AS205126 - par went down https://status.as205126.net/incident/888295 Mon, 04 May 2026 22:17:09 -0000 https://status.as205126.net/incident/888295#efbad4c5a1b0f754a3f6d17617652e05074dfb0aa53a80d659cec23f9c9c9570 We had to restart the router because it is backed by a virtualization tool. https://status.as205126.net/ Sat, 02 May 2026 19:12:35 +0000 https://status.as205126.net/#58e870ebfb4d6d5128935497437c2d9dadd8ac812d6f1d5eb1bb5d85fc11477b AS205126 - par recovered https://status.as205126.net/ Sat, 02 May 2026 19:11:54 +0000 https://status.as205126.net/#a3bded2ead93456a21fea392fe72ecd3dd43a33d4f628df42ff0cd0cabf262a1 AS205126 - cha recovered https://status.as205126.net/ Sat, 02 May 2026 19:11:44 +0000 https://status.as205126.net/#8fab62e962d9b80fb287b7548300757ef73f132a9ef12d9948978683dcdabf78 Edge 1 Paris recovered https://status.as205126.net/ Sat, 02 May 2026 19:11:24 +0000 https://status.as205126.net/#ceb2bd54de45af6898daed0b5bc3b065434f900f037559686a255b5ed169ca5c as205126.net recovered https://status.as205126.net/ Sat, 02 May 2026 19:09:48 +0000 https://status.as205126.net/#58e870ebfb4d6d5128935497437c2d9dadd8ac812d6f1d5eb1bb5d85fc11477b AS205126 - par went down https://status.as205126.net/ Sat, 02 May 2026 19:09:23 +0000 https://status.as205126.net/#ceb2bd54de45af6898daed0b5bc3b065434f900f037559686a255b5ed169ca5c as205126.net went down https://status.as205126.net/ Sat, 02 May 2026 19:09:15 +0000 https://status.as205126.net/#a3bded2ead93456a21fea392fe72ecd3dd43a33d4f628df42ff0cd0cabf262a1 AS205126 - cha went down https://status.as205126.net/ Sat, 02 May 2026 19:08:58 +0000 https://status.as205126.net/#8fab62e962d9b80fb287b7548300757ef73f132a9ef12d9948978683dcdabf78 Edge 1 Paris went down https://status.as205126.net/incident/885954 Sat, 02 May 2026 19:06:50 -0000 https://status.as205126.net/incident/885954#ae81f9d0fe7332fcb9fbb3e4e31b62aac59b7c49897b0855adefc42b502893f3 We are updating the edge router system. https://status.as205126.net/ Fri, 01 May 2026 00:07:13 +0000 https://status.as205126.net/#33251185f88002f4d883739d5f7ac1d0e2356ce8970d3d442fc27aa04ae4b3e8 Load balancer recovered https://status.as205126.net/ Fri, 01 May 2026 00:04:12 +0000 https://status.as205126.net/#33251185f88002f4d883739d5f7ac1d0e2356ce8970d3d442fc27aa04ae4b3e8 Load balancer went down https://status.as205126.net/ Thu, 30 Apr 2026 22:49:08 +0000 https://status.as205126.net/#bf9641c131571886bb5160a0144ae18f12d28add3f7742ac0870327f23963c15 Load balancer recovered https://status.as205126.net/ Thu, 30 Apr 2026 22:46:08 +0000 https://status.as205126.net/#bf9641c131571886bb5160a0144ae18f12d28add3f7742ac0870327f23963c15 Load balancer went down https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:56:00 -0000 https://status.as205126.net/incident/882719#b22871cbd4b96300c54dc8e99e0a45a6eab2fae1f0ba35f4a7c5fbd6fedf6cac The issue seems to be resolved. It seems that we have an IPv6 incompatibility in our infrastructure. https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:51:00 -0000 https://status.as205126.net/incident/882719#e8c946cce960b8ad9728066ea48de3ffcf55fd3302b65bcf6cb6f51b7c063406 We might find the issue, we had applied a fix. and we're monitoring now. https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:43:00 -0000 https://status.as205126.net/incident/882719#7ea7b88dd598f078cedf6f7e24249bf3c619b8a591b8ae2e6791e4ad264887b2 Don't know why but the load balancer decided to struggle again. https://status.as205126.net/ Tue, 28 Apr 2026 23:28:08 +0000 https://status.as205126.net/#28ad1361dc0c0dfa725c7c73e40290337b85b657c698394a942a16e16d23e2f2 Load balancer recovered https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:28:00 -0000 https://status.as205126.net/incident/882719#ed046023b591e22b1212d491a64d69df0f52495a497109bdf9ab5cc78b36266b The services are now back online. https://status.as205126.net/ Tue, 28 Apr 2026 23:26:49 +0000 https://status.as205126.net/#25e282331ef92d4f3a4e5f8faee3abf281c7edc645010c4d8665026c088bb86a Docker&Helm registry recovered https://status.as205126.net/ Tue, 28 Apr 2026 23:26:33 +0000 https://status.as205126.net/#feb69145f15d22f9799603e9aa7a186226650d0b555ca97693f499ba022b6da7 Git server recovered https://status.as205126.net/ Tue, 28 Apr 2026 23:26:32 +0000 https://status.as205126.net/#5a9f99315edcb0f0d1cf7150809272ba37bca317e584df55ed76c98a0934e392 VPN service recovered https://status.as205126.net/ Tue, 28 Apr 2026 23:26:01 +0000 https://status.as205126.net/#f85e3db65f5c2e9a09b25032779bf2333deedf046deaa6effec2aebc5a0712df Authentication service recovered https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:26:00 -0000 https://status.as205126.net/incident/882719#9200bda71fd7839a853a5fc24bec956091c0bc0f059b5b9fd17343e14f181a06 We restarted the load balancer the connections across the nodes seems to be resolved. https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:22:00 -0000 https://status.as205126.net/incident/882719#49d354df8cdb4a79aa9148c32859d79a4665ceaeea905ab58e4b6bbab3b3aaf6 The load balancer decided to lose entire connectivity with all the node except internet. https://status.as205126.net/ Tue, 28 Apr 2026 23:19:25 +0000 https://status.as205126.net/#feb69145f15d22f9799603e9aa7a186226650d0b555ca97693f499ba022b6da7 Git server went down https://status.as205126.net/ Tue, 28 Apr 2026 23:18:58 +0000 https://status.as205126.net/#f85e3db65f5c2e9a09b25032779bf2333deedf046deaa6effec2aebc5a0712df Authentication service went down https://status.as205126.net/ Tue, 28 Apr 2026 23:18:30 +0000 https://status.as205126.net/#5a9f99315edcb0f0d1cf7150809272ba37bca317e584df55ed76c98a0934e392 VPN service went down https://status.as205126.net/ Tue, 28 Apr 2026 23:17:19 +0000 https://status.as205126.net/#28ad1361dc0c0dfa725c7c73e40290337b85b657c698394a942a16e16d23e2f2 Load balancer went down https://status.as205126.net/ Tue, 28 Apr 2026 23:16:53 +0000 https://status.as205126.net/#25e282331ef92d4f3a4e5f8faee3abf281c7edc645010c4d8665026c088bb86a Docker&Helm registry went down https://status.as205126.net/incident/882719 Tue, 28 Apr 2026 23:16:00 -0000 https://status.as205126.net/incident/882719#5318d3462704773b32d1e6911920584a8c9a2cc7d16a108e2c8b1e05d612efa8 Due to connectivity issue, one node cannot connect to the load balancer https://status.as205126.net/ Mon, 27 Apr 2026 22:35:35 +0000 https://status.as205126.net/#316e140580eb36f09279d9a242432a1111e10e71470d8d0f19fda1a1ad9809cd VPN service recovered https://status.as205126.net/ Mon, 27 Apr 2026 22:27:33 +0000 https://status.as205126.net/#316e140580eb36f09279d9a242432a1111e10e71470d8d0f19fda1a1ad9809cd VPN service went down https://status.as205126.net/ Sun, 26 Apr 2026 16:28:11 +0000 https://status.as205126.net/#d81deb35324f1f0b285a871e7ae313a3edc429ab0857cc62c0ce27871a148b96 Load balancer recovered https://status.as205126.net/ Sun, 26 Apr 2026 16:19:08 +0000 https://status.as205126.net/#d81deb35324f1f0b285a871e7ae313a3edc429ab0857cc62c0ce27871a148b96 Load balancer went down https://status.as205126.net/incident/879982 Sun, 26 Apr 2026 11:34:00 -0000 https://status.as205126.net/incident/879982#3a3d86eb517534d9f64983d4b4c69b38da2659126efcd7eb1105d262ee0778c3 The issue is resolved, and seems to be related to the registry and authentication downtime on 25th at 4am https://status.as205126.net/incident/879982 Sun, 26 Apr 2026 01:00:00 -0000 https://status.as205126.net/incident/879982#3cbe3986e7f7b60dad7b431ad7389c8688613ea34f7d9bbd1d4ce6c8a94a7ac5 The root cause seems to be a connection issue between a node and the load balancer. We are restarting the node. No service downtime expected. https://status.as205126.net/incident/879982 Sat, 25 Apr 2026 12:30:00 -0000 https://status.as205126.net/incident/879982#3a19bd7ae7d4eb3a75934a31b3b39a766bbc01ec0c9d9b0e44e00806acd5546f For some services, the connection is being very slow or even dropped after being received by the LB. We are investigating. https://status.as205126.net/ Sat, 25 Apr 2026 02:22:35 +0000 https://status.as205126.net/#904e5e917166ea70fecad8f7653012d4d60aa55db0af63be6d52062379c19266 Authentication service recovered https://status.as205126.net/ Sat, 25 Apr 2026 02:20:50 +0000 https://status.as205126.net/#4e9fcf33f31a99a625f485a915f5ff3113b5e2c4869d88cdad94bd512a12cd0c Docker&Helm registry recovered https://status.as205126.net/ Sat, 25 Apr 2026 01:52:45 +0000 https://status.as205126.net/#4e9fcf33f31a99a625f485a915f5ff3113b5e2c4869d88cdad94bd512a12cd0c Docker&Helm registry went down https://status.as205126.net/ Sat, 25 Apr 2026 01:51:42 +0000 https://status.as205126.net/#904e5e917166ea70fecad8f7653012d4d60aa55db0af63be6d52062379c19266 Authentication service went down https://status.as205126.net/ Tue, 21 Apr 2026 22:20:27 +0000 https://status.as205126.net/#82114a32b0724669b3099ca13a20134e86c1e367b9b1d22d92ef179e52dcfcf5 Git server recovered https://status.as205126.net/ Tue, 21 Apr 2026 22:08:34 +0000 https://status.as205126.net/#82114a32b0724669b3099ca13a20134e86c1e367b9b1d22d92ef179e52dcfcf5 Git server went down https://status.as205126.net/incident/876788 Tue, 21 Apr 2026 22:06:16 -0000 https://status.as205126.net/incident/876788#cf447c0736913db6b38e235071cdb9267a96ba8d6f03639a6a975f2b4e914f78 As the incident on the Git server told earlier, we were trying to deploy an infrastructure update. We are now updating the infrastructure. https://status.as205126.net/ Mon, 20 Apr 2026 15:38:54 +0000 https://status.as205126.net/#b169892e1f6b10b7f3770d05455cf75c453a8720e6728b6ba4809675134a9ad9 AS205126 - cha recovered https://status.as205126.net/ Mon, 20 Apr 2026 15:38:43 +0000 https://status.as205126.net/#91214651f9bc424d74b7352cd51e446e9b23767a75e155521d0f988d0013e6cb Edge 1 Paris recovered https://status.as205126.net/ Mon, 20 Apr 2026 15:38:24 +0000 https://status.as205126.net/#58641c6a2aa3bda8751a9710b10042ea0b37426f1d3592d248393bb147f45af5 as205126.net recovered https://status.as205126.net/ Mon, 20 Apr 2026 15:36:33 +0000 https://status.as205126.net/#fed4f32c5356dcfef0a6e0e51578fce8b713755a7fc5f15fb2a1935d8247f7d6 AS205126 - par recovered https://status.as205126.net/ Mon, 20 Apr 2026 14:09:20 +0000 https://status.as205126.net/#58641c6a2aa3bda8751a9710b10042ea0b37426f1d3592d248393bb147f45af5 as205126.net went down https://status.as205126.net/ Mon, 20 Apr 2026 14:09:15 +0000 https://status.as205126.net/#b169892e1f6b10b7f3770d05455cf75c453a8720e6728b6ba4809675134a9ad9 AS205126 - cha went down https://status.as205126.net/ Mon, 20 Apr 2026 14:09:05 +0000 https://status.as205126.net/#91214651f9bc424d74b7352cd51e446e9b23767a75e155521d0f988d0013e6cb Edge 1 Paris went down https://status.as205126.net/ Mon, 20 Apr 2026 14:06:54 +0000 https://status.as205126.net/#fed4f32c5356dcfef0a6e0e51578fce8b713755a7fc5f15fb2a1935d8247f7d6 AS205126 - par went down https://status.as205126.net/incident/875046 Sun, 19 Apr 2026 11:18:00 -0000 https://status.as205126.net/incident/875046#1ed90865750ad56e4df9f9024ca846035f04cd43e8b9373921e19624fbcfa239 We rolled-back the upgrade. https://status.as205126.net/ Sun, 19 Apr 2026 11:17:25 +0000 https://status.as205126.net/#2c88b2859c8e126e029f18ec3dafa54c0a9f61e670b0e5585b5bd9cfecce5707 Git server recovered https://status.as205126.net/ Sun, 19 Apr 2026 10:53:35 +0000 https://status.as205126.net/#2c88b2859c8e126e029f18ec3dafa54c0a9f61e670b0e5585b5bd9cfecce5707 Git server went down https://status.as205126.net/incident/875046 Sun, 19 Apr 2026 10:52:00 -0000 https://status.as205126.net/incident/875046#7434b183d127899590c1ddb53163d96c0ab39b95df757e55b6b33356b88ca287 We accidentally pushed a non-ready upgrade of the Git server in production. https://status.as205126.net/incident/875002 Sat, 18 Apr 2026 10:33:00 -0000 https://status.as205126.net/incident/875002#d5ae7e541309076d55da340c1a2d5733d00bba02f100d1e00298c709f6e82e11 The provider tells us that everything is now up. https://status.as205126.net/ Sat, 18 Apr 2026 09:56:31 +0000 https://status.as205126.net/#92830524aa84d18419b4496cc92fb50acf3e883bca430cee6202f52f43a34e26 Git server recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:56:31 +0000 https://status.as205126.net/#e01bcd2b57ac6f67248b7cd0c94afdc365d8bb716a848bb9f4677a7763bc1aa8 VPN service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:55:46 +0000 https://status.as205126.net/#e55ca56adbb6bffc9161dddad5922a5a20e1975831f364dba20eb5ed7abfe89c Authentication service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:55:11 +0000 https://status.as205126.net/#1fc17db1bcd1086c2b3ce1a1fee976a2513c0036830df3e2786b8f612989cbcc Load balancer recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:54:36 +0000 https://status.as205126.net/#f5e21c4f7e97fa64d64eedad2f89abc250be6ab65ad264bb0c2016ac3e04489f Docker&Helm registry recovered https://status.as205126.net/incident/875002 Sat, 18 Apr 2026 09:54:00 -0000 https://status.as205126.net/incident/875002#f77a315ed90c1c13328c9c32390a1843c7456b2e2a702c220dd69d74ee2f27ed The upstream is now online. The system is rebooting. https://status.as205126.net/incident/875002 Sat, 18 Apr 2026 09:49:00 -0000 https://status.as205126.net/incident/875002#302e71e476d2acfe05fbfae680f0239aa0cd241aa92ebf15fff5f92fe1a19ef8 It seems they hava a power issue. https://status.as205126.net/ Sat, 18 Apr 2026 09:46:48 +0000 https://status.as205126.net/#f5e21c4f7e97fa64d64eedad2f89abc250be6ab65ad264bb0c2016ac3e04489f Docker&Helm registry went down https://status.as205126.net/ Sat, 18 Apr 2026 09:46:30 +0000 https://status.as205126.net/#92830524aa84d18419b4496cc92fb50acf3e883bca430cee6202f52f43a34e26 Git server went down https://status.as205126.net/ Sat, 18 Apr 2026 09:45:38 +0000 https://status.as205126.net/#e55ca56adbb6bffc9161dddad5922a5a20e1975831f364dba20eb5ed7abfe89c Authentication service went down https://status.as205126.net/ Sat, 18 Apr 2026 09:45:29 +0000 https://status.as205126.net/#e01bcd2b57ac6f67248b7cd0c94afdc365d8bb716a848bb9f4677a7763bc1aa8 VPN service went down https://status.as205126.net/incident/875002 Sat, 18 Apr 2026 09:45:00 -0000 https://status.as205126.net/incident/875002#18e51c59dc5efef1dadf4dcf4e2b6fd5814184fb6208ad645a248f3ef3530204 Our load balancer network provider is down. https://status.as205126.net/ Sat, 18 Apr 2026 09:43:37 +0000 https://status.as205126.net/#1fc17db1bcd1086c2b3ce1a1fee976a2513c0036830df3e2786b8f612989cbcc Load balancer went down https://status.as205126.net/ Sat, 18 Apr 2026 09:36:01 +0000 https://status.as205126.net/#9c0e5133e3a4a5f0f3a6ead2682a7450e9daa12a3af267aa51627c695665c94a Docker&Helm registry recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:35:38 +0000 https://status.as205126.net/#d7b02d4dcd7d331d2d7239337d6ae101f22dd19ba6a38f555fb6edb70b0c0b20 Git server recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:35:37 +0000 https://status.as205126.net/#ed34f88af2fa233b63d7d4951d602bfa92b99dfe6aeb3f277abb66be193e7a5d VPN service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:34:35 +0000 https://status.as205126.net/#3489a2b9d6179b4a6ae854b1edc2ef5ef754dd2cce6abb9e75a55f0489a25581 Authentication service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:34:10 +0000 https://status.as205126.net/#5e40bbba43aab96dc39b71d9a691fdda3ebe8c6b3cc67292e1ea7c7fd3593c19 Load balancer recovered https://status.as205126.net/ Sat, 18 Apr 2026 08:49:30 +0000 https://status.as205126.net/#d7b02d4dcd7d331d2d7239337d6ae101f22dd19ba6a38f555fb6edb70b0c0b20 Git server went down https://status.as205126.net/ Sat, 18 Apr 2026 08:48:40 +0000 https://status.as205126.net/#3489a2b9d6179b4a6ae854b1edc2ef5ef754dd2cce6abb9e75a55f0489a25581 Authentication service went down https://status.as205126.net/ Sat, 18 Apr 2026 08:48:30 +0000 https://status.as205126.net/#ed34f88af2fa233b63d7d4951d602bfa92b99dfe6aeb3f277abb66be193e7a5d VPN service went down https://status.as205126.net/ Sat, 18 Apr 2026 08:47:10 +0000 https://status.as205126.net/#5e40bbba43aab96dc39b71d9a691fdda3ebe8c6b3cc67292e1ea7c7fd3593c19 Load balancer went down https://status.as205126.net/ Sat, 18 Apr 2026 08:45:53 +0000 https://status.as205126.net/#9c0e5133e3a4a5f0f3a6ead2682a7450e9daa12a3af267aa51627c695665c94a Docker&Helm registry went down https://status.as205126.net/ Wed, 15 Apr 2026 20:17:28 +0000 https://status.as205126.net/#5b34173489eaba691718a2c01d7e841f490b9b3316bf8798973357ec95d2edde Git server recovered https://status.as205126.net/ Wed, 15 Apr 2026 19:47:32 +0000 https://status.as205126.net/#5b34173489eaba691718a2c01d7e841f490b9b3316bf8798973357ec95d2edde Git server went down https://status.as205126.net/incident/872544 Wed, 15 Apr 2026 19:46:00 -0000 https://status.as205126.net/incident/872544#3e5fb9983079f75c0538e9832552c2e3feb416471c4676c2062a2d643bc294cb We are updating git server infra https://status.as205126.net/ Tue, 14 Apr 2026 22:08:33 +0000 https://status.as205126.net/#c5e022164669fba3f26275ef451412b5b2e3b28d634c6ee65ef9f2c8534d8cf5 Git server recovered https://status.as205126.net/ Tue, 14 Apr 2026 22:04:44 +0000 https://status.as205126.net/#218fd2231f0681206b2629e13c17f463befff9dc12891df762b1fa68cfe425f2 Authentication service recovered https://status.as205126.net/ Tue, 14 Apr 2026 22:02:36 +0000 https://status.as205126.net/#c5e022164669fba3f26275ef451412b5b2e3b28d634c6ee65ef9f2c8534d8cf5 Git server went down https://status.as205126.net/ Tue, 14 Apr 2026 21:58:46 +0000 https://status.as205126.net/#218fd2231f0681206b2629e13c17f463befff9dc12891df762b1fa68cfe425f2 Authentication service went down https://status.as205126.net/incident/871672 Tue, 14 Apr 2026 21:43:08 -0000 https://status.as205126.net/incident/871672#3458b502ee63bab2850b546b9df07c35a922063c2fed5e31340653136c1a0b8c We are updating the kubernetes cluster to 1.35.3 https://status.as205126.net/ Tue, 14 Apr 2026 16:30:25 +0000 https://status.as205126.net/#77e282d32d0bb9a4f1b20ef4cbd8477942b94b0f4d737a8429c1f80478d092cc AS205126 - par recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:29:54 +0000 https://status.as205126.net/#93290f1aed21e9d67e63fe2b4e822f8096520f5a5301fe0c181edeff889e4f3c AS205126 - cha recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:29:36 +0000 https://status.as205126.net/#21c14db6eda328eb05b248cb996816130a7bca9faad28573f45fb2261b52eb6c Edge 1 Paris recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:29:24 +0000 https://status.as205126.net/#1a1d3f48c0aa28444bd8fd4d905a17dbb64e48f71d73ca4da9fc57f2b759c92a as205126.net recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:27:14 +0000 https://status.as205126.net/#1a1d3f48c0aa28444bd8fd4d905a17dbb64e48f71d73ca4da9fc57f2b759c92a as205126.net went down https://status.as205126.net/ Tue, 14 Apr 2026 16:27:07 +0000 https://status.as205126.net/#93290f1aed21e9d67e63fe2b4e822f8096520f5a5301fe0c181edeff889e4f3c AS205126 - cha went down https://status.as205126.net/ Tue, 14 Apr 2026 16:27:05 +0000 https://status.as205126.net/#21c14db6eda328eb05b248cb996816130a7bca9faad28573f45fb2261b52eb6c Edge 1 Paris went down https://status.as205126.net/ Tue, 14 Apr 2026 16:24:53 +0000 https://status.as205126.net/#77e282d32d0bb9a4f1b20ef4cbd8477942b94b0f4d737a8429c1f80478d092cc AS205126 - par went down https://status.as205126.net/ Mon, 13 Apr 2026 06:55:41 +0000 https://status.as205126.net/#5fbbf91379550db504a9defb88b0b01fb187ae1c4376e7a466be663b630068c8 Authentication service recovered https://status.as205126.net/ Mon, 13 Apr 2026 06:04:36 +0000 https://status.as205126.net/#5fbbf91379550db504a9defb88b0b01fb187ae1c4376e7a466be663b630068c8 Authentication service went down https://status.as205126.net/ Sun, 12 Apr 2026 01:25:10 +0000 https://status.as205126.net/#89c84b991647b4a2ede19081a0438a7201eceb88256db867c4038db56b7c9aa0 Authentication service recovered https://status.as205126.net/ Sun, 12 Apr 2026 01:19:44 +0000 https://status.as205126.net/#89c84b991647b4a2ede19081a0438a7201eceb88256db867c4038db56b7c9aa0 Authentication service went down https://status.as205126.net/incident/869669 Sun, 12 Apr 2026 01:17:00 -0000 https://status.as205126.net/incident/869669#109c7d8fa9f2af7fe0691e0643a3b76455cb909a54c4ab712600b268f8903921 We are updating the authentication system to the latest version. https://status.as205126.net/incident/869655 Sun, 12 Apr 2026 00:36:11 -0000 https://status.as205126.net/incident/869655#79fb048b329a1d661bcd033701b3954a5e2752e78f0925296f5430a4d2778fe8 As the same as the registry, we are updating the authentication ingress. https://status.as205126.net/incident/869629 Sat, 11 Apr 2026 23:55:15 -0000 https://status.as205126.net/incident/869629#4c701e95dfe2b58c5552a14f16de93141bc6990a3aa624353e8ca879259c76b8 After confirming the load balancer backend update, we are updating the registry ingress. https://status.as205126.net/ Sat, 11 Apr 2026 18:29:47 +0000 https://status.as205126.net/#73235a1a95a26af031b739eb7ea07bc2c1a2d231f302de919629a0e8972e5904 Docker&Helm registry recovered https://status.as205126.net/ Sat, 11 Apr 2026 18:23:49 +0000 https://status.as205126.net/#73235a1a95a26af031b739eb7ea07bc2c1a2d231f302de919629a0e8972e5904 Docker&Helm registry went down https://status.as205126.net/incident/869508 Sat, 11 Apr 2026 18:00:28 -0000 https://status.as205126.net/incident/869508#38b59c751cc202d185cf0cfdb829dfa337cc1a478e9c2969bfd3f362cbb6de02 We are testing a new LB update that allow us to control the ingress from Kubernetes. https://status.as205126.net/ Wed, 08 Apr 2026 08:11:48 +0000 https://status.as205126.net/#e6c17fb94463361e72a2375db39f9541c915302e71e4417af1bdd8998b6fc7f0 AS205126 - cha recovered https://status.as205126.net/ Wed, 08 Apr 2026 08:09:07 +0000 https://status.as205126.net/#e6c17fb94463361e72a2375db39f9541c915302e71e4417af1bdd8998b6fc7f0 AS205126 - cha went down https://status.as205126.net/ Wed, 08 Apr 2026 00:17:57 +0000 https://status.as205126.net/#64f4a4748352d064f00305b8028ac153a36322d83314607d5d0e385d80d0da29 Docker&Helm registry recovered https://status.as205126.net/ Wed, 08 Apr 2026 00:17:22 +0000 https://status.as205126.net/#be75a2f86f65557e42594f5f1362ecd7dc459fdc0f7ac8c5713516626ee452cc as205126.net recovered https://status.as205126.net/ Wed, 08 Apr 2026 00:14:50 +0000 https://status.as205126.net/#7cfb9147bd214a8db30b3bd0f77d3028ddf7de7986b59ee70bc8165a1e1da89d AS205126 - cha recovered https://status.as205126.net/ Wed, 08 Apr 2026 00:12:18 +0000 https://status.as205126.net/#64f4a4748352d064f00305b8028ac153a36322d83314607d5d0e385d80d0da29 Docker&Helm registry went down https://status.as205126.net/ Wed, 08 Apr 2026 00:12:18 +0000 https://status.as205126.net/#be75a2f86f65557e42594f5f1362ecd7dc459fdc0f7ac8c5713516626ee452cc as205126.net went down https://status.as205126.net/ Wed, 08 Apr 2026 00:12:11 +0000 https://status.as205126.net/#7cfb9147bd214a8db30b3bd0f77d3028ddf7de7986b59ee70bc8165a1e1da89d AS205126 - cha went down https://status.as205126.net/incident/863665 Thu, 02 Apr 2026 21:45:00 -0000 https://status.as205126.net/incident/863665#03865500c302e7d4666180d2d47ef159a577f47322bdc151b2789b993d5484a9 We are updating the theme of the authentication system. https://status.as205126.net/incident/858966 Wed, 01 Apr 2026 18:04:00 -0000 https://status.as205126.net/incident/858966#f1ddd36dcf63992dba5693b4336ce6a4d69f912f538438007e08041dfda01611 We had to restart some nodes to make it work again. We are monitoring closely the situation, even if the status says resolved. https://status.as205126.net/incident/858966 Wed, 01 Apr 2026 17:55:00 -0000 https://status.as205126.net/incident/858966#c4055b5d7a4123c1a5252995ba4fa8650e1f5158869ec5346bcc2b54997c9975 We are investigating. https://status.as205126.net/incident/858966 Sat, 28 Mar 2026 10:09:00 -0000 https://status.as205126.net/incident/858966#23e67237767e62f19d323ee714cbce4fe5cb44ee2f3143bc8229b417b1ae691b The authentication system came back online without any perturbation. However, it is not load balancing anymore for that component. https://status.as205126.net/incident/858966 Sat, 28 Mar 2026 04:03:00 -0000 https://status.as205126.net/incident/858966#8e742a18b26a3e34598148f4b962ca206230440ebdbafb2a2e9ace96e2bb65ad We have disabled all the nodes from the load balancer except one. The selected node seems to work as intended, but still don’t know why the others break. https://status.as205126.net/incident/858966 Fri, 27 Mar 2026 19:33:00 -0000 https://status.as205126.net/incident/858966#e1d78a88ec8ef3246c71208800b02d4581a9d5e4c35be1b53c5137c83dd8e685 As investigation we are trying to remove node from load balancer to know which one is breaking. https://status.as205126.net/incident/858966 Thu, 26 Mar 2026 18:55:00 -0000 https://status.as205126.net/incident/858966#a6c381a9479d2794db3b6863c14d259fc3a5cb2025717314c9773b3efdded1b2 It seems that there is a network communication problem between some nodes. The issue is that we can’t investigate. https://status.as205126.net/incident/855618 Mon, 23 Mar 2026 16:10:25 -0000 https://status.as205126.net/incident/855618#4f3725158886077ad88e9facdb55b830e33d1bcdb41d8a5c82a34d64d943b68d Due to system instability on Kubernetes, we are rebooting the whole cluster. https://status.as205126.net/incident/854139 Sat, 21 Mar 2026 11:02:00 -0000 https://status.as205126.net/incident/854139#963d4c8a0ce6d72519718a91e88f0fcb28fb09673b4f080d6d2bfac6173fa3c6 We restarted a Kubernetes node, everything seems to be working now. https://status.as205126.net/incident/854139 Sat, 21 Mar 2026 10:35:00 -0000 https://status.as205126.net/incident/854139#43860c5e332d88b79fa822241ced3d2cc163489509d08150c172e5b7bc37c9f7 Some of the services are now online, communication between LB and Kubernetes is now up. We are checking why some services are still down. https://status.as205126.net/incident/854139 Sat, 21 Mar 2026 07:32:00 -0000 https://status.as205126.net/incident/854139#995f979d980e06a6aaaeab96e2e4bf829037a1d9c7ff66ce04bdd433626d4813 Our monitoring system is telling us that the load balancer is currently down, as such as the entire admin panel from our LB provider. We can’t do anything but wait. https://status.as205126.net/incident/853144 Thu, 19 Mar 2026 16:55:00 -0000 https://status.as205126.net/incident/853144#05b7627df41cf0c4e5d4d6f02262816b083084ad091ff209b013f06377404c7f We updated the authentication system https://status.as205126.net/incident/850681 Mon, 16 Mar 2026 19:45:00 -0000 https://status.as205126.net/incident/850681#e8c3d77197429cfd7fcd7101d7988b8d7a2fc4015d10b78f83f3af744f854330 We are upgrading our CSI https://status.as205126.net/incident/843471 Sat, 07 Mar 2026 14:31:00 -0000 https://status.as205126.net/incident/843471#0cc2eb05dde54a1deb6e1c8116e4c667b9986b747b5195f6f2c013e40d334a82 It seems to be a bug in the router software, there is no errors, no FW changes applied. After a reboot, the issue was resolved. https://status.as205126.net/incident/843471 Sat, 07 Mar 2026 14:22:00 -0000 https://status.as205126.net/incident/843471#8be98a14c304225e0fb4fd8b58f6d8a99946164c96ee40c84681363e96db47d9 The issue is under investigation. https://status.as205126.net/incident/843471 Sat, 07 Mar 2026 12:48:00 -0000 https://status.as205126.net/incident/843471#79e36f05ae67623c5e3f6e3eff85a01a1225fe9fccb64f00f3b22670ec2cc347 I am not available to investigate. However, the incident is noted and will be investigated later. https://status.as205126.net/incident/830597 Sun, 22 Feb 2026 12:32:00 -0000 https://status.as205126.net/incident/830597#9a414a2f263c9904698f764bf7348e2f6ed4fd0de795f162bedfa5b1c964c470 We are updating our authentication system. https://status.as205126.net/incident/830356 Sun, 22 Feb 2026 00:20:25 -0000 https://status.as205126.net/incident/830356#4617c4ba31878caaa02069191d67f467db06c926b0ed9b4604c271dc55e172ae We are testing a new Docker registry storage backend. https://status.as205126.net/incident/829141 Fri, 20 Feb 2026 00:34:57 -0000 https://status.as205126.net/incident/829141#67787d31d8204dc2999acbaf9dcf04618f28da4a18365edf3b268d89def67c85 We are updating the kubernetes version to 1.35.1 https://status.as205126.net/incident/828338 Wed, 18 Feb 2026 23:45:31 -0000 https://status.as205126.net/incident/828338#83ee674db7a8634bf2ce5b5155f8e4993686059dcfb89f23f9476f54836db072 We are enabling IPv6 on all the Kubernetes nodes. https://status.as205126.net/incident/828335 Wed, 18 Feb 2026 23:39:37 -0000 https://status.as205126.net/incident/828335#d964b41abe1e964271f26492a9244988cb33470a7578949d20fc4864093dc906 We are enabling IPv6 on par-1 kubernetes node https://status.as205126.net/incident/825957 Sun, 15 Feb 2026 14:27:00 -0000 https://status.as205126.net/incident/825957#ec6af652d664734429f3661aaaca539d79c0b98aa9383dd67b6ce13fe6cb83f5 The node is up, and workload moved to other nodes. https://status.as205126.net/incident/825957 Sun, 15 Feb 2026 14:16:00 -0000 https://status.as205126.net/incident/825957#9ea5f5781b1b7cb27d35e4aca3b56a8d3fa6489a9f2531cd8b674aa8a316eab6 One of our Kubernetes node restarted without any notice. https://status.as205126.net/incident/825093 Fri, 13 Feb 2026 22:36:18 -0000 https://status.as205126.net/incident/825093#3a4687f58844fce61fd91288da8204a2dd2822283f569bcc28ea1fabd055c621 We are currently updating the authentication system. https://status.as205126.net/incident/825060 Fri, 13 Feb 2026 21:28:00 -0000 https://status.as205126.net/incident/825060#59a8f33f0b382a6fa9460e58ceba5bd542b3344ac50360aa7db5293a9f28414f The registry is now online, and the git server too. https://status.as205126.net/incident/825060 Fri, 13 Feb 2026 21:27:00 -0000 https://status.as205126.net/incident/825060#ac4bc5ad7d59eb73010f93de60c0f9aaf11e0e8bfb25a8055f36dc63dab2bd39 The authentication system is now online. The load balancer should not be disturbed anymore. https://status.as205126.net/incident/825060 Fri, 13 Feb 2026 21:10:00 -0000 https://status.as205126.net/incident/825060#d571e0c86006b9e7da048cf8d1022d834a61940615a73ecba52e379303e79429 One of our node lost connectivity and went 100% CPU, we decided to shutdown the machine. We are restarting the services. https://status.as205126.net/incident/819926 Fri, 06 Feb 2026 14:11:00 -0000 https://status.as205126.net/incident/819926#9efa7deff79549eb4e2f57f957d82c375a25ba680dd68e106465357f584e9b4c After seeing the alert, we did some investigation but the monitoring was wrong. Nothing was/is down on the VPN side https://status.as205126.net/incident/819926 Fri, 06 Feb 2026 11:22:00 -0000 https://status.as205126.net/incident/819926#8f31ec9ffd44dfbbdb3f44408303c627833f73cdddafd533dbf72467397b5e47 The VPN service had been updated, the monitoring system was not updated to handle the status code change in the server code. The monitoring was triggered wrongly. https://status.as205126.net/incident/817672 Tue, 03 Feb 2026 15:12:29 -0000 https://status.as205126.net/incident/817672#57f5229a38e67c9942d043405c1adf374bd6e27f7d2ad10b2768571c80c4a2f1 Maintenance completed https://status.as205126.net/incident/817672 Tue, 03 Feb 2026 15:08:04 -0000 https://status.as205126.net/incident/817672#6c42983f668a79bdb0ddfb0ad721fca9a06a3ee8f35bf1663612533af9014836 We are applying upgrades and restarting the AS205126 website. https://status.as205126.net/incident/815780 Sat, 31 Jan 2026 14:25:20 -0000 https://status.as205126.net/incident/815780#5b72fcf0dc0908cd9ad5636092c4c20e895f581226d7c2cb52399af4fd31ff12 Some of our kubernetes nodes are ready but workloads do not start and stuck in creating state. We cordoned the node and rebooting it. https://status.as205126.net/incident/815154 Fri, 30 Jan 2026 12:00:06 -0000 https://status.as205126.net/incident/815154#83c3487cd355490725cbdcab47601fdb5a383b2a383760aa404da5928ffbf88a Since we have OCI as upstream for the cloud hosted servers, we have to modify the configuration of the edge router. https://status.as205126.net/incident/814639 Thu, 29 Jan 2026 20:00:01 -0000 https://status.as205126.net/incident/814639#6c5aea00d63b42a4cf0ca7688e4c97bde4b6845ae3791896b3690905bcb56a45 One of our master nodes is hosted on Oracle Cloud. We recently had the opportunity to enable the BYOASN and BYOIP, we are changing the IP of the node. https://status.as205126.net/incident/810713 Sat, 24 Jan 2026 00:29:09 -0000 https://status.as205126.net/incident/810713#a6e0d87b0c569fe84a4306b0dc63621aaaa725a669cb2df764075ea911103847 We are updating the git server. https://status.as205126.net/incident/810360 Fri, 23 Jan 2026 12:45:03 -0000 https://status.as205126.net/incident/810360#aa5b161af499e6bd43c84c35d8f6ac332fe61e6fe74d359df65b4515051b196e The node storage controller is faulty and does not schedule anymore. We are currently restarting the node https://status.as205126.net/incident/810718 Mon, 19 Jan 2026 12:26:00 -0000 https://status.as205126.net/incident/810718#0f0c5b54feb327842d47918559b6da5dff6342897638f9e0213cc8cba5d42b8e The restart method was effective, the services are working. https://status.as205126.net/incident/810718 Mon, 19 Jan 2026 12:00:00 -0000 https://status.as205126.net/incident/810718#247a7d48ca96d6600509135ca51e9d7b13a33373b840d316e951fd60af0d617e We decided to restart a faulty master and worker node. These node were accepting the pods but not scheduling them, plus the networking was broken. https://status.as205126.net/incident/810718 Sun, 18 Jan 2026 17:13:00 -0000 https://status.as205126.net/incident/810718#85853c08e4544b368e95ce3eee3a012bdb909716815c1dab683c1ec6e0167ed8 The authentication system is also down. Still not investigating. https://status.as205126.net/incident/810718 Sun, 18 Jan 2026 14:38:00 -0000 https://status.as205126.net/incident/810718#b60025c6bc78128993d7cb0548c6158d6cfa1c888927dda12c83e066880cde78 Plenty of workflows on Kubernetes have simply stopped working. We cannot investigate due to personal reasons. https://status.as205126.net/incident/799675 Tue, 06 Jan 2026 19:03:00 -0000 https://status.as205126.net/incident/799675#0f06af46888c92777a4b44e11809729b44880bdd25313e4de678c0b071f3b05c We are updating the authentication system. https://status.as205126.net/incident/790717 Fri, 19 Dec 2025 09:18:00 -0000 https://status.as205126.net/incident/790717#539ca197878b4b8fed85252b0b174ca45bebb0f5fb4d514d5cba494b51576559 We are making an automated git server update https://status.as205126.net/incident/786214 Sat, 13 Dec 2025 22:46:00 -0000 https://status.as205126.net/incident/786214#a9416c3f9afda10a79485c4c173ff3761843cdb963df4138e2991ecceecb5726 The Parisian Kubernetes node is now available. https://status.as205126.net/incident/786214 Sat, 13 Dec 2025 21:03:00 -0000 https://status.as205126.net/incident/786214#69aefd359480d8a0f6968a6d61c151fa7340f1decb8468977506f101b6b17428 The Parisian router has been put back online. https://status.as205126.net/incident/786214 Sat, 13 Dec 2025 17:51:00 -0000 https://status.as205126.net/incident/786214#5c608614133ce0593eb0dd2fdb29b4c2a5251155bda91781d52ce94d8ca6c963 We are keeping the par-1 node down for now until the ping gets better. The authentication service is down. https://status.as205126.net/incident/786214 Sat, 13 Dec 2025 17:50:00 -0000 https://status.as205126.net/incident/786214#b5289ab9acb41474e9d3ffbaf99c6d60ab5936ab91d5a362d773c1d33071f123 Most of Kubernetes services have been restarted. https://status.as205126.net/incident/786214 Sat, 13 Dec 2025 17:36:00 -0000 https://status.as205126.net/incident/786214#cb1f3094469dd95a04db91dc0030e581324de98c7f3f8f10f116109c34a2ac0a We suspect that the Kubernetes cluster might be the issue from the beginning. We are restarting all the system. https://status.as205126.net/incident/786214 Sat, 13 Dec 2025 15:17:00 -0000 https://status.as205126.net/incident/786214#8abb58801973530c93c4eac8e24d570dff58b4a7d8b7ed584dde36ebaf2cae8d Our infra ISP has some issue that lead to very high ping (150ms/25% loss). https://status.as205126.net/incident/786219 Thu, 11 Dec 2025 20:24:00 -0000 https://status.as205126.net/incident/786219#294f3d1524bb35f54e24b2acaa4a0898ad8d0efdf5f952f482b591e827bb2c41 While we cannot yet make an investigation, the system has been able to recover by itself. https://status.as205126.net/incident/786219 Thu, 11 Dec 2025 20:18:00 -0000 https://status.as205126.net/incident/786219#da6238d674609d78f0727c58062fa6f8f94a9414c544161db6be796a9d6cf0d4 The prefix (`2a12:bec4:1cf1::/48`) the router announce has been removed from the global routing table. We cannot make an investigation right now, however nothing valuable is routed from that prefix. Note: the affected service is here because I have to select something. https://status.as205126.net/incident/783591 Wed, 10 Dec 2025 04:58:00 -0000 https://status.as205126.net/incident/783591#839e94d417dd04c17c520903156c5ddc19aa35f16d373e9664ffe2a83b0fcc6f While we cannot investigate, the system got online by itself. https://status.as205126.net/incident/783591 Wed, 10 Dec 2025 03:22:00 -0000 https://status.as205126.net/incident/783591#2855b5b9b1adedca83b26d83ba3ca4341eb9fda22bb4ead02c05222c491e0c5d We lost a Kubernetes node connectivity, the incident is due to pods cannot be scheduled to other nodes. https://status.as205126.net/incident/782942 Tue, 09 Dec 2025 11:55:11 -0000 https://status.as205126.net/incident/782942#6e94db6da25fca5a60a38f266083bcedab3a8e819bfa81d27bec12816931dbbd We are updating the authentication system. https://status.as205126.net/incident/781895 Sun, 07 Dec 2025 20:34:00 -0000 https://status.as205126.net/incident/781895#ec00064c71a9c1bed13a2b9cf7851d605f92710b58206491b802b9714f438fba The issue seems to be resolved after a restart of all the services linked to Git server. https://status.as205126.net/incident/781895 Sun, 07 Dec 2025 20:00:00 -0000 https://status.as205126.net/incident/781895#0df4101338060b9ca17d79a000d63ae906294a7be39b9d4f1d1d447c00751cc7 We requested a restart for all the services that are used for the Git server. https://status.as205126.net/incident/781895 Sun, 07 Dec 2025 19:11:00 -0000 https://status.as205126.net/incident/781895#363d8d44cc213af06b3509c0ffaaf22e03870824d4dbba78755b28505b1a091f We are still investigating why the server is slow to respond. However, we can confirm the issue is not the maintenance done earlier, and the status degraded by itself to downtime with most of the requests getting timed out. https://status.as205126.net/incident/781895 Sun, 07 Dec 2025 19:00:00 -0000 https://status.as205126.net/incident/781895#02ee53380cc6c1ce984a260eca418985640c5ef440d2cb4f0d45a1514a00910f Our Git server is unstable, it seems response delay is much higher than usual. We are investigating if the instability is due to the backup system being forced. https://status.as205126.net/incident/781897 Sun, 07 Dec 2025 17:59:52 -0000 https://status.as205126.net/incident/781897#86d8c195d1b8ce893cc91ff33277b87992cfb4d34cf05b9dc93648ff04444fe2 We re-migrate back to our old backup system due to instability of the current one. Services can be degraded for a short amount of time. https://status.as205126.net/incident/776319 Sat, 29 Nov 2025 10:13:00 -0000 https://status.as205126.net/incident/776319#dd9dca7112a81d219e05d64f6de139605a8e9d97fdfe3a6a0b9e79731b76f06b We are updating the authentication server to the last version https://status.as205126.net/incident/775322 Thu, 27 Nov 2025 15:27:00 -0000 https://status.as205126.net/incident/775322#e2e94a701eb5f7847b92d23b38baf9eda6713673fb9bdf65dd4832cb4c5b276d We used another S3 type provider to fetch all the needed files. The incident is now resolved. https://status.as205126.net/incident/775322 Thu, 27 Nov 2025 14:57:00 -0000 https://status.as205126.net/incident/775322#dd9f9ffda44f7322de2d12b8dfea434da29158593dc20e73225bfa6d654f8e37 Our system tried to update the theme automatically and cause a downtime because of a missing file. The previous files are not accessible due to an error from the old S3 backend. https://status.as205126.net/incident/772752 Sun, 23 Nov 2025 22:48:00 -0000 https://status.as205126.net/incident/772752#d9ffc20a8861b952cb6cd1b112d9b2d94de8ebb1d55d6794fc60a66dea0bfd3a We are doing a electrical maintenance on the Paris site. Some of the service there will be impacted. https://status.as205126.net/incident/771862 Fri, 21 Nov 2025 22:13:30 -0000 https://status.as205126.net/incident/771862#96cbfb1e41fa0d08f77ee9062c11be1f7126d7aee86423eeb6649bd23fd6fa33 The system is renewing his certificates https://status.as205126.net/incident/763340 Thu, 13 Nov 2025 00:07:45 -0000 https://status.as205126.net/incident/763340#90fac94bcf11e0bb1b659e2e4e151a231050f69ca0ef4987adaa05ad5933135c We are updating the authentication system https://status.as205126.net/incident/761705 Tue, 11 Nov 2025 12:07:00 -0000 https://status.as205126.net/incident/761705#2876c8128b7faac08c989d48dc191f7eeb1aa4ae4c494039c0728eec7b4ddbec The ping lowered to a normal level, so we assume the connectivity is back again. https://status.as205126.net/incident/761705 Tue, 11 Nov 2025 10:07:00 -0000 https://status.as205126.net/incident/761705#9342e9bea6bdfac641f70cd9da8f5dffa33c449184cf50faa946ee0a37b122e2 The issue seems not resolved, we still have network disturbance. https://status.as205126.net/incident/761705 Tue, 11 Nov 2025 01:00:00 -0000 https://status.as205126.net/incident/761705#2eedf815f812e1ce102becd4075a6b0cfe9e93fdd38dedbdbf379e607485aaac The service is now online. https://status.as205126.net/incident/761705 Mon, 10 Nov 2025 23:58:00 -0000 https://status.as205126.net/incident/761705#ac42b2a4937f77405205481274d73a2c4ca6b3061ee012bd6da3c3a45443e3ce The issue seems to be resolved. The kubernetes cluster needs to resync all the volumes, perturbation is expected. https://status.as205126.net/incident/761705 Mon, 10 Nov 2025 22:05:00 -0000 https://status.as205126.net/incident/761705#02a8308131bbf6bf3c75fdf11df7b409b5562d096a01d09f1e6fcb808e0b1a49 We successfully remove the paris node from Kubernetes LB, there is no more disturbance for the cluster, except less resources. https://status.as205126.net/incident/761705 Mon, 10 Nov 2025 19:13:00 -0000 https://status.as205126.net/incident/761705#d5bdec0c23deef0a9ede42036840006e6592a8a28e86dc5eb7b67e76fa381c29 Our infrastructure internet provider is down. We cannot do anything to resolve this except moving the major workloads thanks to Kubernetes. https://status.as205126.net/incident/761705 Mon, 10 Nov 2025 19:11:00 -0000 https://status.as205126.net/incident/761705#e193e1e95522ccf282f07693cd7b875d914ffa06214263baea497e51d32719ae The Kubernetes cluster managed to move the workload to another site without data loss. After getting some information from the provider, the issue will last 24h: > Vos services devraient être rétablis le 11/11/2025 à 22:00. https://status.as205126.net/incident/759829 Fri, 07 Nov 2025 10:39:53 -0000 https://status.as205126.net/incident/759829#70964004029ba53faf3d0f48d9ac9bf68812883284d1c8ca6ad81032fe75e508 We are updating the authentication system https://status.as205126.net/incident/759215 Thu, 06 Nov 2025 12:25:30 -0000 https://status.as205126.net/incident/759215#42bce5eadac92386f5cda361e66cd2db1db0765285fd789620bf122c06ee61db We are updating the Kubernetes cluster to the latest version. https://status.as205126.net/incident/758838 Wed, 05 Nov 2025 23:25:00 -0000 https://status.as205126.net/incident/758838#a1cb40b706174bbc37834a3ba2c2bfe958a1e3cfa8b031b1f274245b4816b5bb Our internet provider restored the service, no action on our end or needed. https://status.as205126.net/incident/758838 Wed, 05 Nov 2025 23:11:00 -0000 https://status.as205126.net/incident/758838#c3bd01295db1116a8bcd8e83b77fcf97eed0f04d7415e55e18ff6bdee8d3d4bf After some investigation, we cannot connect even on backup VPN nor backup of backup VPN. The issue seems to be 3rd party. https://status.as205126.net/incident/758838 Wed, 05 Nov 2025 23:10:00 -0000 https://status.as205126.net/incident/758838#2419951e960eba34fe50dbea08660fd11f0fa05a84c21bbc44af4fb553c743e4 One of our site, call name `cha`, lost the internet connection. Some of our services went completely down and the Kubernetes endpoint partially down. The issue is from a 3rd party.