Incidents | Hyrien Incidents reported on status page for Hyrien https://status.hyrien.com/ https://d1lppblt9t2x15.cloudfront.net/logos/d65e1837fca5662df9c59b60128ede39.png Incidents | Hyrien https://status.hyrien.com/ en API recovered https://status.hyrien.com/ Mon, 19 May 2025 13:42:58 +0000 https://status.hyrien.com/#58f35087f8c732ec4bf129118229a4017570c7e81ed0de628457d7dd5c5f7ca1 API recovered API service not available https://status.hyrien.com/incident/565832 Mon, 19 May 2025 13:40:00 -0000 https://status.hyrien.com/incident/565832#01e2b75b7644c86e690cde195d2f2751319cc9c547a4917c08af7c735d0c93d2 The API was fully available again shortly after the reported outage. We have been monitoring this closely over the last few days and have not detected any new outages. Mail Service recovered https://status.hyrien.com/ Sun, 18 May 2025 07:03:29 +0000 https://status.hyrien.com/#7c900529d1848ef6859acde98f4e2187bad06bc3f7ddc95059c5760547200f9d Mail Service recovered System III – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 18 May 2025 07:03:29 +0000 https://status.hyrien.com/#7c900529d1848ef6859acde98f4e2187bad06bc3f7ddc95059c5760547200f9d System III – Eygelshoven, Netherlands recovered Mail Service went down https://status.hyrien.com/ Sun, 18 May 2025 00:15:45 +0000 https://status.hyrien.com/#7c900529d1848ef6859acde98f4e2187bad06bc3f7ddc95059c5760547200f9d Mail Service went down System III – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 18 May 2025 00:15:45 +0000 https://status.hyrien.com/#7c900529d1848ef6859acde98f4e2187bad06bc3f7ddc95059c5760547200f9d System III – Eygelshoven, Netherlands went down Backend I recovered https://status.hyrien.com/ Thu, 15 May 2025 14:27:17 +0000 https://status.hyrien.com/#acacce744e28577c1d465766f1d72f6cbba2ddf9e1c044072b88ad1003741dfa Backend I recovered Backend I went down https://status.hyrien.com/ Thu, 15 May 2025 14:21:15 +0000 https://status.hyrien.com/#acacce744e28577c1d465766f1d72f6cbba2ddf9e1c044072b88ad1003741dfa Backend I went down API service not available https://status.hyrien.com/incident/565832 Thu, 15 May 2025 12:00:00 -0000 https://status.hyrien.com/incident/565832#4b0b25d492fc166319907c16415a5266a20c356c2f21495bc158ec8ea3c7bec1 The API is available again. We are now monitoring the API services in detail. API service not available https://status.hyrien.com/incident/565832 Thu, 15 May 2025 09:40:00 -0000 https://status.hyrien.com/incident/565832#9378208024ccb8328fd8f3033a7a2cbc0f8ffb1b123ca6d09d781c915cebab7f We are currently experiencing an outage of our API service. We are currently looking for the cause. API went down https://status.hyrien.com/ Thu, 15 May 2025 09:36:54 +0000 https://status.hyrien.com/#58f35087f8c732ec4bf129118229a4017570c7e81ed0de628457d7dd5c5f7ca1 API went down API recovered https://status.hyrien.com/ Thu, 15 May 2025 09:30:54 +0000 https://status.hyrien.com/#9ee52aeec317857d5c9d7cc3fce4e3fba608c987c2989ca8c24363dae793f05c API recovered API went down https://status.hyrien.com/ Thu, 15 May 2025 07:15:38 +0000 https://status.hyrien.com/#9ee52aeec317857d5c9d7cc3fce4e3fba608c987c2989ca8c24363dae793f05c API went down API recovered https://status.hyrien.com/ Thu, 15 May 2025 07:00:39 +0000 https://status.hyrien.com/#04716af200859fda3fd70ee8730a94018972984f32d3b83caa7aca63afdeab58 API recovered API went down https://status.hyrien.com/ Thu, 15 May 2025 06:54:37 +0000 https://status.hyrien.com/#04716af200859fda3fd70ee8730a94018972984f32d3b83caa7aca63afdeab58 API went down Backend I recovered https://status.hyrien.com/ Wed, 07 May 2025 06:40:32 +0000 https://status.hyrien.com/#807a94de0550502b4a126591896938ab15d3fade53250712f1c95efa159e7c73 Backend I recovered Backend I went down https://status.hyrien.com/ Wed, 07 May 2025 05:26:02 +0000 https://status.hyrien.com/#807a94de0550502b4a126591896938ab15d3fade53250712f1c95efa159e7c73 Backend I went down Backend I recovered https://status.hyrien.com/ Wed, 07 May 2025 00:37:36 +0000 https://status.hyrien.com/#a1a0a8dddcdcdd26d6df9cc852194c517d6e8f5a12dfc160c7fc72ef6c019245 Backend I recovered Backend I went down https://status.hyrien.com/ Wed, 07 May 2025 00:32:41 +0000 https://status.hyrien.com/#a1a0a8dddcdcdd26d6df9cc852194c517d6e8f5a12dfc160c7fc72ef6c019245 Backend I went down API recovered https://status.hyrien.com/ Tue, 06 May 2025 17:02:13 +0000 https://status.hyrien.com/#12d3bab810d972a31158a2c2fba58c549434dc864f77e2a7bb80c02e8ebde2d7 API recovered API went down https://status.hyrien.com/ Tue, 06 May 2025 16:44:17 +0000 https://status.hyrien.com/#12d3bab810d972a31158a2c2fba58c549434dc864f77e2a7bb80c02e8ebde2d7 API went down Backend I recovered https://status.hyrien.com/ Sat, 03 May 2025 19:27:53 +0000 https://status.hyrien.com/#0bf81c7ed036850d4534064af5412718e5c46a3ee58587b4511222d1117b6a68 Backend I recovered Backend I went down https://status.hyrien.com/ Sat, 03 May 2025 19:22:59 +0000 https://status.hyrien.com/#0bf81c7ed036850d4534064af5412718e5c46a3ee58587b4511222d1117b6a68 Backend I went down Mail Service recovered https://status.hyrien.com/ Thu, 01 May 2025 22:21:45 +0000 https://status.hyrien.com/#907872b868cf903f136b2ec5f2e2a343597dec0f0853d4f7e68cc8c95bcac114 Mail Service recovered System III – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Thu, 01 May 2025 22:21:45 +0000 https://status.hyrien.com/#907872b868cf903f136b2ec5f2e2a343597dec0f0853d4f7e68cc8c95bcac114 System III – Eygelshoven, Netherlands recovered Mail Service went down https://status.hyrien.com/ Thu, 01 May 2025 22:10:12 +0000 https://status.hyrien.com/#907872b868cf903f136b2ec5f2e2a343597dec0f0853d4f7e68cc8c95bcac114 Mail Service went down System III – Eygelshoven, Netherlands went down https://status.hyrien.com/ Thu, 01 May 2025 22:10:12 +0000 https://status.hyrien.com/#907872b868cf903f136b2ec5f2e2a343597dec0f0853d4f7e68cc8c95bcac114 System III – Eygelshoven, Netherlands went down Backend I recovered https://status.hyrien.com/ Sun, 13 Apr 2025 21:34:26 +0000 https://status.hyrien.com/#7ba709c747a9f6f1408f62c4980b7d23c3050cdbd911ee3b698b22c98fe208e0 Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 13 Apr 2025 21:04:25 +0000 https://status.hyrien.com/#7ba709c747a9f6f1408f62c4980b7d23c3050cdbd911ee3b698b22c98fe208e0 Backend I went down Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:50:01 +0000 https://status.hyrien.com/#a17095d3b72e4ebd0641efb32642846f95030700c86e7e9afe1ad8c804ae1757 Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:43:57 +0000 https://status.hyrien.com/#a17095d3b72e4ebd0641efb32642846f95030700c86e7e9afe1ad8c804ae1757 Backend I went down Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:34:59 +0000 https://status.hyrien.com/#1b78a737142be4602b790ccd939ab707f43eaa935e3c71d9d93da0acee0201a8 Backend I recovered Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:33:22 +0000 https://status.hyrien.com/#8f4b6fa98d34d1377301a6c551ab214bb6d033f0c1bc46effc8dfeda438dd134 Service I recovered Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:33:22 +0000 https://status.hyrien.com/#8f4b6fa98d34d1377301a6c551ab214bb6d033f0c1bc46effc8dfeda438dd134 Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:33:22 +0000 https://status.hyrien.com/#8f4b6fa98d34d1377301a6c551ab214bb6d033f0c1bc46effc8dfeda438dd134 System I – Eygelshoven, Netherlands recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:32:31 +0000 https://status.hyrien.com/#538721047c3f773ca084e9d8f3aa601206c9a1745cd55c886ff09f039101b0b7 Service II recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:32:31 +0000 https://status.hyrien.com/#538721047c3f773ca084e9d8f3aa601206c9a1745cd55c886ff09f039101b0b7 Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:32:31 +0000 https://status.hyrien.com/#538721047c3f773ca084e9d8f3aa601206c9a1745cd55c886ff09f039101b0b7 System II – Eygelshoven, Netherlands recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:31:55 +0000 https://status.hyrien.com/#1b78a737142be4602b790ccd939ab707f43eaa935e3c71d9d93da0acee0201a8 Backend I went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:27:40 +0000 https://status.hyrien.com/#8f4b6fa98d34d1377301a6c551ab214bb6d033f0c1bc46effc8dfeda438dd134 Service I went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:27:40 +0000 https://status.hyrien.com/#8f4b6fa98d34d1377301a6c551ab214bb6d033f0c1bc46effc8dfeda438dd134 Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:27:40 +0000 https://status.hyrien.com/#8f4b6fa98d34d1377301a6c551ab214bb6d033f0c1bc46effc8dfeda438dd134 System I – Eygelshoven, Netherlands went down Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:26:49 +0000 https://status.hyrien.com/#538721047c3f773ca084e9d8f3aa601206c9a1745cd55c886ff09f039101b0b7 Service II went down Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:26:49 +0000 https://status.hyrien.com/#538721047c3f773ca084e9d8f3aa601206c9a1745cd55c886ff09f039101b0b7 Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 08:26:49 +0000 https://status.hyrien.com/#538721047c3f773ca084e9d8f3aa601206c9a1745cd55c886ff09f039101b0b7 System II – Eygelshoven, Netherlands went down Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 08:11:00 +0000 https://status.hyrien.com/#d767a7f083c5916be5790a7cdfb61a3b03547d758d9398a8c903a8f68ffc0797 Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 07:59:24 +0000 https://status.hyrien.com/#d767a7f083c5916be5790a7cdfb61a3b03547d758d9398a8c903a8f68ffc0797 Backend I went down Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 07:55:55 +0000 https://status.hyrien.com/#d68023ebb2aad94ca6d7d11903345be6957f410622a9ea4907acbfffbbbfba7a Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 07:41:25 +0000 https://status.hyrien.com/#d68023ebb2aad94ca6d7d11903345be6957f410622a9ea4907acbfffbbbfba7a Backend I went down Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 07:37:57 +0000 https://status.hyrien.com/#793d9244389de34e568558075b15a277db216e731e91b9c890cfe357b75b0525 Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 07:16:50 +0000 https://status.hyrien.com/#793d9244389de34e568558075b15a277db216e731e91b9c890cfe357b75b0525 Backend I went down Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 07:06:09 +0000 https://status.hyrien.com/#95da12f356e9e396f68a846a8ed8da5b66a5184fd8e726c3c871a85428f4da84 Service I recovered Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 07:06:09 +0000 https://status.hyrien.com/#95da12f356e9e396f68a846a8ed8da5b66a5184fd8e726c3c871a85428f4da84 Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 07:06:09 +0000 https://status.hyrien.com/#95da12f356e9e396f68a846a8ed8da5b66a5184fd8e726c3c871a85428f4da84 System I – Eygelshoven, Netherlands recovered Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 07:04:58 +0000 https://status.hyrien.com/#96e2030629c886dfa52fd565c86d45a592b37ed623266c4641e234f72aecf3b4 Backend I recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:59:26 +0000 https://status.hyrien.com/#2d0ab04255d350760a196fbca845bdd4acb30b45924504912d21c4b9f347800f Service II recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:59:26 +0000 https://status.hyrien.com/#2d0ab04255d350760a196fbca845bdd4acb30b45924504912d21c4b9f347800f Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:59:26 +0000 https://status.hyrien.com/#2d0ab04255d350760a196fbca845bdd4acb30b45924504912d21c4b9f347800f System II – Eygelshoven, Netherlands recovered Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:57:32 +0000 https://status.hyrien.com/#95da12f356e9e396f68a846a8ed8da5b66a5184fd8e726c3c871a85428f4da84 Service I went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:57:32 +0000 https://status.hyrien.com/#95da12f356e9e396f68a846a8ed8da5b66a5184fd8e726c3c871a85428f4da84 Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:57:32 +0000 https://status.hyrien.com/#95da12f356e9e396f68a846a8ed8da5b66a5184fd8e726c3c871a85428f4da84 System I – Eygelshoven, Netherlands went down Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:54:09 +0000 https://status.hyrien.com/#6c5422035ea1720e340534f9afb3bd0638ed772d7b719fe398dfcc106d006afb Service I recovered Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:54:09 +0000 https://status.hyrien.com/#6c5422035ea1720e340534f9afb3bd0638ed772d7b719fe398dfcc106d006afb Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:54:09 +0000 https://status.hyrien.com/#6c5422035ea1720e340534f9afb3bd0638ed772d7b719fe398dfcc106d006afb System I – Eygelshoven, Netherlands recovered Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:53:42 +0000 https://status.hyrien.com/#2d0ab04255d350760a196fbca845bdd4acb30b45924504912d21c4b9f347800f Service II went down Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:53:42 +0000 https://status.hyrien.com/#2d0ab04255d350760a196fbca845bdd4acb30b45924504912d21c4b9f347800f Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:53:42 +0000 https://status.hyrien.com/#2d0ab04255d350760a196fbca845bdd4acb30b45924504912d21c4b9f347800f System II – Eygelshoven, Netherlands went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:39:35 +0000 https://status.hyrien.com/#6c5422035ea1720e340534f9afb3bd0638ed772d7b719fe398dfcc106d006afb Service I went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:39:35 +0000 https://status.hyrien.com/#6c5422035ea1720e340534f9afb3bd0638ed772d7b719fe398dfcc106d006afb Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:39:35 +0000 https://status.hyrien.com/#6c5422035ea1720e340534f9afb3bd0638ed772d7b719fe398dfcc106d006afb System I – Eygelshoven, Netherlands went down Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:20:20 +0000 https://status.hyrien.com/#1cfd16cfd65b95e27f488fd78dec3b792b2d47f951ca4d582f91ce30935505e8 Service II recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:20:20 +0000 https://status.hyrien.com/#1cfd16cfd65b95e27f488fd78dec3b792b2d47f951ca4d582f91ce30935505e8 Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 06:20:20 +0000 https://status.hyrien.com/#1cfd16cfd65b95e27f488fd78dec3b792b2d47f951ca4d582f91ce30935505e8 System II – Eygelshoven, Netherlands recovered Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:14:45 +0000 https://status.hyrien.com/#1cfd16cfd65b95e27f488fd78dec3b792b2d47f951ca4d582f91ce30935505e8 Service II went down Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:14:45 +0000 https://status.hyrien.com/#1cfd16cfd65b95e27f488fd78dec3b792b2d47f951ca4d582f91ce30935505e8 Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 06:14:45 +0000 https://status.hyrien.com/#1cfd16cfd65b95e27f488fd78dec3b792b2d47f951ca4d582f91ce30935505e8 System II – Eygelshoven, Netherlands went down Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:57:15 +0000 https://status.hyrien.com/#18a33bf980ca0871368ea3f2d95a90dca91b3a1cf4df46258ae34cac4226cc5d Service I recovered Service I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:57:15 +0000 https://status.hyrien.com/#18a33bf980ca0871368ea3f2d95a90dca91b3a1cf4df46258ae34cac4226cc5d Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:57:15 +0000 https://status.hyrien.com/#18a33bf980ca0871368ea3f2d95a90dca91b3a1cf4df46258ae34cac4226cc5d System I – Eygelshoven, Netherlands recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:53:10 +0000 https://status.hyrien.com/#96e2030629c886dfa52fd565c86d45a592b37ed623266c4641e234f72aecf3b4 Backend I went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:51:35 +0000 https://status.hyrien.com/#18a33bf980ca0871368ea3f2d95a90dca91b3a1cf4df46258ae34cac4226cc5d Service I went down Service I went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:51:35 +0000 https://status.hyrien.com/#18a33bf980ca0871368ea3f2d95a90dca91b3a1cf4df46258ae34cac4226cc5d Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:51:35 +0000 https://status.hyrien.com/#18a33bf980ca0871368ea3f2d95a90dca91b3a1cf4df46258ae34cac4226cc5d System I – Eygelshoven, Netherlands went down Backend I recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:25:51 +0000 https://status.hyrien.com/#f779e3f82bdd6985be70c2a17e3fbbbebcd8dea14c991a841ca5bfe096f69aec Backend I recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:23:25 +0000 https://status.hyrien.com/#f0f406e681623c9ac97a829a5504a20996f59ce435a920ee61570af540afc598 Service II recovered Service II recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:23:25 +0000 https://status.hyrien.com/#f0f406e681623c9ac97a829a5504a20996f59ce435a920ee61570af540afc598 Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 06 Apr 2025 05:23:25 +0000 https://status.hyrien.com/#f0f406e681623c9ac97a829a5504a20996f59ce435a920ee61570af540afc598 System II – Eygelshoven, Netherlands recovered Backend I went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:20:30 +0000 https://status.hyrien.com/#f779e3f82bdd6985be70c2a17e3fbbbebcd8dea14c991a841ca5bfe096f69aec Backend I went down Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:17:44 +0000 https://status.hyrien.com/#f0f406e681623c9ac97a829a5504a20996f59ce435a920ee61570af540afc598 Service II went down Service II went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:17:44 +0000 https://status.hyrien.com/#f0f406e681623c9ac97a829a5504a20996f59ce435a920ee61570af540afc598 Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 06 Apr 2025 05:17:44 +0000 https://status.hyrien.com/#f0f406e681623c9ac97a829a5504a20996f59ce435a920ee61570af540afc598 System II – Eygelshoven, Netherlands went down Backend I recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:07:13 +0000 https://status.hyrien.com/#5b5d3ed60de46f9c58eea677bb43b7bc3866506b64d7a5514316834c4a02773b Backend I recovered Service I recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:05:36 +0000 https://status.hyrien.com/#2ab90ae8c07d92088c6671e44d4abf55cf0b9841ce4f2fb89e48a045f3e9c6cc Service I recovered Service I recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:05:36 +0000 https://status.hyrien.com/#2ab90ae8c07d92088c6671e44d4abf55cf0b9841ce4f2fb89e48a045f3e9c6cc Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:05:36 +0000 https://status.hyrien.com/#2ab90ae8c07d92088c6671e44d4abf55cf0b9841ce4f2fb89e48a045f3e9c6cc System I – Eygelshoven, Netherlands recovered Service II recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:04:42 +0000 https://status.hyrien.com/#085186711e70969f1a342d0419ab9755f56f83b9612a24b093242e55cc25c81e Service II recovered Service II recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:04:42 +0000 https://status.hyrien.com/#085186711e70969f1a342d0419ab9755f56f83b9612a24b093242e55cc25c81e Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Tue, 01 Apr 2025 15:04:42 +0000 https://status.hyrien.com/#085186711e70969f1a342d0419ab9755f56f83b9612a24b093242e55cc25c81e System II – Eygelshoven, Netherlands recovered Service I went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:56:51 +0000 https://status.hyrien.com/#2ab90ae8c07d92088c6671e44d4abf55cf0b9841ce4f2fb89e48a045f3e9c6cc Service I went down Service I went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:56:51 +0000 https://status.hyrien.com/#2ab90ae8c07d92088c6671e44d4abf55cf0b9841ce4f2fb89e48a045f3e9c6cc Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:56:51 +0000 https://status.hyrien.com/#2ab90ae8c07d92088c6671e44d4abf55cf0b9841ce4f2fb89e48a045f3e9c6cc System I – Eygelshoven, Netherlands went down Service II went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:56:06 +0000 https://status.hyrien.com/#085186711e70969f1a342d0419ab9755f56f83b9612a24b093242e55cc25c81e Service II went down Service II went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:56:06 +0000 https://status.hyrien.com/#085186711e70969f1a342d0419ab9755f56f83b9612a24b093242e55cc25c81e Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:56:06 +0000 https://status.hyrien.com/#085186711e70969f1a342d0419ab9755f56f83b9612a24b093242e55cc25c81e System II – Eygelshoven, Netherlands went down Backend I went down https://status.hyrien.com/ Tue, 01 Apr 2025 14:49:52 +0000 https://status.hyrien.com/#5b5d3ed60de46f9c58eea677bb43b7bc3866506b64d7a5514316834c4a02773b Backend I went down Backend I recovered https://status.hyrien.com/ Mon, 31 Mar 2025 20:37:00 +0000 https://status.hyrien.com/#36435bfd8608428e850f9fb4a222798eecc163e6babd6403fc3c12c26ddb2562 Backend I recovered Backend I went down https://status.hyrien.com/ Mon, 31 Mar 2025 20:05:26 +0000 https://status.hyrien.com/#36435bfd8608428e850f9fb4a222798eecc163e6babd6403fc3c12c26ddb2562 Backend I went down Backend I recovered https://status.hyrien.com/ Mon, 31 Mar 2025 19:27:39 +0000 https://status.hyrien.com/#73f63dd09a9f2f76c27f4ffebf8462ebc04fc16cdeac2ccabf22c748fa2c81ed Backend I recovered Backend I went down https://status.hyrien.com/ Mon, 31 Mar 2025 19:16:02 +0000 https://status.hyrien.com/#73f63dd09a9f2f76c27f4ffebf8462ebc04fc16cdeac2ccabf22c748fa2c81ed Backend I went down Backend I recovered https://status.hyrien.com/ Mon, 31 Mar 2025 19:13:26 +0000 https://status.hyrien.com/#a9d77e6335136c290e188845ce545247c8259895e847cf045c61f7b1c3d322cd Backend I recovered Backend I went down https://status.hyrien.com/ Mon, 31 Mar 2025 18:59:38 +0000 https://status.hyrien.com/#a9d77e6335136c290e188845ce545247c8259895e847cf045c61f7b1c3d322cd Backend I went down Backend I recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:31:17 +0000 https://status.hyrien.com/#9c78a4e25c69bc555bf363884a9f797730eb3f5cd10efad1eec29275119fb0d8 Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:24:17 +0000 https://status.hyrien.com/#9c78a4e25c69bc555bf363884a9f797730eb3f5cd10efad1eec29275119fb0d8 Backend I went down Backend I recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:20:33 +0000 https://status.hyrien.com/#d657d1ef00f320af01fd512747ada1e868ff92ce0be38aa30a7f73b780eda02b Backend I recovered Backend I went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:15:14 +0000 https://status.hyrien.com/#d657d1ef00f320af01fd512747ada1e868ff92ce0be38aa30a7f73b780eda02b Backend I went down Service I recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:11:34 +0000 https://status.hyrien.com/#86a0f64142bf407b19c04b0ca6293da0e3bbe90d0dddac1d18a0d75604cf7fae Service I recovered Service I recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:11:34 +0000 https://status.hyrien.com/#86a0f64142bf407b19c04b0ca6293da0e3bbe90d0dddac1d18a0d75604cf7fae Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:11:34 +0000 https://status.hyrien.com/#86a0f64142bf407b19c04b0ca6293da0e3bbe90d0dddac1d18a0d75604cf7fae System I – Eygelshoven, Netherlands recovered Backend I recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:10:50 +0000 https://status.hyrien.com/#a9941ca9bff2460967761fa8965477d6c2981a11d9f79e62c95b2ae294c82ca0 Backend I recovered Service II recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:10:42 +0000 https://status.hyrien.com/#e58f9a57b8152acb32df262ba94934c4987274c39c29d9c4f2578c09e2618ed5 Service II recovered Service II recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:10:42 +0000 https://status.hyrien.com/#e58f9a57b8152acb32df262ba94934c4987274c39c29d9c4f2578c09e2618ed5 Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Sun, 30 Mar 2025 20:10:42 +0000 https://status.hyrien.com/#e58f9a57b8152acb32df262ba94934c4987274c39c29d9c4f2578c09e2618ed5 System II – Eygelshoven, Netherlands recovered Service I went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:02:55 +0000 https://status.hyrien.com/#86a0f64142bf407b19c04b0ca6293da0e3bbe90d0dddac1d18a0d75604cf7fae Service I went down Service I went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:02:55 +0000 https://status.hyrien.com/#86a0f64142bf407b19c04b0ca6293da0e3bbe90d0dddac1d18a0d75604cf7fae Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:02:55 +0000 https://status.hyrien.com/#86a0f64142bf407b19c04b0ca6293da0e3bbe90d0dddac1d18a0d75604cf7fae System I – Eygelshoven, Netherlands went down Service II went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:02:06 +0000 https://status.hyrien.com/#e58f9a57b8152acb32df262ba94934c4987274c39c29d9c4f2578c09e2618ed5 Service II went down Service II went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:02:06 +0000 https://status.hyrien.com/#e58f9a57b8152acb32df262ba94934c4987274c39c29d9c4f2578c09e2618ed5 Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Sun, 30 Mar 2025 20:02:06 +0000 https://status.hyrien.com/#e58f9a57b8152acb32df262ba94934c4987274c39c29d9c4f2578c09e2618ed5 System II – Eygelshoven, Netherlands went down Backend I went down https://status.hyrien.com/ Sun, 30 Mar 2025 19:57:15 +0000 https://status.hyrien.com/#a9941ca9bff2460967761fa8965477d6c2981a11d9f79e62c95b2ae294c82ca0 Backend I went down Backend I recovered https://status.hyrien.com/ Sat, 29 Mar 2025 12:28:19 +0000 https://status.hyrien.com/#13575cf259dbcafc249b0d766dd804a3b381af8e8c5299f8cbf34c13114a6aa3 Backend I recovered Backend I went down https://status.hyrien.com/ Sat, 29 Mar 2025 12:18:14 +0000 https://status.hyrien.com/#13575cf259dbcafc249b0d766dd804a3b381af8e8c5299f8cbf34c13114a6aa3 Backend I went down Backend I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 13:00:54 +0000 https://status.hyrien.com/#be7c99160420610d2b67ffbad227b3676e2a7991dc2a2f0a33e50562225f3c48 Backend I recovered Backend I went down https://status.hyrien.com/ Fri, 14 Mar 2025 12:54:32 +0000 https://status.hyrien.com/#be7c99160420610d2b67ffbad227b3676e2a7991dc2a2f0a33e50562225f3c48 Backend I went down Backend I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:55:30 +0000 https://status.hyrien.com/#0327453d71f1352bd564c5721fd4228ec264b5ccbe42891fdd2e6791c01d9cc8 Backend I recovered Service I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:53:50 +0000 https://status.hyrien.com/#5b221c9467ecdf0d9bff3d4ab1c1e080079c66d57cad2e4dbda8033c47809497 Service I recovered Service I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:53:50 +0000 https://status.hyrien.com/#5b221c9467ecdf0d9bff3d4ab1c1e080079c66d57cad2e4dbda8033c47809497 Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:53:50 +0000 https://status.hyrien.com/#5b221c9467ecdf0d9bff3d4ab1c1e080079c66d57cad2e4dbda8033c47809497 System I – Eygelshoven, Netherlands recovered Service II recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:52:58 +0000 https://status.hyrien.com/#59b91aedbf20e949137d28b3a46ed3d16699a7238f6425a1266829b12926b02f Service II recovered Service II recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:52:58 +0000 https://status.hyrien.com/#59b91aedbf20e949137d28b3a46ed3d16699a7238f6425a1266829b12926b02f Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:52:58 +0000 https://status.hyrien.com/#59b91aedbf20e949137d28b3a46ed3d16699a7238f6425a1266829b12926b02f System II – Eygelshoven, Netherlands recovered Service II went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:38:02 +0000 https://status.hyrien.com/#59b91aedbf20e949137d28b3a46ed3d16699a7238f6425a1266829b12926b02f Service II went down Service II went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:38:02 +0000 https://status.hyrien.com/#59b91aedbf20e949137d28b3a46ed3d16699a7238f6425a1266829b12926b02f Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:38:02 +0000 https://status.hyrien.com/#59b91aedbf20e949137d28b3a46ed3d16699a7238f6425a1266829b12926b02f System II – Eygelshoven, Netherlands went down Service I went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:36:13 +0000 https://status.hyrien.com/#5b221c9467ecdf0d9bff3d4ab1c1e080079c66d57cad2e4dbda8033c47809497 Service I went down Service I went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:36:13 +0000 https://status.hyrien.com/#5b221c9467ecdf0d9bff3d4ab1c1e080079c66d57cad2e4dbda8033c47809497 Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:36:13 +0000 https://status.hyrien.com/#5b221c9467ecdf0d9bff3d4ab1c1e080079c66d57cad2e4dbda8033c47809497 System I – Eygelshoven, Netherlands went down Backend I went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:33:29 +0000 https://status.hyrien.com/#0327453d71f1352bd564c5721fd4228ec264b5ccbe42891fdd2e6791c01d9cc8 Backend I went down Service I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:29:50 +0000 https://status.hyrien.com/#85c94f174a9df4d6022e2809a44e0ad8255288fa726b53a700d2097ced4d51dd Service I recovered Service I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:29:50 +0000 https://status.hyrien.com/#85c94f174a9df4d6022e2809a44e0ad8255288fa726b53a700d2097ced4d51dd Service I recovered System I – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:29:50 +0000 https://status.hyrien.com/#85c94f174a9df4d6022e2809a44e0ad8255288fa726b53a700d2097ced4d51dd System I – Eygelshoven, Netherlands recovered Service II recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:28:57 +0000 https://status.hyrien.com/#34648f8848aba1b287ac2cb575e7515ca44f2904e0997d15528786031cfe528a Service II recovered Service II recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:28:57 +0000 https://status.hyrien.com/#34648f8848aba1b287ac2cb575e7515ca44f2904e0997d15528786031cfe528a Service II recovered System II – Eygelshoven, Netherlands recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:28:57 +0000 https://status.hyrien.com/#34648f8848aba1b287ac2cb575e7515ca44f2904e0997d15528786031cfe528a System II – Eygelshoven, Netherlands recovered Backend I recovered https://status.hyrien.com/ Fri, 14 Mar 2025 02:28:30 +0000 https://status.hyrien.com/#68afff1c1b6431c98b2db9fe44d018d74981766688534b5364a27939e59427b9 Backend I recovered Service I went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:23:51 +0000 https://status.hyrien.com/#85c94f174a9df4d6022e2809a44e0ad8255288fa726b53a700d2097ced4d51dd Service I went down Service I went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:23:51 +0000 https://status.hyrien.com/#85c94f174a9df4d6022e2809a44e0ad8255288fa726b53a700d2097ced4d51dd Service I went down System I – Eygelshoven, Netherlands went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:23:51 +0000 https://status.hyrien.com/#85c94f174a9df4d6022e2809a44e0ad8255288fa726b53a700d2097ced4d51dd System I – Eygelshoven, Netherlands went down Service II went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:23:18 +0000 https://status.hyrien.com/#34648f8848aba1b287ac2cb575e7515ca44f2904e0997d15528786031cfe528a Service II went down Service II went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:23:18 +0000 https://status.hyrien.com/#34648f8848aba1b287ac2cb575e7515ca44f2904e0997d15528786031cfe528a Service II went down System II – Eygelshoven, Netherlands went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:23:18 +0000 https://status.hyrien.com/#34648f8848aba1b287ac2cb575e7515ca44f2904e0997d15528786031cfe528a System II – Eygelshoven, Netherlands went down Backend I went down https://status.hyrien.com/ Fri, 14 Mar 2025 02:21:09 +0000 https://status.hyrien.com/#68afff1c1b6431c98b2db9fe44d018d74981766688534b5364a27939e59427b9 Backend I went down Malfunction of the backend https://status.hyrien.com/incident/471118 Mon, 02 Dec 2024 15:36:00 -0000 https://status.hyrien.com/incident/471118#295baff21e50f80e7dc97b8194b8cd754a33e7ff9803a591c000eaeb8b0055a5 The problem has been fixed. We are currently investigating how this problem occurred and apologise for this outage. Malfunction of the backend https://status.hyrien.com/incident/471118 Mon, 02 Dec 2024 04:19:00 -0000 https://status.hyrien.com/incident/471118#ebf1460c8f5f3f02daeeeed48fc49aee6f8a1815adb4e0bd48e610bc0b081f4f Our systems are experiencing an outage of the Soccer Bot™ Discord bot. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:53:00 -0000 https://status.hyrien.com/incident/464099#8cfa01d86499921e443f6f3e219375a61c304e5c6a966960c44f9f71176fd319 All services are now available again. We apologize for the inconvenience and thank you for your patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 14:21:00 -0000 https://status.hyrien.com/incident/464099#075233ecb6f9973e05740765e5a6db835f1b4476cf8f16792771dc69e162bfbf Some services are slowly becoming available again for some users. We kindly ask for a little patience. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 13:48:00 -0000 https://status.hyrien.com/incident/464099#51d4b21b5be5da4fdb7e3fcd834585305f3fc13c5bfe70247161a24dc8ba25f3 There was a smoke development in the high-voltage substation in the data center region. As soon as the fire department indicates that it is safe, the engineers can continue with the investigation. So the exact end time is not known. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:25:00 -0000 https://status.hyrien.com/incident/464099#58215dfda59fddd9633579fea3b3700663675f5fd27010763c62ea08e537ee0c Currently, troubleshooting is in progress. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Data center outage https://status.hyrien.com/incident/464099 Tue, 19 Nov 2024 12:00:00 -0000 https://status.hyrien.com/incident/464099#b327d1f446ba15cbd3eef7a0f114a1800ea98e13dd7dad2ce38b99605015e248 The data center is currently experiencing connection problems, which means that all systems are currently unavailable. Malfunction of the backend https://status.hyrien.com/incident/460931 Wed, 13 Nov 2024 07:48:00 -0000 https://status.hyrien.com/incident/460931#fd0f5ba116389501aaeb6adeb48ea18088e9c2b3fad8d640dafc3c472a2fa7c4 There were a total of three short outages within the time specified above. Due to the short duration of the outages, there was no impact on ongoing games and their events. Malfunction of the backend https://status.hyrien.com/incident/460931 Wed, 13 Nov 2024 06:26:00 -0000 https://status.hyrien.com/incident/460931#207478c57b4383b5ab6dabe36f2a0d14df48815534873a64952d21fe6b261959 There are currently failures in the backend of the Soccer Bot™ bot. We are checking the problem. API Service Outage https://status.hyrien.com/incident/414286 Thu, 15 Aug 2024 10:30:00 -0000 https://status.hyrien.com/incident/414286#1059a8d723e6af36db5c91b6b44345aa90927816c007c5944a051f539ce4b21c The problem was quickly recognised by our API service provider and has now been fully resolved. Our service is now available again. We apologise for the 30-minute interruption. API Service Outage https://status.hyrien.com/incident/414286 Thu, 15 Aug 2024 10:00:00 -0000 https://status.hyrien.com/incident/414286#be7a95cb850f9462bcdc98aaa807699e388fdac27109a15d9c37f406e8827e7a All users are affected. Our API service provider is currently reporting an outage. Our services are also currently affected by this. API Service Outage https://status.hyrien.com/incident/400600 Fri, 19 Jul 2024 15:30:00 -0000 https://status.hyrien.com/incident/400600#ae93664d94bfc571058335f66237c6b34bdaefd6bd173a6cfb7b607ca1cb2ccf The problem has been identified and has been successfully resolved. The services are fully available. API Service Outage https://status.hyrien.com/incident/400600 Fri, 19 Jul 2024 12:00:00 -0000 https://status.hyrien.com/incident/400600#ae02ec8d5925d6a9d24c722c69e7ed87e0f775e92a8f038e6174af10217c03f6 The problem has been partially identified. However, the inconvenience has not yet been fully resolved. Due to the current situation, we have decided to disable the Discord bot for the time being until the issue is resolved. We hope to be able to fix the problem in the next few hours. API Service Outage https://status.hyrien.com/incident/400600 Fri, 19 Jul 2024 09:30:00 -0000 https://status.hyrien.com/incident/400600#fc6359671349675c3c9d9b914806d8074827ddaa2709473bd667c36c736dff5c All users are affected. Due to a malfunction of a third-party provider, the data of our API provider is not being updated. Soccer Bot™ is currently affected.