Incidents | flyxe.cloud Incidents reported on status page for flyxe.cloud https://status.flyxe.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/1229f01e458025f8b751216380865c57.png Incidents | flyxe.cloud https://status.flyxe.cloud/ en server #2 (NL) recovered https://status.flyxe.cloud/ Wed, 11 Feb 2026 09:54:40 +0000 https://status.flyxe.cloud/#c75d7c0cf2027cba5609460884fa9054b3d05c615841f0b98523de083f7b5c47 server #2 (NL) recovered server #2 (NL) went down https://status.flyxe.cloud/ Wed, 11 Feb 2026 08:29:24 +0000 https://status.flyxe.cloud/#c75d7c0cf2027cba5609460884fa9054b3d05c615841f0b98523de083f7b5c47 server #2 (NL) went down server #4 (RU) recovered https://status.flyxe.cloud/ Wed, 11 Feb 2026 03:40:22 +0000 https://status.flyxe.cloud/#afc27df07b046683199849ff04f8697e9fcca4648d5c3205afa21c7ecfe6df4b server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Wed, 11 Feb 2026 03:37:14 +0000 https://status.flyxe.cloud/#afc27df07b046683199849ff04f8697e9fcca4648d5c3205afa21c7ecfe6df4b server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Tue, 10 Feb 2026 23:25:13 +0000 https://status.flyxe.cloud/#6d9d37c72be33e9eea00357946c1e995637e5ecfb40828bd26d270bb68d10d3f server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Tue, 10 Feb 2026 23:19:08 +0000 https://status.flyxe.cloud/#6d9d37c72be33e9eea00357946c1e995637e5ecfb40828bd26d270bb68d10d3f server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Tue, 10 Feb 2026 23:04:18 +0000 https://status.flyxe.cloud/#5cf36ef611ad6d9d87ebc51c2471736b765354415d4d4b129d16b69a5c9e4b2a server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Tue, 10 Feb 2026 22:58:21 +0000 https://status.flyxe.cloud/#5cf36ef611ad6d9d87ebc51c2471736b765354415d4d4b129d16b69a5c9e4b2a server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Tue, 10 Feb 2026 19:47:18 +0000 https://status.flyxe.cloud/#a94629eb58c3e4755dc7e2b33e9f15859615255d1745208e6bd58f4198db9105 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Tue, 10 Feb 2026 19:43:10 +0000 https://status.flyxe.cloud/#a94629eb58c3e4755dc7e2b33e9f15859615255d1745208e6bd58f4198db9105 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Tue, 10 Feb 2026 07:37:15 +0000 https://status.flyxe.cloud/#aadaab039a097cd009eb716c014a62c92bb61447a73f1905a774a2df9eefddb1 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Tue, 10 Feb 2026 07:25:14 +0000 https://status.flyxe.cloud/#aadaab039a097cd009eb716c014a62c92bb61447a73f1905a774a2df9eefddb1 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Mon, 09 Feb 2026 15:58:17 +0000 https://status.flyxe.cloud/#a6c596943fb5b922bec638dc6d642e97fa0ba1a5d3a875f05406aa397845faf3 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Mon, 09 Feb 2026 15:55:12 +0000 https://status.flyxe.cloud/#a6c596943fb5b922bec638dc6d642e97fa0ba1a5d3a875f05406aa397845faf3 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Mon, 09 Feb 2026 11:10:28 +0000 https://status.flyxe.cloud/#9edc2879eb21649fdf1c77d6cdb72068c4543d698b77778b30cc669407ebb099 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Mon, 09 Feb 2026 10:52:16 +0000 https://status.flyxe.cloud/#9edc2879eb21649fdf1c77d6cdb72068c4543d698b77778b30cc669407ebb099 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 08 Feb 2026 13:25:12 +0000 https://status.flyxe.cloud/#99757447efb9edb3d9d7d0bc37c7ea3e751b1a2022116a0b15e26d75f20b3a34 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 08 Feb 2026 13:22:14 +0000 https://status.flyxe.cloud/#99757447efb9edb3d9d7d0bc37c7ea3e751b1a2022116a0b15e26d75f20b3a34 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 08 Feb 2026 12:52:23 +0000 https://status.flyxe.cloud/#efa441cac9dd9140db1bfdc8d3b2ae41837ed010b805b8467b1eab534dbffa58 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 08 Feb 2026 12:49:06 +0000 https://status.flyxe.cloud/#efa441cac9dd9140db1bfdc8d3b2ae41837ed010b805b8467b1eab534dbffa58 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 08 Feb 2026 10:43:30 +0000 https://status.flyxe.cloud/#4c14ee5eda094c3c2838a7daf38f994ebecff86a6c6e4d0fcf9efdd71dd0d37e server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 08 Feb 2026 10:40:19 +0000 https://status.flyxe.cloud/#4c14ee5eda094c3c2838a7daf38f994ebecff86a6c6e4d0fcf9efdd71dd0d37e server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 08 Feb 2026 10:25:05 +0000 https://status.flyxe.cloud/#fd055ed0756d4f5e95d74edc45f215ffb7d0d82a27a7d2bada6c2a6c06418601 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 08 Feb 2026 10:22:16 +0000 https://status.flyxe.cloud/#fd055ed0756d4f5e95d74edc45f215ffb7d0d82a27a7d2bada6c2a6c06418601 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 08 Feb 2026 09:43:24 +0000 https://status.flyxe.cloud/#51cb9b8d55a906ab701ed519b6ba0935daf39202f41d41adca61adec7eda86b5 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 08 Feb 2026 09:40:55 +0000 https://status.flyxe.cloud/#51cb9b8d55a906ab701ed519b6ba0935daf39202f41d41adca61adec7eda86b5 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 23:37:09 +0000 https://status.flyxe.cloud/#ae8c6b7bdd60b6d35bd57eca5304a24bb661bb1609866531ee3ed42d011d19fb server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 23:34:25 +0000 https://status.flyxe.cloud/#ae8c6b7bdd60b6d35bd57eca5304a24bb661bb1609866531ee3ed42d011d19fb server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 23:22:39 +0000 https://status.flyxe.cloud/#34ec480ddd38f3b398feae1a6e1501c4fae28e09f10fcd69b5c659ab8ea24b28 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 22:58:25 +0000 https://status.flyxe.cloud/#34ec480ddd38f3b398feae1a6e1501c4fae28e09f10fcd69b5c659ab8ea24b28 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 22:37:17 +0000 https://status.flyxe.cloud/#7038ebf9ef9e09f84db891172117b1d2e8476f53b5bd9b98b34e1d098fdd98da server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 22:31:20 +0000 https://status.flyxe.cloud/#7038ebf9ef9e09f84db891172117b1d2e8476f53b5bd9b98b34e1d098fdd98da server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 21:37:12 +0000 https://status.flyxe.cloud/#b51772d3334c0a94a7c21bdaa5ec6fee09f13dcf2a417b48792befcbf0f02856 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 21:34:17 +0000 https://status.flyxe.cloud/#b51772d3334c0a94a7c21bdaa5ec6fee09f13dcf2a417b48792befcbf0f02856 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 21:10:26 +0000 https://status.flyxe.cloud/#9865b989cb29a713a172f8987ad99105373d632e87f070523506d1decff04c89 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 21:04:18 +0000 https://status.flyxe.cloud/#9865b989cb29a713a172f8987ad99105373d632e87f070523506d1decff04c89 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 20:43:12 +0000 https://status.flyxe.cloud/#ef31e6be056c9c64ee490b522b2097e83692c639a063c234e49dd5609e15f589 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 20:25:15 +0000 https://status.flyxe.cloud/#ef31e6be056c9c64ee490b522b2097e83692c639a063c234e49dd5609e15f589 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 20:10:18 +0000 https://status.flyxe.cloud/#679bd2883d0b8a5d1f3f84d55e5db19bb3f11506f7d8b66004dd16ad08fbaef8 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 20:01:17 +0000 https://status.flyxe.cloud/#679bd2883d0b8a5d1f3f84d55e5db19bb3f11506f7d8b66004dd16ad08fbaef8 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 19:40:19 +0000 https://status.flyxe.cloud/#66e0cedd8451f511364aa8b06ee8fb31bd6d9099cab5491fbc89548eb6afc65a server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 19:37:20 +0000 https://status.flyxe.cloud/#66e0cedd8451f511364aa8b06ee8fb31bd6d9099cab5491fbc89548eb6afc65a server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 14:58:16 +0000 https://status.flyxe.cloud/#44ae1c73669c9b909d9a35a714678c1db63fe1eb3ac126d0e2f0ed177101b66f server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 14:52:12 +0000 https://status.flyxe.cloud/#44ae1c73669c9b909d9a35a714678c1db63fe1eb3ac126d0e2f0ed177101b66f server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 14:10:20 +0000 https://status.flyxe.cloud/#2c2a672b306f81663165e0599f0b259c797c0c69288f9abceb9c75c0e1de008d server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 14:01:16 +0000 https://status.flyxe.cloud/#2c2a672b306f81663165e0599f0b259c797c0c69288f9abceb9c75c0e1de008d server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 13:55:15 +0000 https://status.flyxe.cloud/#7f76963f17b3973ae8e8f0dd5f5d1023f17be47338ee588702d4bbaf2122f371 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 13:31:18 +0000 https://status.flyxe.cloud/#7f76963f17b3973ae8e8f0dd5f5d1023f17be47338ee588702d4bbaf2122f371 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 12:25:15 +0000 https://status.flyxe.cloud/#b490a1696634211e5949a8ecd392a8d29c2ef1587919cd2fbcb619373b7f6254 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 12:22:29 +0000 https://status.flyxe.cloud/#b490a1696634211e5949a8ecd392a8d29c2ef1587919cd2fbcb619373b7f6254 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 06:19:15 +0000 https://status.flyxe.cloud/#518ad026a535b04f921a560905e9240022b50b9784222d7d897b8e9242260bc7 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 06:10:22 +0000 https://status.flyxe.cloud/#518ad026a535b04f921a560905e9240022b50b9784222d7d897b8e9242260bc7 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 04:04:21 +0000 https://status.flyxe.cloud/#0c9711b4e340eb221d90767dd4826229cb0d0106c61b23195b177083edbb8027 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 04:01:15 +0000 https://status.flyxe.cloud/#0c9711b4e340eb221d90767dd4826229cb0d0106c61b23195b177083edbb8027 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 01:16:18 +0000 https://status.flyxe.cloud/#86dee73c7525d3d7ba977e73881634c1efc24e2cbea6ca0e001b8f52246d1bd9 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 01:10:31 +0000 https://status.flyxe.cloud/#86dee73c7525d3d7ba977e73881634c1efc24e2cbea6ca0e001b8f52246d1bd9 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 01:07:23 +0000 https://status.flyxe.cloud/#db673d2c8adf62a3aedeb35640a36b5e4936b40d3ecfcd34a475ca644a573fb7 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 01:04:13 +0000 https://status.flyxe.cloud/#db673d2c8adf62a3aedeb35640a36b5e4936b40d3ecfcd34a475ca644a573fb7 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 07 Feb 2026 00:46:21 +0000 https://status.flyxe.cloud/#78a348fc60d944164a52b66b92e4e5edfdde2366eaf55b246fdade097528e017 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 07 Feb 2026 00:40:25 +0000 https://status.flyxe.cloud/#78a348fc60d944164a52b66b92e4e5edfdde2366eaf55b246fdade097528e017 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 06 Feb 2026 23:55:21 +0000 https://status.flyxe.cloud/#64afc18f2bc0f8a883eeb957637014aaaa485e3cf31088f25d0b4d730ebd0270 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 06 Feb 2026 23:52:20 +0000 https://status.flyxe.cloud/#64afc18f2bc0f8a883eeb957637014aaaa485e3cf31088f25d0b4d730ebd0270 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 06 Feb 2026 22:31:12 +0000 https://status.flyxe.cloud/#ec9fbde461b143c3703016baf3031e003ee9d2741d47ad673d110883be300863 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 06 Feb 2026 22:22:25 +0000 https://status.flyxe.cloud/#ec9fbde461b143c3703016baf3031e003ee9d2741d47ad673d110883be300863 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 06 Feb 2026 16:13:34 +0000 https://status.flyxe.cloud/#da53cb910cdfb22371b70957fbb4d0892b0bf6e55010077b334ac5e475469853 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 06 Feb 2026 16:10:18 +0000 https://status.flyxe.cloud/#da53cb910cdfb22371b70957fbb4d0892b0bf6e55010077b334ac5e475469853 server #4 (RU) went down server #3 (DE) recovered https://status.flyxe.cloud/ Fri, 06 Feb 2026 07:02:27 +0000 https://status.flyxe.cloud/#0b42b94a855a02e4c909635b30df42e899730e766735a09c76a056f901966aa5 server #3 (DE) recovered server #3 (DE) went down https://status.flyxe.cloud/ Fri, 06 Feb 2026 06:56:55 +0000 https://status.flyxe.cloud/#0b42b94a855a02e4c909635b30df42e899730e766735a09c76a056f901966aa5 server #3 (DE) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 06 Feb 2026 05:04:13 +0000 https://status.flyxe.cloud/#6c291fd1710521e4099c8667f50c8967ea623e310914ff61700c76314462e9d2 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 06 Feb 2026 05:01:11 +0000 https://status.flyxe.cloud/#6c291fd1710521e4099c8667f50c8967ea623e310914ff61700c76314462e9d2 server #4 (RU) went down server #3 (DE) recovered https://status.flyxe.cloud/ Tue, 03 Feb 2026 10:02:29 +0000 https://status.flyxe.cloud/#cb84c5c0d55b21ef8c7d6e72787527a1511c5bfcd2a0ff59b7d7e6edecf0990d server #3 (DE) recovered flyxe.cloud website recovered https://status.flyxe.cloud/ Tue, 03 Feb 2026 10:02:24 +0000 https://status.flyxe.cloud/#15938071f9491185f7030db577ed80998b60829fb383ad77f2c05a2134633618 flyxe.cloud website recovered server #1 (RU) recovered https://status.flyxe.cloud/ Tue, 03 Feb 2026 10:00:43 +0000 https://status.flyxe.cloud/#aed8e681cd949e2987aa06aec6f7ec395f786d71fac143e815f9f84934972ed7 server #1 (RU) recovered server #1 (RU) went down https://status.flyxe.cloud/ Tue, 03 Feb 2026 09:59:19 +0000 https://status.flyxe.cloud/#aed8e681cd949e2987aa06aec6f7ec395f786d71fac143e815f9f84934972ed7 server #1 (RU) went down flyxe.cloud website went down https://status.flyxe.cloud/ Tue, 03 Feb 2026 09:58:24 +0000 https://status.flyxe.cloud/#15938071f9491185f7030db577ed80998b60829fb383ad77f2c05a2134633618 flyxe.cloud website went down server #3 (DE) went down https://status.flyxe.cloud/ Tue, 03 Feb 2026 09:57:38 +0000 https://status.flyxe.cloud/#cb84c5c0d55b21ef8c7d6e72787527a1511c5bfcd2a0ff59b7d7e6edecf0990d server #3 (DE) went down server #3 (DE) recovered https://status.flyxe.cloud/ Mon, 02 Feb 2026 23:32:29 +0000 https://status.flyxe.cloud/#47594debf720540c2685493bcfcca4f946ebfe22d65b22c55900cb793d11bcc3 server #3 (DE) recovered server #3 (DE) went down https://status.flyxe.cloud/ Mon, 02 Feb 2026 23:28:09 +0000 https://status.flyxe.cloud/#47594debf720540c2685493bcfcca4f946ebfe22d65b22c55900cb793d11bcc3 server #3 (DE) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 01 Feb 2026 01:46:21 +0000 https://status.flyxe.cloud/#9579760cfab1180076fcafcd30f426ab15c58ac12147b2b7d808ee2de190b4ef server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 01 Feb 2026 01:43:18 +0000 https://status.flyxe.cloud/#9579760cfab1180076fcafcd30f426ab15c58ac12147b2b7d808ee2de190b4ef server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sun, 01 Feb 2026 00:37:13 +0000 https://status.flyxe.cloud/#0c1c3397ec8f986e7d813562887320928dc81d7b3fd6e43810360fe8a0c76d4a server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sun, 01 Feb 2026 00:34:15 +0000 https://status.flyxe.cloud/#0c1c3397ec8f986e7d813562887320928dc81d7b3fd6e43810360fe8a0c76d4a server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 22:31:15 +0000 https://status.flyxe.cloud/#fc4e53fccef4bc802113e14022998474bc49f1f1835e6a433944e6d1e1ec6277 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 22:28:11 +0000 https://status.flyxe.cloud/#fc4e53fccef4bc802113e14022998474bc49f1f1835e6a433944e6d1e1ec6277 server #4 (RU) went down server #5 (DE) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 21:34:54 +0000 https://status.flyxe.cloud/#726fb145c01d2cf9ac2d4a00ae27a9a81fb1192b555f145c7a3d7de5028d24b0 server #5 (DE) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 18:04:15 +0000 https://status.flyxe.cloud/#9f2b76e92b20e204c4e31690cfd394ce79c3a4446194f63f255dbb5b077ba6fe server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 17:58:20 +0000 https://status.flyxe.cloud/#9f2b76e92b20e204c4e31690cfd394ce79c3a4446194f63f255dbb5b077ba6fe server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 17:43:12 +0000 https://status.flyxe.cloud/#8a296d6b9462a02152be1b10634777843ce5b86a49f2371dd3be91924ba0ecd2 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 17:37:11 +0000 https://status.flyxe.cloud/#8a296d6b9462a02152be1b10634777843ce5b86a49f2371dd3be91924ba0ecd2 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 15:40:16 +0000 https://status.flyxe.cloud/#e8afabe727313558b98efd83f822aabf544d4316287514ec9bb3e9f8c636fdd7 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 15:37:13 +0000 https://status.flyxe.cloud/#e8afabe727313558b98efd83f822aabf544d4316287514ec9bb3e9f8c636fdd7 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 15:28:22 +0000 https://status.flyxe.cloud/#99bfacf7caf8aabe76211229a1ba0f94aa6f46f8337cf9ce3712c00c06b073b8 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 15:22:19 +0000 https://status.flyxe.cloud/#99bfacf7caf8aabe76211229a1ba0f94aa6f46f8337cf9ce3712c00c06b073b8 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 14:55:22 +0000 https://status.flyxe.cloud/#3398e58b69b3223df65c6e53e805d6db41386df214c1095754a1cda17f3964b7 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 14:49:17 +0000 https://status.flyxe.cloud/#3398e58b69b3223df65c6e53e805d6db41386df214c1095754a1cda17f3964b7 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 13:46:19 +0000 https://status.flyxe.cloud/#75fd242ecf9dc03671f5c589a20019661cd0bf9705bd4fcd8910426dd274656f server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 13:40:13 +0000 https://status.flyxe.cloud/#75fd242ecf9dc03671f5c589a20019661cd0bf9705bd4fcd8910426dd274656f server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 10:37:13 +0000 https://status.flyxe.cloud/#efe7da5be77b6a52cbc52a299ab340641bf25b21a6752b4e2359a4d54448c947 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 10:34:15 +0000 https://status.flyxe.cloud/#efe7da5be77b6a52cbc52a299ab340641bf25b21a6752b4e2359a4d54448c947 server #4 (RU) went down flyxe.cloud client area recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 09:54:06 +0000 https://status.flyxe.cloud/#a7ddb0e18606e5309707e528ab12ba3564c512bd287cd6890d305befa9028e8c flyxe.cloud client area recovered flyxe.cloud client area went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 09:46:57 +0000 https://status.flyxe.cloud/#a7ddb0e18606e5309707e528ab12ba3564c512bd287cd6890d305befa9028e8c flyxe.cloud client area went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 04:55:18 +0000 https://status.flyxe.cloud/#592a179a071f476bd634f13501eaf45bcdb9d1407170d25ad9a80a5d4d107048 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 04:52:09 +0000 https://status.flyxe.cloud/#592a179a071f476bd634f13501eaf45bcdb9d1407170d25ad9a80a5d4d107048 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Sat, 31 Jan 2026 03:31:18 +0000 https://status.flyxe.cloud/#cb0336cb5c4b37100ab5ec356d877d26fdc194a3219e363137d98ec27ec46bfa server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Sat, 31 Jan 2026 03:28:10 +0000 https://status.flyxe.cloud/#cb0336cb5c4b37100ab5ec356d877d26fdc194a3219e363137d98ec27ec46bfa server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 20:22:16 +0000 https://status.flyxe.cloud/#3b75ef304e153b14630d9661669af389475f3a8bf595e3711f881395d6a9e1d5 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 20:19:16 +0000 https://status.flyxe.cloud/#3b75ef304e153b14630d9661669af389475f3a8bf595e3711f881395d6a9e1d5 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 19:01:12 +0000 https://status.flyxe.cloud/#c514ae807fc2c6fc176c0015fb32aa002f2c7ffa3d7fc295cdb0a02f0ebd88d7 server #4 (RU) recovered server #3 (DE) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 18:53:19 +0000 https://status.flyxe.cloud/#0371f4a0f1c9f36247118e0d34357eb0a28f61882d8485b7de2f317a807cb64c server #3 (DE) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 18:52:11 +0000 https://status.flyxe.cloud/#c514ae807fc2c6fc176c0015fb32aa002f2c7ffa3d7fc295cdb0a02f0ebd88d7 server #4 (RU) went down server #3 (DE) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 18:21:35 +0000 https://status.flyxe.cloud/#0371f4a0f1c9f36247118e0d34357eb0a28f61882d8485b7de2f317a807cb64c server #3 (DE) went down server #3 (DE) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 15:32:25 +0000 https://status.flyxe.cloud/#51e5b432e4668e96c03c88218d9b943aa5767da4a08f1b9317413beab3bc10ec server #3 (DE) recovered server #3 (DE) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 15:21:17 +0000 https://status.flyxe.cloud/#51e5b432e4668e96c03c88218d9b943aa5767da4a08f1b9317413beab3bc10ec server #3 (DE) went down server #3 (DE) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 15:09:18 +0000 https://status.flyxe.cloud/#eeb48d81c87393589dd1a9bfb0d5f175b9c88f1605d57ca7285f3064f7b103b8 server #3 (DE) recovered server #3 (DE) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 15:00:35 +0000 https://status.flyxe.cloud/#eeb48d81c87393589dd1a9bfb0d5f175b9c88f1605d57ca7285f3064f7b103b8 server #3 (DE) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 11:17:31 +0000 https://status.flyxe.cloud/#8d763195feb1dd41bcc4010e2473daa8a2cb08bbe899d2f484e882097ab928a9 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 11:13:12 +0000 https://status.flyxe.cloud/#8d763195feb1dd41bcc4010e2473daa8a2cb08bbe899d2f484e882097ab928a9 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 09:34:13 +0000 https://status.flyxe.cloud/#a17d6d399c0bca4832091808341bcc7e56919e33b830e06aafc5625194e1dba5 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 09:28:29 +0000 https://status.flyxe.cloud/#a17d6d399c0bca4832091808341bcc7e56919e33b830e06aafc5625194e1dba5 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Fri, 30 Jan 2026 02:46:17 +0000 https://status.flyxe.cloud/#e3df83dbdd417117c214405ab454786ab422e9d2c735cf3b5bb7a8dbb1ddd725 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Fri, 30 Jan 2026 02:43:24 +0000 https://status.flyxe.cloud/#e3df83dbdd417117c214405ab454786ab422e9d2c735cf3b5bb7a8dbb1ddd725 server #4 (RU) went down server #4 (RU) recovered https://status.flyxe.cloud/ Tue, 27 Jan 2026 20:40:29 +0000 https://status.flyxe.cloud/#11268df5ef33c4fdcb849bcf57d02a666523a77761e47edd4c01c084f6d330a3 server #4 (RU) recovered server #4 (RU) went down https://status.flyxe.cloud/ Tue, 27 Jan 2026 20:37:13 +0000 https://status.flyxe.cloud/#11268df5ef33c4fdcb849bcf57d02a666523a77761e47edd4c01c084f6d330a3 server #4 (RU) went down плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:38:36 -0000 https://status.flyxe.cloud/incident/787042#08bdbe9baa8e3d5f94a28e7ef08fedacc4325dc761a7717f503f845405a63715 Maintenance completed плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:38:36 -0000 https://status.flyxe.cloud/incident/787042#08bdbe9baa8e3d5f94a28e7ef08fedacc4325dc761a7717f503f845405a63715 Maintenance completed плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:38:36 -0000 https://status.flyxe.cloud/incident/787042#08bdbe9baa8e3d5f94a28e7ef08fedacc4325dc761a7717f503f845405a63715 Maintenance completed плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:38:36 -0000 https://status.flyxe.cloud/incident/787042#08bdbe9baa8e3d5f94a28e7ef08fedacc4325dc761a7717f503f845405a63715 Maintenance completed плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:38:36 -0000 https://status.flyxe.cloud/incident/787042#08bdbe9baa8e3d5f94a28e7ef08fedacc4325dc761a7717f503f845405a63715 Maintenance completed плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:38:36 -0000 https://status.flyxe.cloud/incident/787042#08bdbe9baa8e3d5f94a28e7ef08fedacc4325dc761a7717f503f845405a63715 Maintenance completed плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. плановое техническое обслуживание https://status.flyxe.cloud/incident/787042 Mon, 15 Dec 2025 20:00:50 -0000 https://status.flyxe.cloud/incident/787042#ddbcd0adcb189071e597e1c2d11fad83e478bad64e9e0e3d8795a69be8f0d246 в ночь с 15 декабря 2025 года на 16 декабря 2025 года будет проведено плановое техническое обслуживание и проверка всех наших серверов. возможны временные перебои при использовании наших сервисов веб-хостинга, размещения баз данных, а также CDN-хранилища. сервисы DDoS-защиты flyxe.cloud DDoS-Protection и датацентр в Восточной Европе будут работать без перебоев. сбой сети на сервере #2 https://status.flyxe.cloud/incident/787038 Mon, 15 Dec 2025 19:47:00 -0000 https://status.flyxe.cloud/incident/787038#73bba0012812b833bd9e917cad0c6a7d86cd45df40160733d28642c2a47342c9 проблема устранена. доступ к сервисам веб-хостинга возобновлён. просим прощения за предоставленные неудобства. сбой сети на сервере #2 https://status.flyxe.cloud/incident/787038 Mon, 15 Dec 2025 19:36:00 -0000 https://status.flyxe.cloud/incident/787038#c6b3290776567cc914a1e7cc28695b0bc13d3587091cf01d3a0be6764f101051 на сервере общего веб-хостинга (#2, Нидерланды) произошел сбой сети. сервер временно недоступен. мы уже работаем над решением данной проблемы. сбой питания в датацентре https://status.flyxe.cloud/incident/784003 Wed, 10 Dec 2025 21:09:00 -0000 https://status.flyxe.cloud/incident/784003#4bc8741fa4c32ecea78dd7ef70025240e7643cea41f16b0945971bbf7615fa51 проблема устранена. работа всех 32 серверов восстановлена. сбой питания в датацентре https://status.flyxe.cloud/incident/784003 Wed, 10 Dec 2025 20:58:00 -0000 https://status.flyxe.cloud/incident/784003#420a20aa4a9406ba4194b7aab025d9c23edab71668f6ee487d2804458e5c0613 произошел сбой питания в нашем датацентре в Восточной Европе. мы уже работаем над решением данной проблемы. приносим извинения за предоставленные неудобства.