Incidents | AS205126 Incidents reported on status page for AS205126 https://status.as205126.net/ en Unplanned git upgrade 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. Git server recovered https://status.as205126.net/ Sun, 19 Apr 2026 11:17:25 +0000 https://status.as205126.net/#2c88b2859c8e126e029f18ec3dafa54c0a9f61e670b0e5585b5bd9cfecce5707 Git server recovered Git server went down https://status.as205126.net/ Sun, 19 Apr 2026 10:53:35 +0000 https://status.as205126.net/#2c88b2859c8e126e029f18ec3dafa54c0a9f61e670b0e5585b5bd9cfecce5707 Git server went down Unplanned git 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. Kubernetes load balancer upstream down 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. Git server recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:56:31 +0000 https://status.as205126.net/#92830524aa84d18419b4496cc92fb50acf3e883bca430cee6202f52f43a34e26 Git server recovered VPN service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:56:31 +0000 https://status.as205126.net/#e01bcd2b57ac6f67248b7cd0c94afdc365d8bb716a848bb9f4677a7763bc1aa8 VPN service recovered Authentication service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:55:46 +0000 https://status.as205126.net/#e55ca56adbb6bffc9161dddad5922a5a20e1975831f364dba20eb5ed7abfe89c Authentication service recovered Load balancer recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:55:11 +0000 https://status.as205126.net/#1fc17db1bcd1086c2b3ce1a1fee976a2513c0036830df3e2786b8f612989cbcc Load balancer recovered Docker&Helm registry recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:54:36 +0000 https://status.as205126.net/#f5e21c4f7e97fa64d64eedad2f89abc250be6ab65ad264bb0c2016ac3e04489f Docker&Helm registry recovered Kubernetes load balancer upstream down 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. Kubernetes load balancer upstream down 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. Docker&Helm registry went down https://status.as205126.net/ Sat, 18 Apr 2026 09:46:48 +0000 https://status.as205126.net/#f5e21c4f7e97fa64d64eedad2f89abc250be6ab65ad264bb0c2016ac3e04489f Docker&Helm registry went down Git server went down https://status.as205126.net/ Sat, 18 Apr 2026 09:46:30 +0000 https://status.as205126.net/#92830524aa84d18419b4496cc92fb50acf3e883bca430cee6202f52f43a34e26 Git server went down Authentication service went down https://status.as205126.net/ Sat, 18 Apr 2026 09:45:38 +0000 https://status.as205126.net/#e55ca56adbb6bffc9161dddad5922a5a20e1975831f364dba20eb5ed7abfe89c Authentication service went down VPN service went down https://status.as205126.net/ Sat, 18 Apr 2026 09:45:29 +0000 https://status.as205126.net/#e01bcd2b57ac6f67248b7cd0c94afdc365d8bb716a848bb9f4677a7763bc1aa8 VPN service went down Kubernetes load balancer upstream 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. Load balancer went down https://status.as205126.net/ Sat, 18 Apr 2026 09:43:37 +0000 https://status.as205126.net/#1fc17db1bcd1086c2b3ce1a1fee976a2513c0036830df3e2786b8f612989cbcc Load balancer went down Docker&Helm registry recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:36:01 +0000 https://status.as205126.net/#9c0e5133e3a4a5f0f3a6ead2682a7450e9daa12a3af267aa51627c695665c94a Docker&Helm registry recovered Git server recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:35:38 +0000 https://status.as205126.net/#d7b02d4dcd7d331d2d7239337d6ae101f22dd19ba6a38f555fb6edb70b0c0b20 Git server recovered VPN service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:35:37 +0000 https://status.as205126.net/#ed34f88af2fa233b63d7d4951d602bfa92b99dfe6aeb3f277abb66be193e7a5d VPN service recovered Authentication service recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:34:35 +0000 https://status.as205126.net/#3489a2b9d6179b4a6ae854b1edc2ef5ef754dd2cce6abb9e75a55f0489a25581 Authentication service recovered Load balancer recovered https://status.as205126.net/ Sat, 18 Apr 2026 09:34:10 +0000 https://status.as205126.net/#5e40bbba43aab96dc39b71d9a691fdda3ebe8c6b3cc67292e1ea7c7fd3593c19 Load balancer recovered Git server went down https://status.as205126.net/ Sat, 18 Apr 2026 08:49:30 +0000 https://status.as205126.net/#d7b02d4dcd7d331d2d7239337d6ae101f22dd19ba6a38f555fb6edb70b0c0b20 Git server went down Authentication service went down https://status.as205126.net/ Sat, 18 Apr 2026 08:48:40 +0000 https://status.as205126.net/#3489a2b9d6179b4a6ae854b1edc2ef5ef754dd2cce6abb9e75a55f0489a25581 Authentication service went down VPN service went down https://status.as205126.net/ Sat, 18 Apr 2026 08:48:30 +0000 https://status.as205126.net/#ed34f88af2fa233b63d7d4951d602bfa92b99dfe6aeb3f277abb66be193e7a5d VPN service went down Load balancer went down https://status.as205126.net/ Sat, 18 Apr 2026 08:47:10 +0000 https://status.as205126.net/#5e40bbba43aab96dc39b71d9a691fdda3ebe8c6b3cc67292e1ea7c7fd3593c19 Load balancer went down Docker&Helm registry went down https://status.as205126.net/ Sat, 18 Apr 2026 08:45:53 +0000 https://status.as205126.net/#9c0e5133e3a4a5f0f3a6ead2682a7450e9daa12a3af267aa51627c695665c94a Docker&Helm registry went down Git server recovered https://status.as205126.net/ Wed, 15 Apr 2026 20:17:28 +0000 https://status.as205126.net/#5b34173489eaba691718a2c01d7e841f490b9b3316bf8798973357ec95d2edde Git server recovered Git server went down https://status.as205126.net/ Wed, 15 Apr 2026 19:47:32 +0000 https://status.as205126.net/#5b34173489eaba691718a2c01d7e841f490b9b3316bf8798973357ec95d2edde Git server went down Updating Git server 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 Git server recovered https://status.as205126.net/ Tue, 14 Apr 2026 22:08:33 +0000 https://status.as205126.net/#c5e022164669fba3f26275ef451412b5b2e3b28d634c6ee65ef9f2c8534d8cf5 Git server recovered Authentication service recovered https://status.as205126.net/ Tue, 14 Apr 2026 22:04:44 +0000 https://status.as205126.net/#218fd2231f0681206b2629e13c17f463befff9dc12891df762b1fa68cfe425f2 Authentication service recovered Git server went down https://status.as205126.net/ Tue, 14 Apr 2026 22:02:36 +0000 https://status.as205126.net/#c5e022164669fba3f26275ef451412b5b2e3b28d634c6ee65ef9f2c8534d8cf5 Git server went down Authentication service went down https://status.as205126.net/ Tue, 14 Apr 2026 21:58:46 +0000 https://status.as205126.net/#218fd2231f0681206b2629e13c17f463befff9dc12891df762b1fa68cfe425f2 Authentication service went down Updating Kubernetes cluster version 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 AS205126 - par recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:30:25 +0000 https://status.as205126.net/#77e282d32d0bb9a4f1b20ef4cbd8477942b94b0f4d737a8429c1f80478d092cc AS205126 - par recovered AS205126 - cha recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:29:54 +0000 https://status.as205126.net/#93290f1aed21e9d67e63fe2b4e822f8096520f5a5301fe0c181edeff889e4f3c AS205126 - cha recovered Edge 1 Paris recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:29:36 +0000 https://status.as205126.net/#21c14db6eda328eb05b248cb996816130a7bca9faad28573f45fb2261b52eb6c Edge 1 Paris recovered as205126.net recovered https://status.as205126.net/ Tue, 14 Apr 2026 16:29:24 +0000 https://status.as205126.net/#1a1d3f48c0aa28444bd8fd4d905a17dbb64e48f71d73ca4da9fc57f2b759c92a as205126.net recovered as205126.net went down https://status.as205126.net/ Tue, 14 Apr 2026 16:27:14 +0000 https://status.as205126.net/#1a1d3f48c0aa28444bd8fd4d905a17dbb64e48f71d73ca4da9fc57f2b759c92a as205126.net went down AS205126 - cha went down https://status.as205126.net/ Tue, 14 Apr 2026 16:27:07 +0000 https://status.as205126.net/#93290f1aed21e9d67e63fe2b4e822f8096520f5a5301fe0c181edeff889e4f3c AS205126 - cha went down Edge 1 Paris went down https://status.as205126.net/ Tue, 14 Apr 2026 16:27:05 +0000 https://status.as205126.net/#21c14db6eda328eb05b248cb996816130a7bca9faad28573f45fb2261b52eb6c Edge 1 Paris went down AS205126 - par went down https://status.as205126.net/ Tue, 14 Apr 2026 16:24:53 +0000 https://status.as205126.net/#77e282d32d0bb9a4f1b20ef4cbd8477942b94b0f4d737a8429c1f80478d092cc AS205126 - par went down Authentication service recovered https://status.as205126.net/ Mon, 13 Apr 2026 06:55:41 +0000 https://status.as205126.net/#5fbbf91379550db504a9defb88b0b01fb187ae1c4376e7a466be663b630068c8 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 13 Apr 2026 06:04:36 +0000 https://status.as205126.net/#5fbbf91379550db504a9defb88b0b01fb187ae1c4376e7a466be663b630068c8 Authentication service went down Authentication service recovered https://status.as205126.net/ Sun, 12 Apr 2026 01:25:10 +0000 https://status.as205126.net/#89c84b991647b4a2ede19081a0438a7201eceb88256db867c4038db56b7c9aa0 Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 12 Apr 2026 01:19:44 +0000 https://status.as205126.net/#89c84b991647b4a2ede19081a0438a7201eceb88256db867c4038db56b7c9aa0 Authentication service went down Authentication system update 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. Authentication ingress changes 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. Registry ingress changes 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. Docker&Helm registry recovered https://status.as205126.net/ Sat, 11 Apr 2026 18:29:47 +0000 https://status.as205126.net/#73235a1a95a26af031b739eb7ea07bc2c1a2d231f302de919629a0e8972e5904 Docker&Helm registry recovered Docker&Helm registry went down https://status.as205126.net/ Sat, 11 Apr 2026 18:23:49 +0000 https://status.as205126.net/#73235a1a95a26af031b739eb7ea07bc2c1a2d231f302de919629a0e8972e5904 Docker&Helm registry went down Testing new LB update 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. AS205126 - cha recovered https://status.as205126.net/ Wed, 08 Apr 2026 08:11:48 +0000 https://status.as205126.net/#e6c17fb94463361e72a2375db39f9541c915302e71e4417af1bdd8998b6fc7f0 AS205126 - cha recovered AS205126 - cha went down https://status.as205126.net/ Wed, 08 Apr 2026 08:09:07 +0000 https://status.as205126.net/#e6c17fb94463361e72a2375db39f9541c915302e71e4417af1bdd8998b6fc7f0 AS205126 - cha went down Docker&Helm registry recovered https://status.as205126.net/ Wed, 08 Apr 2026 00:17:57 +0000 https://status.as205126.net/#64f4a4748352d064f00305b8028ac153a36322d83314607d5d0e385d80d0da29 Docker&Helm registry recovered as205126.net recovered https://status.as205126.net/ Wed, 08 Apr 2026 00:17:22 +0000 https://status.as205126.net/#be75a2f86f65557e42594f5f1362ecd7dc459fdc0f7ac8c5713516626ee452cc as205126.net recovered AS205126 - cha recovered https://status.as205126.net/ Wed, 08 Apr 2026 00:14:50 +0000 https://status.as205126.net/#7cfb9147bd214a8db30b3bd0f77d3028ddf7de7986b59ee70bc8165a1e1da89d AS205126 - cha recovered Docker&Helm registry went down https://status.as205126.net/ Wed, 08 Apr 2026 00:12:18 +0000 https://status.as205126.net/#64f4a4748352d064f00305b8028ac153a36322d83314607d5d0e385d80d0da29 Docker&Helm registry went down as205126.net went down https://status.as205126.net/ Wed, 08 Apr 2026 00:12:18 +0000 https://status.as205126.net/#be75a2f86f65557e42594f5f1362ecd7dc459fdc0f7ac8c5713516626ee452cc as205126.net went down AS205126 - cha went down https://status.as205126.net/ Wed, 08 Apr 2026 00:12:11 +0000 https://status.as205126.net/#7cfb9147bd214a8db30b3bd0f77d3028ddf7de7986b59ee70bc8165a1e1da89d AS205126 - cha went down AS205126 - cha recovered https://status.as205126.net/ Fri, 03 Apr 2026 23:53:43 +0000 https://status.as205126.net/#5b0eba9efb0d330635b71a4c377a4bfc287b2158ddf45edf550308a32b95d4b9 AS205126 - cha recovered as205126.net recovered https://status.as205126.net/ Fri, 03 Apr 2026 23:53:18 +0000 https://status.as205126.net/#de5a915ad8e2194885fb7e622057328388d972c19692d96a51064e226b4d8f55 as205126.net recovered as205126.net went down https://status.as205126.net/ Fri, 03 Apr 2026 23:51:19 +0000 https://status.as205126.net/#de5a915ad8e2194885fb7e622057328388d972c19692d96a51064e226b4d8f55 as205126.net went down AS205126 - cha went down https://status.as205126.net/ Fri, 03 Apr 2026 23:51:18 +0000 https://status.as205126.net/#5b0eba9efb0d330635b71a4c377a4bfc287b2158ddf45edf550308a32b95d4b9 AS205126 - cha went down Authentication service recovered https://status.as205126.net/ Thu, 02 Apr 2026 22:13:38 +0000 https://status.as205126.net/#ed71fc002ed697609c98e23297050ae1454bf182f16f55d3e23f2f88fd9020e6 Authentication service recovered Authentication service went down https://status.as205126.net/ Thu, 02 Apr 2026 22:07:42 +0000 https://status.as205126.net/#ed71fc002ed697609c98e23297050ae1454bf182f16f55d3e23f2f88fd9020e6 Authentication service went down Authentication service recovered https://status.as205126.net/ Thu, 02 Apr 2026 21:58:44 +0000 https://status.as205126.net/#4f6c3b031648f76d5636f52df13420c85fa5ee88de3ae34c0c870ffabb4375d5 Authentication service recovered Authentication service went down https://status.as205126.net/ Thu, 02 Apr 2026 21:49:44 +0000 https://status.as205126.net/#4f6c3b031648f76d5636f52df13420c85fa5ee88de3ae34c0c870ffabb4375d5 Authentication service went down Updating the authentication system theme 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. Kubernetes communication error 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. Kubernetes communication error https://status.as205126.net/incident/858966 Wed, 01 Apr 2026 17:55:00 -0000 https://status.as205126.net/incident/858966#c4055b5d7a4123c1a5252995ba4fa8650e1f5158869ec5346bcc2b54997c9975 We are investigating. Authentication service recovered https://status.as205126.net/ Wed, 01 Apr 2026 17:22:44 +0000 https://status.as205126.net/#c1a559aeb6f7d569639d2e55c071acb9cfc9a2359e5110268e40c735912ff859 Authentication service recovered Authentication service went down https://status.as205126.net/ Wed, 01 Apr 2026 17:16:42 +0000 https://status.as205126.net/#c1a559aeb6f7d569639d2e55c071acb9cfc9a2359e5110268e40c735912ff859 Authentication service went down Kubernetes communication error 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. Authentication service recovered https://status.as205126.net/ Sat, 28 Mar 2026 04:04:41 +0000 https://status.as205126.net/#88182d6df4381b6c48693112b42f84ca5891cb74fec18aee858a4c79cdce5660 Authentication service recovered Kubernetes communication error 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. Authentication service went down https://status.as205126.net/ Sat, 28 Mar 2026 03:44:39 +0000 https://status.as205126.net/#88182d6df4381b6c48693112b42f84ca5891cb74fec18aee858a4c79cdce5660 Authentication service went down Authentication service recovered https://status.as205126.net/ Sat, 28 Mar 2026 03:40:37 +0000 https://status.as205126.net/#263a57abef60d36baf0d092c438380c48489b237b238ab99b0d1e21cb8433c41 Authentication service recovered Load balancer recovered https://status.as205126.net/ Sat, 28 Mar 2026 02:58:10 +0000 https://status.as205126.net/#16ed878e2417a8bafb2cc85598f62bc35e0121ef9183f3d84b1c83ccb56250a1 Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 28 Mar 2026 02:55:36 +0000 https://status.as205126.net/#16ed878e2417a8bafb2cc85598f62bc35e0121ef9183f3d84b1c83ccb56250a1 Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 28 Mar 2026 02:37:06 +0000 https://status.as205126.net/#40b842bc7474e9e82a78235f2b03b2a092dfd2ec2fb0d22764f9e030e67d66aa Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 28 Mar 2026 02:07:38 +0000 https://status.as205126.net/#40b842bc7474e9e82a78235f2b03b2a092dfd2ec2fb0d22764f9e030e67d66aa Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 28 Mar 2026 01:49:09 +0000 https://status.as205126.net/#e425c170dc16d775ab90300804e08e2371965125ef2a98c765c218b8bb84e26a Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 28 Mar 2026 01:31:38 +0000 https://status.as205126.net/#e425c170dc16d775ab90300804e08e2371965125ef2a98c765c218b8bb84e26a Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 28 Mar 2026 00:10:11 +0000 https://status.as205126.net/#fcb701d93eb1af625d49a6f90df6814c932a43c14f43ea54d09d70d1fa0acaf4 Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 28 Mar 2026 00:04:36 +0000 https://status.as205126.net/#fcb701d93eb1af625d49a6f90df6814c932a43c14f43ea54d09d70d1fa0acaf4 Load balancer went down Authentication service went down https://status.as205126.net/ Fri, 27 Mar 2026 22:38:08 +0000 https://status.as205126.net/#263a57abef60d36baf0d092c438380c48489b237b238ab99b0d1e21cb8433c41 Authentication service went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 22:34:09 +0000 https://status.as205126.net/#3196ac3760d1789af079ba7ece6a0f09a09a9f7b9e7ac9001737bd4614b10a4f Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 22:31:40 +0000 https://status.as205126.net/#3196ac3760d1789af079ba7ece6a0f09a09a9f7b9e7ac9001737bd4614b10a4f Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 22:13:08 +0000 https://status.as205126.net/#adc84d6af747cba8e3d1159ca87b7f24c75eca33770a5e6c06559d9ccf5d177c Load balancer recovered Authentication service recovered https://status.as205126.net/ Fri, 27 Mar 2026 22:07:40 +0000 https://status.as205126.net/#f5690892bba0952d374eb27854b2fae825f18c19ff58460008e3ab28fb304721 Authentication service recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 22:01:37 +0000 https://status.as205126.net/#adc84d6af747cba8e3d1159ca87b7f24c75eca33770a5e6c06559d9ccf5d177c Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 21:52:13 +0000 https://status.as205126.net/#2cedfb3bf8858fde54db6de7a047d078861e6dea8b57ac3c4710d10b0fd8f135 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 21:31:37 +0000 https://status.as205126.net/#2cedfb3bf8858fde54db6de7a047d078861e6dea8b57ac3c4710d10b0fd8f135 Load balancer went down Authentication service went down https://status.as205126.net/ Fri, 27 Mar 2026 21:11:39 +0000 https://status.as205126.net/#f5690892bba0952d374eb27854b2fae825f18c19ff58460008e3ab28fb304721 Authentication service went down Authentication service recovered https://status.as205126.net/ Fri, 27 Mar 2026 21:07:42 +0000 https://status.as205126.net/#7c3292941e7fcb9d871bc593c839d802784b3471c5dafda97dd7bc85e3b68803 Authentication service recovered Authentication service went down https://status.as205126.net/ Fri, 27 Mar 2026 20:26:08 +0000 https://status.as205126.net/#7c3292941e7fcb9d871bc593c839d802784b3471c5dafda97dd7bc85e3b68803 Authentication service went down Authentication service recovered https://status.as205126.net/ Fri, 27 Mar 2026 20:16:40 +0000 https://status.as205126.net/#6935cc6a5f04968c9d36d79c898e07a47161b7a83053e0f8ea781b40157fa48e Authentication service recovered Authentication service went down https://status.as205126.net/ Fri, 27 Mar 2026 20:05:40 +0000 https://status.as205126.net/#6935cc6a5f04968c9d36d79c898e07a47161b7a83053e0f8ea781b40157fa48e Authentication service went down Authentication service recovered https://status.as205126.net/ Fri, 27 Mar 2026 20:01:36 +0000 https://status.as205126.net/#3bc8c95902661663d05e46f82913fdaad3f3e20c90b82bbaaf47d9f4e0f2a08c Authentication service recovered Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 20:01:07 +0000 https://status.as205126.net/#7affe9b5756e7ea29defd211602d6dfef2e7f1550fd3235d69a87d8a1e647fe2 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 19:43:35 +0000 https://status.as205126.net/#7affe9b5756e7ea29defd211602d6dfef2e7f1550fd3235d69a87d8a1e647fe2 Load balancer went down Kubernetes communication error 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. Authentication service went down https://status.as205126.net/ Fri, 27 Mar 2026 19:29:39 +0000 https://status.as205126.net/#3bc8c95902661663d05e46f82913fdaad3f3e20c90b82bbaaf47d9f4e0f2a08c Authentication service went down Authentication service recovered https://status.as205126.net/ Fri, 27 Mar 2026 19:25:36 +0000 https://status.as205126.net/#fe5e76f5a93e9117151afbbd0b9cc9599e6c4ff05a57910a8ce1cd7d8c64140f Authentication service recovered Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 18:52:09 +0000 https://status.as205126.net/#f92d40768efd686edfced68210b5e3e59b97ffeef76a6afbe5418f96cad8ea0b Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 18:02:10 +0000 https://status.as205126.net/#f92d40768efd686edfced68210b5e3e59b97ffeef76a6afbe5418f96cad8ea0b Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 17:58:09 +0000 https://status.as205126.net/#51fc5b8ef48fee25c8e16787f98453b2e62095e925c4a4e40f995372108493cd Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 16:44:06 +0000 https://status.as205126.net/#51fc5b8ef48fee25c8e16787f98453b2e62095e925c4a4e40f995372108493cd Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 16:40:13 +0000 https://status.as205126.net/#f2ca21d1d658d5184482077e73576fce0e444de7af397fd5afc6d340b569d437 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 14:49:36 +0000 https://status.as205126.net/#f2ca21d1d658d5184482077e73576fce0e444de7af397fd5afc6d340b569d437 Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 14:34:11 +0000 https://status.as205126.net/#18d00847ec0c44af609a3bb924770c4928adcc65dbf3211d74d7251ec2a23db9 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 14:31:38 +0000 https://status.as205126.net/#18d00847ec0c44af609a3bb924770c4928adcc65dbf3211d74d7251ec2a23db9 Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 14:19:09 +0000 https://status.as205126.net/#4b07b0b9ec43a70ddadba2dbba13330034eaff30722c18ee746f08feec6139fb Load balancer recovered Git server recovered https://status.as205126.net/ Fri, 27 Mar 2026 12:41:30 +0000 https://status.as205126.net/#dd5721e4f946ceb09a06128cb9cafd566664d7a709f1383127587c3fb42678a4 Git server recovered Git server went down https://status.as205126.net/ Fri, 27 Mar 2026 12:32:30 +0000 https://status.as205126.net/#dd5721e4f946ceb09a06128cb9cafd566664d7a709f1383127587c3fb42678a4 Git server went down Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 12:23:08 +0000 https://status.as205126.net/#4b07b0b9ec43a70ddadba2dbba13330034eaff30722c18ee746f08feec6139fb Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 12:19:10 +0000 https://status.as205126.net/#873eee37d35389818c2c9efc8fa323505c16508297dc1bf8c750a94e7a73e614 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 11:25:39 +0000 https://status.as205126.net/#873eee37d35389818c2c9efc8fa323505c16508297dc1bf8c750a94e7a73e614 Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 11:16:11 +0000 https://status.as205126.net/#c2466aa1ea729f16dae59ae44403053fa88988ca3483c7230c943e59aae42452 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 10:01:35 +0000 https://status.as205126.net/#c2466aa1ea729f16dae59ae44403053fa88988ca3483c7230c943e59aae42452 Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 09:43:09 +0000 https://status.as205126.net/#dd6756eb6ab629213d3b70acbe729e2e34fc622dfb103d71c59c0b76fb69420e Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 09:08:07 +0000 https://status.as205126.net/#dd6756eb6ab629213d3b70acbe729e2e34fc622dfb103d71c59c0b76fb69420e Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 09:04:08 +0000 https://status.as205126.net/#a12ce77a11af94fb143098217606d16e53c32eac8f082ed2af8837abc7371538 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 08:19:35 +0000 https://status.as205126.net/#a12ce77a11af94fb143098217606d16e53c32eac8f082ed2af8837abc7371538 Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 07:40:14 +0000 https://status.as205126.net/#0d99cde1c282c52e49875eb729dc20e4078d10e4c1022b43bdb69e701a26aeaa Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 05:04:35 +0000 https://status.as205126.net/#0d99cde1c282c52e49875eb729dc20e4078d10e4c1022b43bdb69e701a26aeaa Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 04:58:10 +0000 https://status.as205126.net/#6652cd1a64af279e913a868bfb7af6f772e0f6652a7f1f95f25281747ca6b24e Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 04:16:36 +0000 https://status.as205126.net/#6652cd1a64af279e913a868bfb7af6f772e0f6652a7f1f95f25281747ca6b24e Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 04:10:10 +0000 https://status.as205126.net/#e78da60bd9c9d1146aed33327a155f1e909bda0f006f07937f1594b0cb831338 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 27 Mar 2026 00:22:35 +0000 https://status.as205126.net/#e78da60bd9c9d1146aed33327a155f1e909bda0f006f07937f1594b0cb831338 Load balancer went down Load balancer recovered https://status.as205126.net/ Fri, 27 Mar 2026 00:10:14 +0000 https://status.as205126.net/#474975107c27a2ff89323b0a16424e0c7e1d3a91e13c9490b15f7cfc2b0a15ff Load balancer recovered Load balancer went down https://status.as205126.net/ Thu, 26 Mar 2026 22:17:09 +0000 https://status.as205126.net/#474975107c27a2ff89323b0a16424e0c7e1d3a91e13c9490b15f7cfc2b0a15ff Load balancer went down Load balancer recovered https://status.as205126.net/ Thu, 26 Mar 2026 22:07:08 +0000 https://status.as205126.net/#25c271225e896d6ff5e2a30035fa25dd02a48feb6e9781dae88f8055f054861b Load balancer recovered Load balancer went down https://status.as205126.net/ Thu, 26 Mar 2026 21:28:39 +0000 https://status.as205126.net/#25c271225e896d6ff5e2a30035fa25dd02a48feb6e9781dae88f8055f054861b Load balancer went down Load balancer recovered https://status.as205126.net/ Thu, 26 Mar 2026 21:13:07 +0000 https://status.as205126.net/#8038506d01c91aada98967926bd9f6958fff6c8b054be5d3f385ca744df0ca10 Load balancer recovered Load balancer went down https://status.as205126.net/ Thu, 26 Mar 2026 19:52:36 +0000 https://status.as205126.net/#8038506d01c91aada98967926bd9f6958fff6c8b054be5d3f385ca744df0ca10 Load balancer went down Authentication service went down https://status.as205126.net/ Thu, 26 Mar 2026 18:59:08 +0000 https://status.as205126.net/#fe5e76f5a93e9117151afbbd0b9cc9599e6c4ff05a57910a8ce1cd7d8c64140f Authentication service went down Kubernetes communication error 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. Authentication service recovered https://status.as205126.net/ Thu, 26 Mar 2026 18:49:40 +0000 https://status.as205126.net/#02a847e72067e60b59bd738a09ae81ae2d1c5382eeb36adc115c6e6d1387b271 Authentication service recovered Load balancer recovered https://status.as205126.net/ Thu, 26 Mar 2026 18:10:12 +0000 https://status.as205126.net/#ebe44a143f58ffc14e5ecfe5378fc89695749e5f9c9966a0e79bee71f1763f0c Load balancer recovered Load balancer went down https://status.as205126.net/ Thu, 26 Mar 2026 17:40:37 +0000 https://status.as205126.net/#ebe44a143f58ffc14e5ecfe5378fc89695749e5f9c9966a0e79bee71f1763f0c Load balancer went down Load balancer recovered https://status.as205126.net/ Thu, 26 Mar 2026 16:34:05 +0000 https://status.as205126.net/#25dda154ae25ddb4ed437161795b13f915fcc52db64dd7cb6a6fef8305efa554 Load balancer recovered Load balancer went down https://status.as205126.net/ Thu, 26 Mar 2026 16:19:37 +0000 https://status.as205126.net/#25dda154ae25ddb4ed437161795b13f915fcc52db64dd7cb6a6fef8305efa554 Load balancer went down Load balancer recovered https://status.as205126.net/ Thu, 26 Mar 2026 14:58:13 +0000 https://status.as205126.net/#9d7e89cb07a08a1a5f3cfef0465fc95e8d9e517cc83bbbf831dad4f4f16eb995 Load balancer recovered Load balancer went down https://status.as205126.net/ Thu, 26 Mar 2026 14:52:39 +0000 https://status.as205126.net/#9d7e89cb07a08a1a5f3cfef0465fc95e8d9e517cc83bbbf831dad4f4f16eb995 Load balancer went down Authentication service went down https://status.as205126.net/ Thu, 26 Mar 2026 14:38:38 +0000 https://status.as205126.net/#02a847e72067e60b59bd738a09ae81ae2d1c5382eeb36adc115c6e6d1387b271 Authentication service went down Git server recovered https://status.as205126.net/ Wed, 25 Mar 2026 16:44:30 +0000 https://status.as205126.net/#6ce38e275d5a5203684c32c7be2ff5889be319dfd334f403438a86b4eaba25ce Git server recovered Authentication service recovered https://status.as205126.net/ Wed, 25 Mar 2026 00:31:39 +0000 https://status.as205126.net/#7e34cad09a95da1c2681ab0cb7bd982bdb604d8ff7597c393a3e0731028f91a6 Authentication service recovered AS205126 - par recovered https://status.as205126.net/ Wed, 25 Mar 2026 00:24:26 +0000 https://status.as205126.net/#ce1862c2a567f95158ee0f1c3ecce3e45bae147f7116532f6a4e1e455c37953e AS205126 - par recovered Load balancer recovered https://status.as205126.net/ Wed, 25 Mar 2026 00:16:16 +0000 https://status.as205126.net/#b8aff7c04cca49a65a618de14501f487c6ec266f372d8b47841979e6044f3a04 Load balancer recovered Docker&Helm registry recovered https://status.as205126.net/ Wed, 25 Mar 2026 00:15:08 +0000 https://status.as205126.net/#53a47d2224d324fbeddc44f02399a213e6a803ae093ee8baed82b4277a9b441e Docker&Helm registry recovered Load balancer went down https://status.as205126.net/ Wed, 25 Mar 2026 00:10:40 +0000 https://status.as205126.net/#b8aff7c04cca49a65a618de14501f487c6ec266f372d8b47841979e6044f3a04 Load balancer went down Git server went down https://status.as205126.net/ Wed, 25 Mar 2026 00:10:26 +0000 https://status.as205126.net/#6ce38e275d5a5203684c32c7be2ff5889be319dfd334f403438a86b4eaba25ce Git server went down AS205126 - par went down https://status.as205126.net/ Wed, 25 Mar 2026 00:09:54 +0000 https://status.as205126.net/#ce1862c2a567f95158ee0f1c3ecce3e45bae147f7116532f6a4e1e455c37953e AS205126 - par went down Docker&Helm registry went down https://status.as205126.net/ Wed, 25 Mar 2026 00:08:48 +0000 https://status.as205126.net/#53a47d2224d324fbeddc44f02399a213e6a803ae093ee8baed82b4277a9b441e Docker&Helm registry went down Authentication service went down https://status.as205126.net/ Wed, 25 Mar 2026 00:08:13 +0000 https://status.as205126.net/#7e34cad09a95da1c2681ab0cb7bd982bdb604d8ff7597c393a3e0731028f91a6 Authentication service went down Load balancer recovered https://status.as205126.net/ Tue, 24 Mar 2026 14:55:08 +0000 https://status.as205126.net/#665c98dd4b7edf78bef589ef9dddfea55f8d6853d3c75adbc00933ac051c3392 Load balancer recovered Load balancer went down https://status.as205126.net/ Tue, 24 Mar 2026 14:52:09 +0000 https://status.as205126.net/#665c98dd4b7edf78bef589ef9dddfea55f8d6853d3c75adbc00933ac051c3392 Load balancer went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 17:19:36 +0000 https://status.as205126.net/#bad2f3e80130360b998416ca76c5fd2d27019840351dc313493dd5fff8a957d3 Authentication service recovered VPN service recovered https://status.as205126.net/ Mon, 23 Mar 2026 17:05:25 +0000 https://status.as205126.net/#0f6724ea3df9a7315bd65225c2823c930ba18bde2b235126d093356a1476dc2c VPN service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 17:05:10 +0000 https://status.as205126.net/#bad2f3e80130360b998416ca76c5fd2d27019840351dc313493dd5fff8a957d3 Authentication service went down Git server recovered https://status.as205126.net/ Mon, 23 Mar 2026 16:47:26 +0000 https://status.as205126.net/#4222e3a0ecb02c9a0bfe669d31f9b17a1a459651b8f3673df077d65c8e51a7d8 Git server recovered Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 16:46:42 +0000 https://status.as205126.net/#2c262e211428c33a75eb67976d03f5a2373c1d8e0cec1f45ff4199be4c2738e8 Authentication service recovered Git server went down https://status.as205126.net/ Mon, 23 Mar 2026 16:32:38 +0000 https://status.as205126.net/#4222e3a0ecb02c9a0bfe669d31f9b17a1a459651b8f3673df077d65c8e51a7d8 Git server went down Load balancer recovered https://status.as205126.net/ Mon, 23 Mar 2026 16:19:12 +0000 https://status.as205126.net/#1facc7d6e95ced67724c9c15f2b6f44708baa41e47e66cc122da6be296b19021 Load balancer recovered Load balancer went down https://status.as205126.net/ Mon, 23 Mar 2026 16:16:33 +0000 https://status.as205126.net/#1facc7d6e95ced67724c9c15f2b6f44708baa41e47e66cc122da6be296b19021 Load balancer went down VPN service went down https://status.as205126.net/ Mon, 23 Mar 2026 16:14:39 +0000 https://status.as205126.net/#0f6724ea3df9a7315bd65225c2823c930ba18bde2b235126d093356a1476dc2c VPN service went down Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 16:13:39 +0000 https://status.as205126.net/#2c262e211428c33a75eb67976d03f5a2373c1d8e0cec1f45ff4199be4c2738e8 Authentication service went down Kubernetes cluster restart 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. Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 15:52:43 +0000 https://status.as205126.net/#ef738595a7a2f350011360aae51b7b5a29d74542b39163607bac8f373378919f Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 15:47:10 +0000 https://status.as205126.net/#ef738595a7a2f350011360aae51b7b5a29d74542b39163607bac8f373378919f Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 13:37:40 +0000 https://status.as205126.net/#e67156b22c6a15da400010a774e72b95e5d265b1b10d35f4a715eecac675333e Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 13:23:10 +0000 https://status.as205126.net/#e67156b22c6a15da400010a774e72b95e5d265b1b10d35f4a715eecac675333e Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 13:13:42 +0000 https://status.as205126.net/#43aacca7311ee630ac717f8e8185b135f993f0b9c0e297d8774d611a07a5b449 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 12:56:41 +0000 https://status.as205126.net/#43aacca7311ee630ac717f8e8185b135f993f0b9c0e297d8774d611a07a5b449 Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 10:46:42 +0000 https://status.as205126.net/#b338a8224f19e53e16d497f436d7cfbca959c4d395769db5b37d12b5d620d5e4 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 10:41:11 +0000 https://status.as205126.net/#b338a8224f19e53e16d497f436d7cfbca959c4d395769db5b37d12b5d620d5e4 Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 10:04:43 +0000 https://status.as205126.net/#5c27aab4315ceed3594a82ecbbde71846795e69794f0c1efbf8a100ee6b00418 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 09:59:03 +0000 https://status.as205126.net/#5c27aab4315ceed3594a82ecbbde71846795e69794f0c1efbf8a100ee6b00418 Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 05:58:45 +0000 https://status.as205126.net/#7968b00d763710f0d1e9df4fcc0d278eca9f84ce91f88c5d0bec75a1ebad11a9 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 05:50:12 +0000 https://status.as205126.net/#7968b00d763710f0d1e9df4fcc0d278eca9f84ce91f88c5d0bec75a1ebad11a9 Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 01:25:33 +0000 https://status.as205126.net/#b22c2f5e13bc722c0a8323fbb49f59a5d25392e440ef4d0f212d8a48940dd671 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 01:17:04 +0000 https://status.as205126.net/#b22c2f5e13bc722c0a8323fbb49f59a5d25392e440ef4d0f212d8a48940dd671 Authentication service went down Authentication service recovered https://status.as205126.net/ Mon, 23 Mar 2026 01:10:44 +0000 https://status.as205126.net/#4ff2d61cac6c771b84cc59351257e485c5ce3eb20076a13f0da0634b2515a3f2 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 23 Mar 2026 00:53:12 +0000 https://status.as205126.net/#4ff2d61cac6c771b84cc59351257e485c5ce3eb20076a13f0da0634b2515a3f2 Authentication service went down Authentication service recovered https://status.as205126.net/ Sun, 22 Mar 2026 23:43:42 +0000 https://status.as205126.net/#4dbbf0743afe5c0a74d8e470c23e2a6c9765cc12db4f93b45234e458ee5fe81b Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 22 Mar 2026 23:35:10 +0000 https://status.as205126.net/#4dbbf0743afe5c0a74d8e470c23e2a6c9765cc12db4f93b45234e458ee5fe81b Authentication service went down Authentication service recovered https://status.as205126.net/ Sun, 22 Mar 2026 22:19:47 +0000 https://status.as205126.net/#df60054dfe8cec0dcf73996ec4fc853aca7aa32e718b55a5f6ef52779d1f62b5 Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 22 Mar 2026 22:11:13 +0000 https://status.as205126.net/#df60054dfe8cec0dcf73996ec4fc853aca7aa32e718b55a5f6ef52779d1f62b5 Authentication service went down Authentication service recovered https://status.as205126.net/ Sun, 22 Mar 2026 21:52:42 +0000 https://status.as205126.net/#64db981e099c62e7f5d3fb75667d8b36c8815f46a9ec49ea3c18aacc22927149 Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 22 Mar 2026 21:44:10 +0000 https://status.as205126.net/#64db981e099c62e7f5d3fb75667d8b36c8815f46a9ec49ea3c18aacc22927149 Authentication service went down Authentication service recovered https://status.as205126.net/ Sun, 22 Mar 2026 19:58:42 +0000 https://status.as205126.net/#084fc9b370cd760e39507e043b08e4ab68ce7811291d44db6686b8970c165ba1 Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 22 Mar 2026 19:53:06 +0000 https://status.as205126.net/#084fc9b370cd760e39507e043b08e4ab68ce7811291d44db6686b8970c165ba1 Authentication service went down Authentication service recovered https://status.as205126.net/ Sun, 22 Mar 2026 19:13:40 +0000 https://status.as205126.net/#6614c5a4055e3ba0594a35b6b2b9b8c251143d29baf9ec9410c77f0382256ff0 Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 22 Mar 2026 19:08:04 +0000 https://status.as205126.net/#6614c5a4055e3ba0594a35b6b2b9b8c251143d29baf9ec9410c77f0382256ff0 Authentication service went down VPN service recovered https://status.as205126.net/ Sun, 22 Mar 2026 16:20:26 +0000 https://status.as205126.net/#2cebff087ebec2d06591e768933ed42f5de5c9699500320f18ce5d7318472526 VPN service recovered VPN service went down https://status.as205126.net/ Sun, 22 Mar 2026 16:14:36 +0000 https://status.as205126.net/#2cebff087ebec2d06591e768933ed42f5de5c9699500320f18ce5d7318472526 VPN service went down Authentication service recovered https://status.as205126.net/ Sat, 21 Mar 2026 19:10:43 +0000 https://status.as205126.net/#e0868912de071a1e38d51b6e45a66dfbdc01527b20daa48675d7131f0d29bdd2 Authentication service recovered Docker&Helm registry recovered https://status.as205126.net/ Sat, 21 Mar 2026 19:08:53 +0000 https://status.as205126.net/#62be02120f47223d40a7d9d039241718abb1d3c5af1d2ee68de64afc7169b56c Docker&Helm registry recovered Git server recovered https://status.as205126.net/ Sat, 21 Mar 2026 19:08:44 +0000 https://status.as205126.net/#c9dd6bbdab6b5e2e94f18126ea477e96bcc8cbf75f5c01c6e07fc94efef34afa Git server recovered Authentication service went down https://status.as205126.net/ Sat, 21 Mar 2026 18:53:43 +0000 https://status.as205126.net/#e0868912de071a1e38d51b6e45a66dfbdc01527b20daa48675d7131f0d29bdd2 Authentication service went down Docker&Helm registry went down https://status.as205126.net/ Sat, 21 Mar 2026 18:52:54 +0000 https://status.as205126.net/#62be02120f47223d40a7d9d039241718abb1d3c5af1d2ee68de64afc7169b56c Docker&Helm registry went down Git server went down https://status.as205126.net/ Sat, 21 Mar 2026 18:52:29 +0000 https://status.as205126.net/#c9dd6bbdab6b5e2e94f18126ea477e96bcc8cbf75f5c01c6e07fc94efef34afa Git server went down The load balancer provider is currently down 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. Authentication service recovered https://status.as205126.net/ Sat, 21 Mar 2026 11:01:36 +0000 https://status.as205126.net/#4e4ab3bf0becc58502f0105955c7f5a77726e916b2f2be76f0cb83266c6552e2 Authentication service recovered Load balancer recovered https://status.as205126.net/ Sat, 21 Mar 2026 10:49:13 +0000 https://status.as205126.net/#dcfe8e482a80f699a0571b49fad44c38aa74278d56f9422b5181fc2eb399899b Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 21 Mar 2026 10:46:40 +0000 https://status.as205126.net/#dcfe8e482a80f699a0571b49fad44c38aa74278d56f9422b5181fc2eb399899b Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 21 Mar 2026 10:37:07 +0000 https://status.as205126.net/#e8bd8de04083ac3436700f5620cc59c9a44690beccbcffdb99cc33de221d0913 Load balancer recovered The load balancer provider is currently down 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. Load balancer went down https://status.as205126.net/ Sat, 21 Mar 2026 10:13:40 +0000 https://status.as205126.net/#e8bd8de04083ac3436700f5620cc59c9a44690beccbcffdb99cc33de221d0913 Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 21 Mar 2026 09:58:05 +0000 https://status.as205126.net/#a1e80f5f66a7564290bd390de60fe7458eb09cadbe4cb344e31e44b99a48a4bc Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 21 Mar 2026 09:52:37 +0000 https://status.as205126.net/#a1e80f5f66a7564290bd390de60fe7458eb09cadbe4cb344e31e44b99a48a4bc Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 21 Mar 2026 09:16:13 +0000 https://status.as205126.net/#27bf8ae893d24de9aafef962d18b1c14d6c232e7103a308d39884b22873c9d94 Load balancer recovered Load balancer went down https://status.as205126.net/ Sat, 21 Mar 2026 09:10:42 +0000 https://status.as205126.net/#27bf8ae893d24de9aafef962d18b1c14d6c232e7103a308d39884b22873c9d94 Load balancer went down Load balancer recovered https://status.as205126.net/ Sat, 21 Mar 2026 08:22:13 +0000 https://status.as205126.net/#328fb94697c2210224681562dd744ff6d837e8c85216343adb91c4ded0140d70 Load balancer recovered VPN service recovered https://status.as205126.net/ Sat, 21 Mar 2026 08:17:28 +0000 https://status.as205126.net/#1d76fca6fecabb320c7576eded9e77807fbd4a9216a57d450904761adb7f518c VPN service recovered Docker&Helm registry recovered https://status.as205126.net/ Sat, 21 Mar 2026 07:54:32 +0000 https://status.as205126.net/#1ec30537eeeb3460b643e0ceda82217f036f714c37fe36d414e63207481e501d Docker&Helm registry recovered Git server recovered https://status.as205126.net/ Sat, 21 Mar 2026 07:54:27 +0000 https://status.as205126.net/#34f63bec95690b7e99c517b0893442fe7c5fae25e3fc40c8f75fdf29b8752121 Git server recovered The load balancer provider is currently 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. Load balancer went down https://status.as205126.net/ Sat, 21 Mar 2026 07:14:13 +0000 https://status.as205126.net/#328fb94697c2210224681562dd744ff6d837e8c85216343adb91c4ded0140d70 Load balancer went down Docker&Helm registry went down https://status.as205126.net/ Sat, 21 Mar 2026 07:13:55 +0000 https://status.as205126.net/#1ec30537eeeb3460b643e0ceda82217f036f714c37fe36d414e63207481e501d Docker&Helm registry went down Git server went down https://status.as205126.net/ Sat, 21 Mar 2026 07:13:27 +0000 https://status.as205126.net/#34f63bec95690b7e99c517b0893442fe7c5fae25e3fc40c8f75fdf29b8752121 Git server went down VPN service went down https://status.as205126.net/ Sat, 21 Mar 2026 07:12:26 +0000 https://status.as205126.net/#1d76fca6fecabb320c7576eded9e77807fbd4a9216a57d450904761adb7f518c VPN service went down Authentication service went down https://status.as205126.net/ Sat, 21 Mar 2026 07:11:34 +0000 https://status.as205126.net/#4e4ab3bf0becc58502f0105955c7f5a77726e916b2f2be76f0cb83266c6552e2 Authentication service went down Authentication service recovered https://status.as205126.net/ Thu, 19 Mar 2026 17:04:41 +0000 https://status.as205126.net/#f1df6f1d53a0be90c5367c07271fdee4b832d6b27c194c43182872ad75a3ac08 Authentication service recovered Authentication service went down https://status.as205126.net/ Thu, 19 Mar 2026 16:58:41 +0000 https://status.as205126.net/#f1df6f1d53a0be90c5367c07271fdee4b832d6b27c194c43182872ad75a3ac08 Authentication service went down Update the authentication system 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 VPN service recovered https://status.as205126.net/ Mon, 16 Mar 2026 20:02:32 +0000 https://status.as205126.net/#d6264d6b1122f6b1b5b11baedaed042ac45a6b8161b4747ce75d6a1b8ca7d99e VPN service recovered VPN service went down https://status.as205126.net/ Mon, 16 Mar 2026 19:50:34 +0000 https://status.as205126.net/#d6264d6b1122f6b1b5b11baedaed042ac45a6b8161b4747ce75d6a1b8ca7d99e VPN service went down Kubernetes CSI maintenance 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 as205126.net recovered https://status.as205126.net/ Sat, 14 Mar 2026 09:56:19 +0000 https://status.as205126.net/#db2a832ea91be0a8f0f1a89292bf7d702fae71320821c01664b7a4692905c836 as205126.net recovered as205126.net went down https://status.as205126.net/ Sat, 14 Mar 2026 09:54:18 +0000 https://status.as205126.net/#db2a832ea91be0a8f0f1a89292bf7d702fae71320821c01664b7a4692905c836 as205126.net went down AS205126 - par recovered https://status.as205126.net/ Sun, 08 Mar 2026 22:27:33 +0000 https://status.as205126.net/#3ed74d9a2972967a27aae273c0b7528de7f3b46d77c0d47e55a6f5c5aca40b7e AS205126 - par recovered AS205126 - par went down https://status.as205126.net/ Sun, 08 Mar 2026 22:24:50 +0000 https://status.as205126.net/#3ed74d9a2972967a27aae273c0b7528de7f3b46d77c0d47e55a6f5c5aca40b7e AS205126 - par went down as205126.net recovered https://status.as205126.net/ Sun, 08 Mar 2026 22:17:18 +0000 https://status.as205126.net/#a11b95dcf7a1ebd48dfa3113cf9891d01d0c43f2d92987c4ecd33e73754a38c6 as205126.net recovered AS205126 - par recovered https://status.as205126.net/ Sun, 08 Mar 2026 22:15:28 +0000 https://status.as205126.net/#1d4af3cc4cba0050ebfbe1d1efa687a6d4b5e0a8ede88ebbff1fb33bdc7d1ac7 AS205126 - par recovered AS205126 - cha recovered https://status.as205126.net/ Sun, 08 Mar 2026 22:14:55 +0000 https://status.as205126.net/#7404195d4cce95dfc730eff691af6ce06a706dbbdb2550365e504eaf062f6316 AS205126 - cha recovered Edge 1 Paris recovered https://status.as205126.net/ Sun, 08 Mar 2026 22:14:37 +0000 https://status.as205126.net/#baf57a19f9e86afe67c4bf7471ed7c9feed75be2d793feae764b154d347e37ad Edge 1 Paris recovered AS205126 - par went down https://status.as205126.net/ Sun, 08 Mar 2026 22:12:50 +0000 https://status.as205126.net/#1d4af3cc4cba0050ebfbe1d1efa687a6d4b5e0a8ede88ebbff1fb33bdc7d1ac7 AS205126 - par went down as205126.net went down https://status.as205126.net/ Sun, 08 Mar 2026 22:12:15 +0000 https://status.as205126.net/#a11b95dcf7a1ebd48dfa3113cf9891d01d0c43f2d92987c4ecd33e73754a38c6 as205126.net went down AS205126 - cha went down https://status.as205126.net/ Sun, 08 Mar 2026 22:12:10 +0000 https://status.as205126.net/#7404195d4cce95dfc730eff691af6ce06a706dbbdb2550365e504eaf062f6316 AS205126 - cha went down Edge 1 Paris went down https://status.as205126.net/ Sun, 08 Mar 2026 22:12:01 +0000 https://status.as205126.net/#baf57a19f9e86afe67c4bf7471ed7c9feed75be2d793feae764b154d347e37ad Edge 1 Paris went down AS205126 - par recovered https://status.as205126.net/ Sun, 08 Mar 2026 17:45:28 +0000 https://status.as205126.net/#b0ad430e9c87717fec9162ece8e8198e6343f6aca6e7829014af519366596e6e AS205126 - par recovered AS205126 - par went down https://status.as205126.net/ Sun, 08 Mar 2026 17:42:49 +0000 https://status.as205126.net/#b0ad430e9c87717fec9162ece8e8198e6343f6aca6e7829014af519366596e6e AS205126 - par went down AS205126 - par recovered https://status.as205126.net/ Sat, 07 Mar 2026 14:33:06 +0000 https://status.as205126.net/#f4876c578e3bf12062067592c415e91191a8b47a3ceeb2fb0c25f919fc30fa3f AS205126 - par recovered Connection lost between Paris and edge router 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. Connection lost between Paris and edge router 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. AS205126 - par went down https://status.as205126.net/ Sat, 07 Mar 2026 12:48:51 +0000 https://status.as205126.net/#f4876c578e3bf12062067592c415e91191a8b47a3ceeb2fb0c25f919fc30fa3f AS205126 - par went down Connection lost between Paris and edge router 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. AS205126 - cha recovered https://status.as205126.net/ Fri, 06 Mar 2026 07:56:47 +0000 https://status.as205126.net/#4b364b85a956a9da0684addaf2e0cde2e8cea5894f2f0f905968085504d06871 AS205126 - cha recovered AS205126 - cha went down https://status.as205126.net/ Fri, 06 Mar 2026 07:54:10 +0000 https://status.as205126.net/#4b364b85a956a9da0684addaf2e0cde2e8cea5894f2f0f905968085504d06871 AS205126 - cha went down VPN service recovered https://status.as205126.net/ Tue, 03 Mar 2026 03:05:28 +0000 https://status.as205126.net/#7a2a687ca35ef67c98e61b547f29fcafee17ec086718495200b8ac33c0dd83a3 VPN service recovered Git server recovered https://status.as205126.net/ Tue, 03 Mar 2026 03:02:31 +0000 https://status.as205126.net/#b408f825e6d99e86f24d4ce4605a7a7d37fd7486c0de4adb5736bf0f0d584867 Git server recovered Authentication service recovered https://status.as205126.net/ Tue, 03 Mar 2026 03:01:39 +0000 https://status.as205126.net/#65e10b4c8c25ee1f514920fdae0f7a80eb4622d09c70e32b9219662621326ff4 Authentication service recovered AS205126 - par recovered https://status.as205126.net/ Tue, 03 Mar 2026 02:54:29 +0000 https://status.as205126.net/#d9222bcfcd20d9312984bfd857a6c9ac447ec63c4f1bdeaccbc992fd6ca92361 AS205126 - par recovered Load balancer recovered https://status.as205126.net/ Tue, 03 Mar 2026 02:52:26 +0000 https://status.as205126.net/#f6027718245ccdb053174ab7546700421f9cf79552c1cb0817798a04e27b4519 Load balancer recovered Load balancer went down https://status.as205126.net/ Tue, 03 Mar 2026 02:49:37 +0000 https://status.as205126.net/#f6027718245ccdb053174ab7546700421f9cf79552c1cb0817798a04e27b4519 Load balancer went down Git server went down https://status.as205126.net/ Tue, 03 Mar 2026 02:49:28 +0000 https://status.as205126.net/#b408f825e6d99e86f24d4ce4605a7a7d37fd7486c0de4adb5736bf0f0d584867 Git server went down VPN service went down https://status.as205126.net/ Tue, 03 Mar 2026 02:48:28 +0000 https://status.as205126.net/#7a2a687ca35ef67c98e61b547f29fcafee17ec086718495200b8ac33c0dd83a3 VPN service went down Authentication service went down https://status.as205126.net/ Tue, 03 Mar 2026 02:47:07 +0000 https://status.as205126.net/#65e10b4c8c25ee1f514920fdae0f7a80eb4622d09c70e32b9219662621326ff4 Authentication service went down AS205126 - par went down https://status.as205126.net/ Tue, 03 Mar 2026 02:45:50 +0000 https://status.as205126.net/#d9222bcfcd20d9312984bfd857a6c9ac447ec63c4f1bdeaccbc992fd6ca92361 AS205126 - par went down AS205126 - par recovered https://status.as205126.net/ Tue, 03 Mar 2026 00:30:27 +0000 https://status.as205126.net/#8053b9999f288d25cb725ec59afb6c140e4dae9e7ebc8713e9837bdeb82b2d73 AS205126 - par recovered AS205126 - par went down https://status.as205126.net/ Tue, 03 Mar 2026 00:27:51 +0000 https://status.as205126.net/#8053b9999f288d25cb725ec59afb6c140e4dae9e7ebc8713e9837bdeb82b2d73 AS205126 - par went down Git server recovered https://status.as205126.net/ Mon, 23 Feb 2026 18:50:29 +0000 https://status.as205126.net/#1b7302daaf661cde9a5fb5c7708e80244427986ce25c7ba023d03f762d6f9157 Git server recovered Git server went down https://status.as205126.net/ Mon, 23 Feb 2026 18:44:31 +0000 https://status.as205126.net/#1b7302daaf661cde9a5fb5c7708e80244427986ce25c7ba023d03f762d6f9157 Git server went down Authentication service recovered https://status.as205126.net/ Sun, 22 Feb 2026 12:40:39 +0000 https://status.as205126.net/#d4dafc43c09ec07f9a163f071c07e85f239aeb84b2a97db2d70856b6706eec96 Authentication service recovered Authentication service went down https://status.as205126.net/ Sun, 22 Feb 2026 12:34:37 +0000 https://status.as205126.net/#d4dafc43c09ec07f9a163f071c07e85f239aeb84b2a97db2d70856b6706eec96 Authentication service went down Updating authentication system 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. Changing Docker registry backend storage for experiment 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. VPN service recovered https://status.as205126.net/ Sat, 21 Feb 2026 14:47:28 +0000 https://status.as205126.net/#59f83752dd4e55aae30602b7e8c9ac33f4f8bc4cf8935f724c7ccba58b4f4e64 VPN service recovered Git server recovered https://status.as205126.net/ Sat, 21 Feb 2026 14:47:28 +0000 https://status.as205126.net/#41be15c489dd20fc2aa7cf3ce4c0c2d38e3d8cb61dd2d260cb176e9965bf0027 Git server recovered Git server went down https://status.as205126.net/ Sat, 21 Feb 2026 14:41:28 +0000 https://status.as205126.net/#41be15c489dd20fc2aa7cf3ce4c0c2d38e3d8cb61dd2d260cb176e9965bf0027 Git server went down VPN service went down https://status.as205126.net/ Sat, 21 Feb 2026 14:41:28 +0000 https://status.as205126.net/#59f83752dd4e55aae30602b7e8c9ac33f4f8bc4cf8935f724c7ccba58b4f4e64 VPN service went down VPN service recovered https://status.as205126.net/ Sat, 21 Feb 2026 13:23:29 +0000 https://status.as205126.net/#0e21e201147dbe897f6160eb9f4f55abed6b3d719c79b9d3411ac2415aae7985 VPN service recovered Git server recovered https://status.as205126.net/ Sat, 21 Feb 2026 13:23:29 +0000 https://status.as205126.net/#989b91034c41cbce41c9390d4d14259edf9c13c9ad0479406e7f020ccd7229cb Git server recovered VPN service went down https://status.as205126.net/ Sat, 21 Feb 2026 13:17:28 +0000 https://status.as205126.net/#0e21e201147dbe897f6160eb9f4f55abed6b3d719c79b9d3411ac2415aae7985 VPN service went down Git server went down https://status.as205126.net/ Sat, 21 Feb 2026 13:17:28 +0000 https://status.as205126.net/#989b91034c41cbce41c9390d4d14259edf9c13c9ad0479406e7f020ccd7229cb Git server went down Git server recovered https://status.as205126.net/ Sat, 21 Feb 2026 13:11:28 +0000 https://status.as205126.net/#f2868ab094daaa76e0f3d20ad90df14b5d3c3656dc1ceb779d3bdd49945d2c1b Git server recovered VPN service recovered https://status.as205126.net/ Sat, 21 Feb 2026 13:11:28 +0000 https://status.as205126.net/#dfe9cf93b764ca70c2c3de8fc18570903e46e462bc3bda74cf43705fc002a63d VPN service recovered VPN service went down https://status.as205126.net/ Sat, 21 Feb 2026 13:05:29 +0000 https://status.as205126.net/#dfe9cf93b764ca70c2c3de8fc18570903e46e462bc3bda74cf43705fc002a63d VPN service went down Git server went down https://status.as205126.net/ Sat, 21 Feb 2026 13:05:29 +0000 https://status.as205126.net/#f2868ab094daaa76e0f3d20ad90df14b5d3c3656dc1ceb779d3bdd49945d2c1b Git server went down VPN service recovered https://status.as205126.net/ Sat, 21 Feb 2026 12:53:29 +0000 https://status.as205126.net/#5fe031eb958774a7da4a6c423376552afaeb5be9719f2b8431e59dbf337a0a28 VPN service recovered Git server recovered https://status.as205126.net/ Sat, 21 Feb 2026 12:53:28 +0000 https://status.as205126.net/#8fa402ed8bf4a7c098b364dd0dc79286ee0f577b5f1d5e37742b98a58344a16f Git server recovered VPN service went down https://status.as205126.net/ Sat, 21 Feb 2026 12:47:28 +0000 https://status.as205126.net/#5fe031eb958774a7da4a6c423376552afaeb5be9719f2b8431e59dbf337a0a28 VPN service went down Git server went down https://status.as205126.net/ Sat, 21 Feb 2026 12:47:26 +0000 https://status.as205126.net/#8fa402ed8bf4a7c098b364dd0dc79286ee0f577b5f1d5e37742b98a58344a16f Git server went down Git server recovered https://status.as205126.net/ Sat, 21 Feb 2026 12:14:29 +0000 https://status.as205126.net/#8a8d13f2574a9016e199e47b6fd5f49720f110c30dd7cb5bccd30d558acf20dd Git server recovered VPN service recovered https://status.as205126.net/ Sat, 21 Feb 2026 12:14:29 +0000 https://status.as205126.net/#a60e050c21df7d2660a8f8a88f356b9b27374a2a2499e59a82cb39ada888a93f VPN service recovered VPN service went down https://status.as205126.net/ Sat, 21 Feb 2026 12:08:29 +0000 https://status.as205126.net/#a60e050c21df7d2660a8f8a88f356b9b27374a2a2499e59a82cb39ada888a93f VPN service went down Git server went down https://status.as205126.net/ Sat, 21 Feb 2026 12:08:29 +0000 https://status.as205126.net/#8a8d13f2574a9016e199e47b6fd5f49720f110c30dd7cb5bccd30d558acf20dd Git server went down Git server recovered https://status.as205126.net/ Sat, 21 Feb 2026 11:05:29 +0000 https://status.as205126.net/#119f99a99a811fb25e0d2996c1781b76edd0b0659c58fc4fe6db0fc75fc60d76 Git server recovered VPN service recovered https://status.as205126.net/ Sat, 21 Feb 2026 11:05:29 +0000 https://status.as205126.net/#d33d25c545121f23c5224a2f11f0afcae905d8ce57eda6a38c024fa04d5450cd VPN service recovered VPN service went down https://status.as205126.net/ Sat, 21 Feb 2026 10:59:29 +0000 https://status.as205126.net/#d33d25c545121f23c5224a2f11f0afcae905d8ce57eda6a38c024fa04d5450cd VPN service went down Git server went down https://status.as205126.net/ Sat, 21 Feb 2026 10:59:28 +0000 https://status.as205126.net/#119f99a99a811fb25e0d2996c1781b76edd0b0659c58fc4fe6db0fc75fc60d76 Git server went down Updating Kubernetes cluster version 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 Git server recovered https://status.as205126.net/ Thu, 19 Feb 2026 22:53:28 +0000 https://status.as205126.net/#41a96459728470186678273971b876c693054584f4d6d5f5a333e98b70cf0891 Git server recovered Git server went down https://status.as205126.net/ Thu, 19 Feb 2026 22:47:29 +0000 https://status.as205126.net/#41a96459728470186678273971b876c693054584f4d6d5f5a333e98b70cf0891 Git server went down Enable IPv6 on kubernetes nodes 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. Enable IPv6 on par-1 kubernetes node 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 Authentication service recovered https://status.as205126.net/ Wed, 18 Feb 2026 17:19:40 +0000 https://status.as205126.net/#2ce00702674d017f5e75201e0afd62d308353d76bcde2539715d1e28e74a8aaf Authentication service recovered Authentication service went down https://status.as205126.net/ Wed, 18 Feb 2026 17:14:24 +0000 https://status.as205126.net/#2ce00702674d017f5e75201e0afd62d308353d76bcde2539715d1e28e74a8aaf Authentication service went down Kubernetes node oci-1 restarted 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. Kubernetes node oci-1 restarted 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. Authentication service recovered https://status.as205126.net/ Sun, 15 Feb 2026 01:31:34 +0000 https://status.as205126.net/#18897990bc6f54e1a252116f0d5fee80fc1f90180df575bb50aa1c417c0b3ad6 Authentication service recovered Authentication service went down https://status.as205126.net/ Sat, 14 Feb 2026 23:08:34 +0000 https://status.as205126.net/#18897990bc6f54e1a252116f0d5fee80fc1f90180df575bb50aa1c417c0b3ad6 Authentication service went down VPN service recovered https://status.as205126.net/ Sat, 14 Feb 2026 20:26:28 +0000 https://status.as205126.net/#c6c4e1b61ebef545ae38c891437ce4543fd3c3c8352c7aba3e69eeefd832e73d VPN service recovered VPN service went down https://status.as205126.net/ Sat, 14 Feb 2026 20:17:55 +0000 https://status.as205126.net/#c6c4e1b61ebef545ae38c891437ce4543fd3c3c8352c7aba3e69eeefd832e73d VPN service went down Authentication service recovered https://status.as205126.net/ Fri, 13 Feb 2026 23:01:36 +0000 https://status.as205126.net/#8644336f75b7f161e862d5d60b6c9271e54e73f730e15d579892b88ecbcc6c3e Authentication service recovered Authentication service went down https://status.as205126.net/ Fri, 13 Feb 2026 22:55:37 +0000 https://status.as205126.net/#8644336f75b7f161e862d5d60b6c9271e54e73f730e15d579892b88ecbcc6c3e Authentication service went down Authentication service recovered https://status.as205126.net/ Fri, 13 Feb 2026 22:52:36 +0000 https://status.as205126.net/#4bb79d6abc9f29e6b0af066725821c518057dcda9ca378308a986f5a9ac7e1ff Authentication service recovered Authentication service went down https://status.as205126.net/ Fri, 13 Feb 2026 22:40:32 +0000 https://status.as205126.net/#4bb79d6abc9f29e6b0af066725821c518057dcda9ca378308a986f5a9ac7e1ff Authentication service went down Updating authentication system 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. A node lost connectivity 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. A node lost connectivity 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. Authentication service recovered https://status.as205126.net/ Fri, 13 Feb 2026 21:25:36 +0000 https://status.as205126.net/#68b213812fbc91e6ba934c924b2b5cdbed78228fdb8e5ca9ebfd023c405a739c Authentication service recovered Docker&Helm registry recovered https://status.as205126.net/ Fri, 13 Feb 2026 21:14:44 +0000 https://status.as205126.net/#4c48466d7c2fc4c2ed2c35380e4e78fd2c995345d93946139db36c6f429b42ca Docker&Helm registry recovered A node lost connectivity 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. Docker&Helm registry went down https://status.as205126.net/ Fri, 13 Feb 2026 21:08:47 +0000 https://status.as205126.net/#4c48466d7c2fc4c2ed2c35380e4e78fd2c995345d93946139db36c6f429b42ca Docker&Helm registry went down Authentication service went down https://status.as205126.net/ Fri, 13 Feb 2026 21:07:38 +0000 https://status.as205126.net/#68b213812fbc91e6ba934c924b2b5cdbed78228fdb8e5ca9ebfd023c405a739c Authentication service went down Load balancer recovered https://status.as205126.net/ Fri, 13 Feb 2026 18:10:07 +0000 https://status.as205126.net/#830e7f59ea6b1c8da1a99b6f4dfe5f4971f2d3ff807c06340d1a01952f3780a7 Load balancer recovered Load balancer went down https://status.as205126.net/ Fri, 13 Feb 2026 18:07:06 +0000 https://status.as205126.net/#830e7f59ea6b1c8da1a99b6f4dfe5f4971f2d3ff807c06340d1a01952f3780a7 Load balancer went down VPN service recovered https://status.as205126.net/ Thu, 12 Feb 2026 10:08:25 +0000 https://status.as205126.net/#c31b6359ccf1e65cc45a701bbc09166f1d5a980f8b2d5474f8e1217df064604e VPN service recovered VPN service went down https://status.as205126.net/ Thu, 12 Feb 2026 10:02:25 +0000 https://status.as205126.net/#c31b6359ccf1e65cc45a701bbc09166f1d5a980f8b2d5474f8e1217df064604e VPN service went down VPN service update 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 VPN service recovered https://status.as205126.net/ Fri, 06 Feb 2026 14:10:52 +0000 https://status.as205126.net/#7ee2722fbe48df2023c380cb42e8d5324256a19f320929d572553d270b53ab85 VPN service recovered VPN service went down https://status.as205126.net/ Fri, 06 Feb 2026 11:23:33 +0000 https://status.as205126.net/#7ee2722fbe48df2023c380cb42e8d5324256a19f320929d572553d270b53ab85 VPN service went down VPN service update 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. Docker&Helm registry recovered https://status.as205126.net/ Fri, 06 Feb 2026 11:15:43 +0000 https://status.as205126.net/#4b574c3daf7a65acd58665442c810b4e9140d06e649688b7c5151fb49db3214d Docker&Helm registry recovered Docker&Helm registry went down https://status.as205126.net/ Fri, 06 Feb 2026 11:07:52 +0000 https://status.as205126.net/#4b574c3daf7a65acd58665442c810b4e9140d06e649688b7c5151fb49db3214d Docker&Helm registry went down Git server recovered https://status.as205126.net/ Fri, 06 Feb 2026 10:14:28 +0000 https://status.as205126.net/#b7d25fe9ace4a24a42f91f46fcef2e6e8e921afa258c8d747a0814372ee21c75 Git server recovered Authentication service recovered https://status.as205126.net/ Fri, 06 Feb 2026 10:13:44 +0000 https://status.as205126.net/#0e3717cfa83d766486d33257fb9a13292e881f36103fc3488015789a5330e34f Authentication service recovered Git server went down https://status.as205126.net/ Fri, 06 Feb 2026 10:07:31 +0000 https://status.as205126.net/#b7d25fe9ace4a24a42f91f46fcef2e6e8e921afa258c8d747a0814372ee21c75 Git server went down Authentication service went down https://status.as205126.net/ Fri, 06 Feb 2026 10:05:41 +0000 https://status.as205126.net/#0e3717cfa83d766486d33257fb9a13292e881f36103fc3488015789a5330e34f Authentication service went down VPN service recovered https://status.as205126.net/ Fri, 06 Feb 2026 00:05:32 +0000 https://status.as205126.net/#33720dae326a86b70496912daec5dd11d7f2e4881d437a685585da1ba340bb35 VPN service recovered VPN service went down https://status.as205126.net/ Fri, 06 Feb 2026 00:00:02 +0000 https://status.as205126.net/#33720dae326a86b70496912daec5dd11d7f2e4881d437a685585da1ba340bb35 VPN service went down VPN service recovered https://status.as205126.net/ Thu, 05 Feb 2026 03:56:29 +0000 https://status.as205126.net/#d618c1b06979525147d9c745b1a832a2599920bd46d9ce015a365841fa87deaf VPN service recovered VPN service went down https://status.as205126.net/ Thu, 05 Feb 2026 03:50:33 +0000 https://status.as205126.net/#d618c1b06979525147d9c745b1a832a2599920bd46d9ce015a365841fa87deaf VPN service went down Applying update with restart on AS website https://status.as205126.net/incident/817672 Tue, 03 Feb 2026 15:12:29 -0000 https://status.as205126.net/incident/817672#57f5229a38e67c9942d043405c1adf374bd6e27f7d2ad10b2768571c80c4a2f1 Maintenance completed Applying update with restart on AS website 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. VPN service recovered https://status.as205126.net/ Mon, 02 Feb 2026 19:32:35 +0000 https://status.as205126.net/#e32767766ca4b6b828f308b8dd954849487bf3c1724d2dd2b5bb754348085c93 VPN service recovered VPN service went down https://status.as205126.net/ Mon, 02 Feb 2026 19:26:31 +0000 https://status.as205126.net/#e32767766ca4b6b828f308b8dd954849487bf3c1724d2dd2b5bb754348085c93 VPN service went down VPN service recovered https://status.as205126.net/ Sun, 01 Feb 2026 23:20:29 +0000 https://status.as205126.net/#77d98be11aaa901fb4e1e7723f765675a9024e2ba17c0656c8e506b821d62fec VPN service recovered VPN service went down https://status.as205126.net/ Sun, 01 Feb 2026 23:14:28 +0000 https://status.as205126.net/#77d98be11aaa901fb4e1e7723f765675a9024e2ba17c0656c8e506b821d62fec VPN service went down Git server recovered https://status.as205126.net/ Sat, 31 Jan 2026 19:08:49 +0000 https://status.as205126.net/#7b42ba9708dcd55332a67c7154adee02a4826d98a469f5b7209ab9f8dc975520 Git server recovered Git server went down https://status.as205126.net/ Sat, 31 Jan 2026 19:07:28 +0000 https://status.as205126.net/#7b42ba9708dcd55332a67c7154adee02a4826d98a469f5b7209ab9f8dc975520 Git server went down Important node reboot 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. VPN service recovered https://status.as205126.net/ Sat, 31 Jan 2026 09:50:30 +0000 https://status.as205126.net/#a2dc1b3595e8615cb830f8b57f9b5ed13dd80ac7c9a3e48ffb76aaeb0d06f398 VPN service recovered VPN service went down https://status.as205126.net/ Sat, 31 Jan 2026 09:41:29 +0000 https://status.as205126.net/#a2dc1b3595e8615cb830f8b57f9b5ed13dd80ac7c9a3e48ffb76aaeb0d06f398 VPN service went down Changing network policy on edge router 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. VPN service recovered https://status.as205126.net/ Fri, 30 Jan 2026 09:26:31 +0000 https://status.as205126.net/#65057fac75f0c3103a5469d8ab1f30f53667632a2182dda96796fe0b4e5bb630 VPN service recovered VPN service went down https://status.as205126.net/ Fri, 30 Jan 2026 09:18:05 +0000 https://status.as205126.net/#65057fac75f0c3103a5469d8ab1f30f53667632a2182dda96796fe0b4e5bb630 VPN service went down Authentication service recovered https://status.as205126.net/ Thu, 29 Jan 2026 20:25:39 +0000 https://status.as205126.net/#c1b5c2aac814ff2bc0ae8629dfa88a3dd65eba91d25cbc530cc8d931c1bdfb50 Authentication service recovered Authentication service went down https://status.as205126.net/ Thu, 29 Jan 2026 20:11:09 +0000 https://status.as205126.net/#c1b5c2aac814ff2bc0ae8629dfa88a3dd65eba91d25cbc530cc8d931c1bdfb50 Authentication service went down Network maintenance on OCI hosted node 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. Git server recovered https://status.as205126.net/ Wed, 28 Jan 2026 11:59:27 +0000 https://status.as205126.net/#12ec70f1b6369c31453384bd8d666cb572a70cbec41dbb75c57d6b2cdb1b7c41 Git server recovered Docker&Helm registry recovered https://status.as205126.net/ Wed, 28 Jan 2026 11:50:49 +0000 https://status.as205126.net/#454a6ee7e3ace68552f1b42d1e0108f18af5d1bfbc16eb132ce67c6fd6fbbe5b Docker&Helm registry recovered Docker&Helm registry went down https://status.as205126.net/ Wed, 28 Jan 2026 11:44:50 +0000 https://status.as205126.net/#454a6ee7e3ace68552f1b42d1e0108f18af5d1bfbc16eb132ce67c6fd6fbbe5b Docker&Helm registry went down Git server went down https://status.as205126.net/ Wed, 28 Jan 2026 11:44:48 +0000 https://status.as205126.net/#12ec70f1b6369c31453384bd8d666cb572a70cbec41dbb75c57d6b2cdb1b7c41 Git server went down Authentication service recovered https://status.as205126.net/ Mon, 26 Jan 2026 10:32:04 +0000 https://status.as205126.net/#391a9d3785b74fcea6e28e66a4cfba5f53e5e7359794eb43f0cbd4743ab2b530 Authentication service recovered Authentication service went down https://status.as205126.net/ Mon, 26 Jan 2026 10:11:09 +0000 https://status.as205126.net/#391a9d3785b74fcea6e28e66a4cfba5f53e5e7359794eb43f0cbd4743ab2b530 Authentication service went down Git server recovered https://status.as205126.net/ Sun, 25 Jan 2026 05:08:33 +0000 https://status.as205126.net/#5922870df16e138530285ee9567e58b045a71f91bd641886edcf902c7e3bc744 Git server recovered Docker&Helm registry recovered https://status.as205126.net/ Sun, 25 Jan 2026 05:06:37 +0000 https://status.as205126.net/#bd6d46724b96fc79c1ca43362eb219ca0b3cb909f3ccb5fe4153a489379cc77d Docker&Helm registry recovered Docker&Helm registry went down https://status.as205126.net/ Sun, 25 Jan 2026 05:04:52 +0000 https://status.as205126.net/#bd6d46724b96fc79c1ca43362eb219ca0b3cb909f3ccb5fe4153a489379cc77d Docker&Helm registry went down Git server went down https://status.as205126.net/ Sun, 25 Jan 2026 05:04:27 +0000 https://status.as205126.net/#5922870df16e138530285ee9567e58b045a71f91bd641886edcf902c7e3bc744 Git server went down VPN service recovered https://status.as205126.net/ Sat, 24 Jan 2026 17:59:30 +0000 https://status.as205126.net/#dbf93c1d74fb581460e8b81fa9f83cce9b41ff9106a1045b1887a5259527355b VPN service recovered VPN service went down https://status.as205126.net/ Sat, 24 Jan 2026 17:53:30 +0000 https://status.as205126.net/#dbf93c1d74fb581460e8b81fa9f83cce9b41ff9106a1045b1887a5259527355b VPN service went down Authentication service recovered https://status.as205126.net/ Sat, 24 Jan 2026 15:46:39 +0000 https://status.as205126.net/#d1718640d80b5eb2aff58f23824b6e95c14cab9bdb943ddc2c0141525749a2fa Authentication service recovered Git server recovered https://status.as205126.net/ Sat, 24 Jan 2026 15:39:09 +0000 https://status.as205126.net/#f634c261655cd287a0f8e0e7bb12733ee2917c1f7e84b7fa7c3822f5ee286bce Git server recovered Docker&Helm registry recovered https://status.as205126.net/ Sat, 24 Jan 2026 15:39:01 +0000 https://status.as205126.net/#e1e054b5828e283365e10b691cfd8cd793f2d71bfe814417ed75a576893752d3 Docker&Helm registry recovered Authentication service went down https://status.as205126.net/ Sat, 24 Jan 2026 15:36:00 +0000 https://status.as205126.net/#d1718640d80b5eb2aff58f23824b6e95c14cab9bdb943ddc2c0141525749a2fa Authentication service went down Docker&Helm registry went down https://status.as205126.net/ Sat, 24 Jan 2026 15:34:51 +0000 https://status.as205126.net/#e1e054b5828e283365e10b691cfd8cd793f2d71bfe814417ed75a576893752d3 Docker&Helm registry went down Git server went down https://status.as205126.net/ Sat, 24 Jan 2026 15:34:26 +0000 https://status.as205126.net/#f634c261655cd287a0f8e0e7bb12733ee2917c1f7e84b7fa7c3822f5ee286bce Git server went down Git server recovered https://status.as205126.net/ Sat, 24 Jan 2026 00:35:30 +0000 https://status.as205126.net/#e28a103ec670bfc913c10c696c975270241463e78a3a6c129c4202a4c419c349 Git server recovered Git server went down https://status.as205126.net/ Sat, 24 Jan 2026 00:32:29 +0000 https://status.as205126.net/#e28a103ec670bfc913c10c696c975270241463e78a3a6c129c4202a4c419c349 Git server went down Update Git server 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. Git server recovered https://status.as205126.net/ Fri, 23 Jan 2026 13:02:29 +0000 https://status.as205126.net/#e0184c5576bc459c5be0e406ff1fc2cd955ed9bdc3e40c47ca9e030bd5ce8a0e Git server recovered Authentication service recovered https://status.as205126.net/ Fri, 23 Jan 2026 12:58:42 +0000 https://status.as205126.net/#778d2718f1424cf1836d3d9e77d23d927c3dc24256ef92b83aa38dacc9d0ea0d Authentication service recovered Git server went down https://status.as205126.net/ Fri, 23 Jan 2026 12:48:31 +0000 https://status.as205126.net/#e0184c5576bc459c5be0e406ff1fc2cd955ed9bdc3e40c47ca9e030bd5ce8a0e Git server went down Authentication service went down https://status.as205126.net/ Fri, 23 Jan 2026 12:46:35 +0000 https://status.as205126.net/#778d2718f1424cf1836d3d9e77d23d927c3dc24256ef92b83aa38dacc9d0ea0d Authentication service went down Restart par-1 kubernetes node 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 Docker&Helm registry recovered https://status.as205126.net/ Fri, 23 Jan 2026 12:27:38 +0000 https://status.as205126.net/#914d08cfb94755030d84d83925b9da3a2e7c3987b68ee462afca019174d69cc4 Docker&Helm registry recovered Docker&Helm registry went down https://status.as205126.net/ Fri, 23 Jan 2026 12:25:50 +0000 https://status.as205126.net/#914d08cfb94755030d84d83925b9da3a2e7c3987b68ee462afca019174d69cc4 Docker&Helm registry went down Docker&Helm registry recovered https://status.as205126.net/ Fri, 23 Jan 2026 09:35:54 +0000 https://status.as205126.net/#66a62d0a0044332e5a4e54e801deafb1db3201d5e6a47c4db019940e6a76afe1 Docker&Helm registry recovered Docker&Helm registry went down https://status.as205126.net/ Fri, 23 Jan 2026 09:34:47 +0000 https://status.as205126.net/#66a62d0a0044332e5a4e54e801deafb1db3201d5e6a47c4db019940e6a76afe1 Docker&Helm registry went down Docker&Helm registry recovered https://status.as205126.net/ Fri, 23 Jan 2026 02:38:47 +0000 https://status.as205126.net/#72ed3a8871f36fa6c6e1d251e321cadcdcdd954c4ab2cccaa21a4422ef386040 Docker&Helm registry recovered Git server recovered https://status.as205126.net/ Fri, 23 Jan 2026 02:38:34 +0000 https://status.as205126.net/#3cae887ba823fc312ae0a7c8deea41990946db4069bed10bfe62449b6391e137 Git server recovered Docker&Helm registry went down https://status.as205126.net/ Fri, 23 Jan 2026 02:37:45 +0000 https://status.as205126.net/#72ed3a8871f36fa6c6e1d251e321cadcdcdd954c4ab2cccaa21a4422ef386040 Docker&Helm registry went down Git server went down https://status.as205126.net/ Fri, 23 Jan 2026 02:37:27 +0000 https://status.as205126.net/#3cae887ba823fc312ae0a7c8deea41990946db4069bed10bfe62449b6391e137 Git server went down Service unavailability 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. Service unavailability 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. Service unavailability 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. Service unavailability 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. Authentication system update 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. Automated git server update 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 Connectivity lost on Paris 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. Connectivity lost on Paris 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. Connectivity lost on Paris 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. Connectivity lost on Paris 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. Connectivity lost on Paris 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. Connectivity lost on Paris 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). Manchester router lost connectivity 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. Manchester router lost connectivity 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. Connectivity lost on Kubernetes node 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. Connectivity lost on Kubernetes node 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. Authentication system update 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. Git server instablity 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. Git server instablity 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. Git server instablity 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. Git server instablity 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. Force backup all the services 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. Updating authentication server 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 Authentication server down 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. Authentication server down 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. Electrical maintenance on Paris site 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. Load Balancer certificate renewal - auto 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 Authentication system update 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 Major outage on Paris site 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. Major outage on Paris site 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. Major outage on Paris site 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. Major outage on Paris site 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. Major outage on Paris site 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. Major outage on Paris site 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. Major outage on Paris site 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. Authentication system update 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 Updating Kubernetes endpoint 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. `cha` site lost internet connectivity 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. `cha` site lost internet connectivity 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. `cha` site lost internet connectivity 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.