Incidents reported on status page for AS205126 https://status.as205126.net/ en https://status.as205126.net/incident/1020835 Thu, 27 Aug 2026 01:49:00 -0000 https://status.as205126.net/incident/1020835#888445c2ada99a5a6a14d5e5ec6ebe599425ea771c8c64c92ecaf100ed117009 The cluster is now in a healthy state. https://status.as205126.net/incident/1020835 Thu, 27 Aug 2026 01:29:00 -0000 https://status.as205126.net/incident/1020835#bb8959bf4d3756410a4911acb7e3da251fe203f0da4b2c86b295bdd3105a2ad3 Everything is now up, still syncing. https://status.as205126.net/incident/1020835 Thu, 27 Aug 2026 00:08:00 -0000 https://status.as205126.net/incident/1020835#ad04f2c24faa51fc2d438cf76a6778925b76d4e4937cfa1351cbb74defce7ebf Status degraded while synchronizing volumes. https://status.as205126.net/incident/1020835 Wed, 26 Aug 2026 22:01:00 -0000 https://status.as205126.net/incident/1020835#2e6917123172f44b099b47ff6730d825f6cc0dd2609811887f1aa6f9dcf93f3a Nodes are syncing each other to updates data. Some minor disruption can occur during that time. https://status.as205126.net/incident/1020835 Wed, 26 Aug 2026 21:58:00 -0000 https://status.as205126.net/incident/1020835#5e9d903308b33e767fb6611e8dfe3015b776ddfe89b58da9caa03f6caff707ba We re-added the node to the cluster but have duplicated resources. We are working on a fix. https://status.as205126.net/incident/1020835 Wed, 26 Aug 2026 00:11:00 -0000 https://status.as205126.net/incident/1020835#57f19b95269869fb501e1a2a5eb359fbe219f44a466030fceec089bc4fd825ea The par-1 issue is resolved. We'll work on the node restoration tomorrow. https://status.as205126.net/incident/1033345 Wed, 26 Aug 2026 00:10:00 -0000 https://status.as205126.net/incident/1033345#02faf4513362f69b14fbb3681e8da17e35ce928e7b91112d746e9aef3c5967c7 Resolved. https://status.as205126.net/incident/1033345 Wed, 26 Aug 2026 00:09:00 -0000 https://status.as205126.net/incident/1033345#0fa6ae7109761a52902f38292ed5b78753ba2bdfe448cedac8b8037a590d8382 Firewall blocked the site IPs. We've unblocked them. Monitoring. https://status.as205126.net/incident/1033345 Wed, 26 Aug 2026 00:05:00 -0000 https://status.as205126.net/incident/1033345#e3dcac66be415d925a1839c8409a1e189f650e770a0eef5c995726367e0b4e7a K8s LB lost connectivity with cha-1 site. https://status.as205126.net/incident/1020835 Wed, 26 Aug 2026 00:03:00 -0000 https://status.as205126.net/incident/1020835#e6146aeb85248277e8fc50233ee3cd8deda8c10f81b3078cf14188b54cac406b registry is ok https://status.as205126.net/incident/1020835 Tue, 25 Aug 2026 23:15:00 -0000 https://status.as205126.net/incident/1020835#69fafef8a1b72462370cf673e14d65868703c54fa25dd794a913d5fcb00f758f On top of that, one of our site lost connectivity and the node cannot recover by itself. We are investigating, and trying to restart node. For the lost node, a week ago, we are preparing a plan to restore everything. https://status.as205126.net/incident/1020835 Thu, 20 Aug 2026 17:49:00 -0000 https://status.as205126.net/incident/1020835#65a276aee080ed867402589be003a5675ac041aa230826cbcd3743cc57ddff09 We are still looking for solutions. https://status.as205126.net/incident/1020835 Wed, 19 Aug 2026 17:23:00 -0000 https://status.as205126.net/incident/1020835#576c6203ea024ac404ab55c181278d7847b06f7e4bd9f57b2ec8b6441665ea5e The node is still not able to be deployed, we increased resources on one of our node to take more workload. Status is still degraded even if services are accessible. https://status.as205126.net/incident/1020835 Wed, 19 Aug 2026 07:48:00 -0000 https://status.as205126.net/incident/1020835#bdbf55352db069883c7404e0731329d2dc0386e47f6bc3c954ad464f9f91d4de We tried to recreate node from backup, but the provider does not have capacity. https://status.as205126.net/incident/1020835 Tue, 18 Aug 2026 23:15:00 -0000 https://status.as205126.net/incident/1020835#227f0693d9e0caebe9bf68c2ca2f23c46351f3a0d83ec0c105dcbcc921c86a33 One of our provider just suspended one our node due to new limitations. https://status.as205126.net/incident/1014843 Sun, 16 Aug 2026 01:43:34 -0000 https://status.as205126.net/incident/1014843#dc49c1b24cc573e8f86848646a98f087354a45c3428b499798d35260ec964a52 We are updating the git server to the latest version. https://status.as205126.net/incident/1012456 Fri, 14 Aug 2026 16:09:02 -0000 https://status.as205126.net/incident/1012456#eb2da652819b214acaeeef5b9ede132d1e9ea3c429daebf3fb058027a982cbca Due to volumes failure, we have to increate node storage. https://status.as205126.net/incident/998420 Thu, 06 Aug 2026 17:59:00 -0000 https://status.as205126.net/incident/998420#632f74d5388938e6c668525efe385cfe11f9c5d0047de97a75cf2fa613a1451a Their maintenance is done. https://status.as205126.net/incident/998420 Thu, 06 Aug 2026 17:50:00 -0000 https://status.as205126.net/incident/998420#f51d4c25f1c23167df20787003aebbbc3072bc880ffe20d0ef0e07ba2c6681b2 An urgent maintenance is in progress without notice from one of our providers. We are sorry for the interruption. https://status.as205126.net/incident/971833 Wed, 22 Jul 2026 00:00:08 -0000 https://status.as205126.net/incident/971833#3612ef280c417b4a5cafe06cf16756cdeb9f1468c5afcb838b9c367e55cbaa16 Our provider is going to do a maintenance on the infrastructure that manager our edge router. A part of our infrastructure will be unreachable. Only the services listed in the maintenance notice will be disturbed. Provider notice: https://status.virtua.cloud/maintenance/cmrtc228f0003p701p0khc6nj https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 15:14:00 -0000 https://status.as205126.net/incident/963668#c99cbb9f69a5ef107fe25e282e63bd3a62f4e9422d08b7ba82baba515a3f9faa Everything is back online. We'll work on a refactor of the load balancer. https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 14:58:00 -0000 https://status.as205126.net/incident/963668#d8cf92705a3abd59a4788883c614a31bfddcf2923397dbb9a4fb93b9362faab2 All the services are now up, but performances are degraded. https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 14:53:00 -0000 https://status.as205126.net/incident/963668#d3cfa0e91673bb790d2656d671449490c13ed3ddc7228d93169315c1e37bb71f Performances degraded due to unwanted PVCs sync due to tunnel restart on our node. https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 14:50:00 -0000 https://status.as205126.net/incident/963668#b832ac15d5b27ec025ce9177f93abd934aa67ba68ac93193eb85b29f29c0ec7a the fix isn't fixing anymore. https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 14:33:00 -0000 https://status.as205126.net/incident/963668#c682d163e41461c9055490d8ed6cbf225e764f6a15e0eb19170a532310ca2e0a the fix is running, services are now accessible but issue still here. we are still working on this. https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 14:28:00 -0000 https://status.as205126.net/incident/963668#b991784eb3794df0d43ee1c263c5a24d753dd129662c8134cbbb910e34507cde We have identified that is wireguard the issue. We are working on a fix. https://status.as205126.net/incident/963668 Tue, 14 Jul 2026 14:20:00 -0000 https://status.as205126.net/incident/963668#ce4b62fd2f37a501b913f6755b05f06553876aa70b6ecdbdadbb41938c215691 One of our kubernetes node is unavailable, the network pipe between the node and the load balancer is broken. We are investigating. https://status.as205126.net/incident/963443 Tue, 14 Jul 2026 08:24:46 -0000 https://status.as205126.net/incident/963443#004c8fe4e7fb25b27c2b21070cead5cdeb375c89825ab0c51a87a015c01dcb7d We are updating the authentication system. https://status.as205126.net/incident/963438 Tue, 14 Jul 2026 08:20:45 -0000 https://status.as205126.net/incident/963438#266af34b37e3b29f971441d1f1572bc5a4639b43f8358d1989396671bbb731d0 We are updating the VPN service https://status.as205126.net/incident/963435 Tue, 14 Jul 2026 08:19:06 -0000 https://status.as205126.net/incident/963435#91f20d2b5f1146393cd96ace32c80ba4c5425a892f17840a3244c54ad3cbf7fc We are updating the git server https://status.as205126.net/incident/962972 Mon, 13 Jul 2026 21:46:06 -0000 https://status.as205126.net/incident/962972#945303db9117d76071fad3ad3c93950c6b30db31f25eea366ac1bb8158e24900 We are updating the registry https://status.as205126.net/incident/961841 Mon, 13 Jul 2026 10:07:26 -0000 https://status.as205126.net/incident/961841#dbc2e1e6261cbfbf8137eac3686dd95c4b88a33298eeb2742c29e8bdf98e35c5 We are updating the registry. https://status.as205126.net/incident/961827 Mon, 13 Jul 2026 10:03:30 -0000 https://status.as205126.net/incident/961827#a81adc60b456e9aa329368f810ea54cbbc699ada575a510cac89d3720a57fed7 We are updating the git server https://status.as205126.net/incident/946118 Tue, 07 Jul 2026 13:47:00 -0000 https://status.as205126.net/incident/946118#884ebf77c549dcfe499d8be21b754eb23393068e9980c99d5583da9ba7ce786d It seems that the issue is resolved our end, but provider is monitoring. https://status.as205126.net/incident/946118 Tue, 07 Jul 2026 13:20:00 -0000 https://status.as205126.net/incident/946118#720bde5764d37f8a57c022e671cfdaae669693cd6f4cd19972c958068a4f7af9 Our load balancer provider is down https://status.as205126.net/incident/977185 Mon, 06 Jul 2026 22:51:58 -0000 https://status.as205126.net/incident/977185#e967457f1479ad02fcda56897e0d779189a6129dd61ea691d640c700096eccc0 Our LB provider told us that they must have to do an urgent update due to [CVE-2026-53359](https://nvd.nist.gov/vuln/detail/CVE-2026-53359). 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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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/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.