Incidents reported on status page for WAIcore Hosting https://status.waicore.com/ en https://status.waicore.com/ Thu, 26 Feb 2026 11:23:44 +0000 https://status.waicore.com/#9403d89ed19f8ff8a25aed3e2a085dc72e7ff809fbe1ab147a5e29a863962e61 my.waicore.com recovered https://status.waicore.com/ Thu, 26 Feb 2026 11:18:43 +0000 https://status.waicore.com/#5f6fa38b5ce7ab2189870e1963666a78aacd540dee987d5e06fb5b80f0301c4c waicore.com recovered https://status.waicore.com/ Thu, 26 Feb 2026 11:00:13 +0000 https://status.waicore.com/#9403d89ed19f8ff8a25aed3e2a085dc72e7ff809fbe1ab147a5e29a863962e61 my.waicore.com went down https://status.waicore.com/ Thu, 26 Feb 2026 10:53:46 +0000 https://status.waicore.com/#5f6fa38b5ce7ab2189870e1963666a78aacd540dee987d5e06fb5b80f0301c4c waicore.com went down https://status.waicore.com/ Thu, 26 Feb 2026 09:59:42 +0000 https://status.waicore.com/#4cb2a1b415fc242502a2b7fe852097f7695e80d96cc82e434a13e0cca0bcf0fd waicore.com recovered https://status.waicore.com/ Thu, 26 Feb 2026 09:57:11 +0000 https://status.waicore.com/#114fa7cd34ff82ac3e4964c3034859f4ff81ba1e23056b47a24661945296ed44 my.waicore.com recovered https://status.waicore.com/ Thu, 26 Feb 2026 09:51:23 +0000 https://status.waicore.com/#4cb2a1b415fc242502a2b7fe852097f7695e80d96cc82e434a13e0cca0bcf0fd waicore.com went down https://status.waicore.com/ Thu, 26 Feb 2026 09:45:15 +0000 https://status.waicore.com/#114fa7cd34ff82ac3e4964c3034859f4ff81ba1e23056b47a24661945296ed44 my.waicore.com went down https://status.waicore.com/ Wed, 25 Feb 2026 19:23:44 +0000 https://status.waicore.com/#fa88b4908b03ed30f92cd24c145e40a8ed53352916ace4bdc8a09c2277a6a2d0 my.waicore.com recovered https://status.waicore.com/ Wed, 25 Feb 2026 19:18:35 +0000 https://status.waicore.com/#fa88b4908b03ed30f92cd24c145e40a8ed53352916ace4bdc8a09c2277a6a2d0 my.waicore.com went down https://status.waicore.com/ Wed, 25 Feb 2026 18:45:32 +0000 https://status.waicore.com/#8ea31b88707f0b6dbbc00cbff3cb234954b1400b328aaa5b2a884131fe7ee6a9 vm.waicore.com recovered https://status.waicore.com/ Wed, 25 Feb 2026 18:39:53 +0000 https://status.waicore.com/#8ea31b88707f0b6dbbc00cbff3cb234954b1400b328aaa5b2a884131fe7ee6a9 vm.waicore.com went down https://status.waicore.com/ Wed, 18 Feb 2026 19:17:19 +0000 https://status.waicore.com/#9cc521041e1be0724141c5ef71dff314ca6f154e3880ab38ef97058b46fd99cb waicore.com recovered https://status.waicore.com/ Wed, 18 Feb 2026 19:12:15 +0000 https://status.waicore.com/#9cc521041e1be0724141c5ef71dff314ca6f154e3880ab38ef97058b46fd99cb waicore.com went down https://status.waicore.com/ Sat, 14 Feb 2026 21:54:04 +0000 https://status.waicore.com/#542bcdba385745dd78444867bd1cbbac61970029f3a21bff6b126485a1e65ea6 vm.waicore.com recovered https://status.waicore.com/ Sat, 14 Feb 2026 21:53:42 +0000 https://status.waicore.com/#ea16bb179f2778e1e30231832bbf607b18beeebf426283c5699c5e2a557fbf0d my.waicore.com recovered https://status.waicore.com/ Sat, 14 Feb 2026 21:53:21 +0000 https://status.waicore.com/#7a92afef1f1fc3c7bb65573a5db7c55e730688437742f3e4503e2bb3899e50b5 waicore.com recovered https://status.waicore.com/ Sat, 14 Feb 2026 21:33:45 +0000 https://status.waicore.com/#542bcdba385745dd78444867bd1cbbac61970029f3a21bff6b126485a1e65ea6 vm.waicore.com went down https://status.waicore.com/ Sat, 14 Feb 2026 21:30:11 +0000 https://status.waicore.com/#7a92afef1f1fc3c7bb65573a5db7c55e730688437742f3e4503e2bb3899e50b5 waicore.com went down https://status.waicore.com/ Sat, 14 Feb 2026 21:27:36 +0000 https://status.waicore.com/#ea16bb179f2778e1e30231832bbf607b18beeebf426283c5699c5e2a557fbf0d my.waicore.com went down https://status.waicore.com/incident/821421 Sun, 08 Feb 2026 18:42:00 -0000 https://status.waicore.com/incident/821421#2d97376e33a9d194676d5deb30bb0b1ddfcd043a1db912c0fe436e14874d3576 We have returned AuroLogic as the standard exit route after checking that the routes are working properly. https://status.waicore.com/ Sun, 08 Feb 2026 18:33:07 +0000 https://status.waicore.com/#4a14246b297026de28f340be638723d403035022d7523cfb306aa1ae0bafb5a2 vm.waicore.com recovered https://status.waicore.com/ Sun, 08 Feb 2026 18:32:49 +0000 https://status.waicore.com/#771446bd01318a92360b76bfd371039106dcab684a8e6aab74c647f9baf8bcb1 my.waicore.com recovered https://status.waicore.com/ Sun, 08 Feb 2026 18:32:24 +0000 https://status.waicore.com/#9f5a38c110f35e0fa3172dfc1509468c956e846bf5824d5a87127f91f3a4b871 waicore.com recovered https://status.waicore.com/incident/821421 Sun, 08 Feb 2026 18:14:00 -0000 https://status.waicore.com/incident/821421#cc08ee15ab989ab7a4dfc758072aeeb827801a750135e8342d91efac8a67955a After investigating the incident, an automation failure was detected that mistakenly routed traffic for CloudFlare prefixes via filters. The bug and the consequences have been eliminated, and we continue to monitor the situation. https://status.waicore.com/ Sun, 08 Feb 2026 17:54:20 +0000 https://status.waicore.com/#771446bd01318a92360b76bfd371039106dcab684a8e6aab74c647f9baf8bcb1 my.waicore.com went down https://status.waicore.com/incident/821421 Sun, 08 Feb 2026 17:54:00 -0000 https://status.waicore.com/incident/821421#45d5f663405e6d746cf541e225d8afc8573831cf5395b3809379a78a9721bfd2 We took immediate action and used a backup uplink for outgoing traffic, which mitigated the consequences. https://status.waicore.com/ Sun, 08 Feb 2026 17:51:37 +0000 https://status.waicore.com/#4a14246b297026de28f340be638723d403035022d7523cfb306aa1ae0bafb5a2 vm.waicore.com went down https://status.waicore.com/ Sun, 08 Feb 2026 17:51:01 +0000 https://status.waicore.com/#9f5a38c110f35e0fa3172dfc1509468c956e846bf5824d5a87127f91f3a4b871 waicore.com went down https://status.waicore.com/incident/821421 Sun, 08 Feb 2026 17:46:00 -0000 https://status.waicore.com/incident/821421#1c2e6c3ead59027e708548161e232c3e832cac3bde24f6ed4b1b06beb3550434 Incorrect routing was detected via AuroLogic. Outgoing traffic was filtered and then routed through Helsinki. https://status.waicore.com/incident/821425 Sun, 08 Feb 2026 17:40:00 -0000 https://status.waicore.com/incident/821425#742a8c4ff039b73b3028596016e5400ebf25018b2a35da22caf82403d0e8cd09 As a result of monitoring, incorrect operation of the server was detected. At this stage, measures have been taken to mitigate the consequences and prevent future failures. The server will be decommissioned in the coming days for a detailed study of the issue. https://status.waicore.com/incident/821425 Sun, 08 Feb 2026 15:55:00 -0000 https://status.waicore.com/incident/821425#a1e51e0087dfaf5db3dd106ff69aa46aae19c034a7727907956b81d3279196ca As a result of the server failure, some servers of the EP tariff line became unavailable. We are monitoring the situation and making every effort to resolve the issue. https://status.waicore.com/incident/821413 Sun, 08 Feb 2026 14:42:00 -0000 https://status.waicore.com/incident/821413#5525e5c84c6aa285f5cfd4ec1f2311671aca42a95cec3675abf6e04d276f00e6 The incident was completely resolved on the side of our upstream AuroLogic https://status.waicore.com/incident/821413 Sun, 08 Feb 2026 14:04:00 -0000 https://status.waicore.com/incident/821413#69c8e4357f76618e20decc5bf3c67f0c944d949fa9fda6b7e3d3b6a13b0cb077 We have identified a incorrect ingress routing for traffic traversing over Arelion. Due to that, ingress traffic was partially being transported from Arelion over Helsinki, Finland into the Frankfurt network. This caused local congestion in Helsinki on the transport network back to Frankfurt. The bgp-session policy for the export of routes from Frankfurt to Helsinki is currently on reject and we're investigating the cause. The issue arose when we implemented a policy change different from the related interconnection between Frankfurt an Helsinki, relating to the transport network between Digital Realty and Equinix Frankfurt. We're investigating if the issue is related to a potential software bug in Frankfurt and will provide a post-mortem analysis soon. https://status.waicore.com/ Wed, 04 Feb 2026 21:54:09 +0000 https://status.waicore.com/#f161e4a2401e13177267cdb3bd50b602f62eb9ed6dd913d8e125e8ae4f3a872f vm.waicore.com recovered https://status.waicore.com/ Wed, 04 Feb 2026 21:45:01 +0000 https://status.waicore.com/#f161e4a2401e13177267cdb3bd50b602f62eb9ed6dd913d8e125e8ae4f3a872f vm.waicore.com went down https://status.waicore.com/ Wed, 04 Feb 2026 18:56:26 +0000 https://status.waicore.com/#4ab69f26adc955df5eef2acfb3286f8ed4e1c5b1061576275163274592234619 waicore.com recovered https://status.waicore.com/ Wed, 04 Feb 2026 18:47:24 +0000 https://status.waicore.com/#4ab69f26adc955df5eef2acfb3286f8ed4e1c5b1061576275163274592234619 waicore.com went down https://status.waicore.com/ Tue, 03 Feb 2026 10:20:24 +0000 https://status.waicore.com/#947a4c32a2e61780df2ce13ebc3837c5057818339cc85a3603beb09664b3a65b waicore.com recovered https://status.waicore.com/ Tue, 03 Feb 2026 10:18:49 +0000 https://status.waicore.com/#da35a00eda6473a1c7ef2dafaaa9b3da98549b581316dc6c3a733574165114fc vm.waicore.com recovered https://status.waicore.com/ Tue, 03 Feb 2026 09:24:20 +0000 https://status.waicore.com/#947a4c32a2e61780df2ce13ebc3837c5057818339cc85a3603beb09664b3a65b waicore.com went down https://status.waicore.com/ Tue, 03 Feb 2026 09:22:50 +0000 https://status.waicore.com/#da35a00eda6473a1c7ef2dafaaa9b3da98549b581316dc6c3a733574165114fc vm.waicore.com went down https://status.waicore.com/ Sat, 31 Jan 2026 15:14:59 +0000 https://status.waicore.com/#817320fde16f7eb76a525db4bafa49ed3daaa2f112464374a884b42c54155982 vm.waicore.com recovered https://status.waicore.com/ Sat, 31 Jan 2026 15:06:53 +0000 https://status.waicore.com/#817320fde16f7eb76a525db4bafa49ed3daaa2f112464374a884b42c54155982 vm.waicore.com went down https://status.waicore.com/ Sat, 31 Jan 2026 14:47:53 +0000 https://status.waicore.com/#2722a6410c2ccdfbaebf4b862455872ddfa35de33fff6906d74d1f2fd3ad8ba5 vm.waicore.com recovered https://status.waicore.com/ Sat, 31 Jan 2026 14:28:55 +0000 https://status.waicore.com/#2722a6410c2ccdfbaebf4b862455872ddfa35de33fff6906d74d1f2fd3ad8ba5 vm.waicore.com went down https://status.waicore.com/ Wed, 28 Jan 2026 11:23:40 +0000 https://status.waicore.com/#50feeaef1144c09d58676ff8ee49f96195abdd91561a6015b96b213c109034c2 my.waicore.com recovered https://status.waicore.com/ Wed, 28 Jan 2026 11:06:41 +0000 https://status.waicore.com/#50feeaef1144c09d58676ff8ee49f96195abdd91561a6015b96b213c109034c2 my.waicore.com went down https://status.waicore.com/ Wed, 21 Jan 2026 16:11:49 +0000 https://status.waicore.com/#1ef8a27193a2eb453b1b4368f7f6aa92e4d34858d0d59aaadd4011d61c8fc0a7 my.waicore.com recovered https://status.waicore.com/ Wed, 21 Jan 2026 16:06:19 +0000 https://status.waicore.com/#1ef8a27193a2eb453b1b4368f7f6aa92e4d34858d0d59aaadd4011d61c8fc0a7 my.waicore.com went down https://status.waicore.com/ Mon, 19 Jan 2026 10:29:53 +0000 https://status.waicore.com/#18718abf1ef1e4b0079607d8974b2de0c907689a1894d82a450edb5c82ad7d03 my.waicore.com recovered https://status.waicore.com/ Mon, 19 Jan 2026 10:24:39 +0000 https://status.waicore.com/#18718abf1ef1e4b0079607d8974b2de0c907689a1894d82a450edb5c82ad7d03 my.waicore.com went down https://status.waicore.com/ Thu, 15 Jan 2026 23:02:46 +0000 https://status.waicore.com/#bdebf62f6db1ae14d7810d8d10501e5554e7e45b11dfe6e0d74bace26ca074e3 my.waicore.com recovered https://status.waicore.com/ Thu, 15 Jan 2026 22:08:51 +0000 https://status.waicore.com/#bdebf62f6db1ae14d7810d8d10501e5554e7e45b11dfe6e0d74bace26ca074e3 my.waicore.com went down https://status.waicore.com/ Thu, 15 Jan 2026 21:44:44 +0000 https://status.waicore.com/#3bc62b88f0596996713cd7e662cf4527939be722c22595e3c80cfe2591858417 my.waicore.com recovered https://status.waicore.com/ Thu, 15 Jan 2026 21:12:42 +0000 https://status.waicore.com/#3bc62b88f0596996713cd7e662cf4527939be722c22595e3c80cfe2591858417 my.waicore.com went down https://status.waicore.com/ Mon, 12 Jan 2026 15:02:40 +0000 https://status.waicore.com/#2a9c4dbd3def8352adbb6407fcf2c36ee787442e54822005ebf0ab516e469748 my.waicore.com recovered https://status.waicore.com/ Mon, 12 Jan 2026 14:51:59 +0000 https://status.waicore.com/#2a9c4dbd3def8352adbb6407fcf2c36ee787442e54822005ebf0ab516e469748 my.waicore.com went down https://status.waicore.com/ Mon, 12 Jan 2026 13:14:49 +0000 https://status.waicore.com/#76f18a622f03372d7df31169ec8cfedb4b7e8d1c59e0c793184636a15af49646 my.waicore.com recovered https://status.waicore.com/ Mon, 12 Jan 2026 13:06:45 +0000 https://status.waicore.com/#76f18a622f03372d7df31169ec8cfedb4b7e8d1c59e0c793184636a15af49646 my.waicore.com went down https://status.waicore.com/ Mon, 12 Jan 2026 12:35:40 +0000 https://status.waicore.com/#9bd99afba9e8e34cf261185dfc3942c3d0bd5e4c140fc11e4d4da0b6a05c7d03 my.waicore.com recovered https://status.waicore.com/ Mon, 12 Jan 2026 12:21:42 +0000 https://status.waicore.com/#9bd99afba9e8e34cf261185dfc3942c3d0bd5e4c140fc11e4d4da0b6a05c7d03 my.waicore.com went down https://status.waicore.com/ Mon, 12 Jan 2026 12:11:49 +0000 https://status.waicore.com/#44dba76f03d7ecf36797f97d985a4c399597873dfd6c4a205ca07e38bf80fab6 my.waicore.com recovered https://status.waicore.com/ Mon, 12 Jan 2026 12:03:56 +0000 https://status.waicore.com/#44dba76f03d7ecf36797f97d985a4c399597873dfd6c4a205ca07e38bf80fab6 my.waicore.com went down https://status.waicore.com/ Sun, 11 Jan 2026 04:11:46 +0000 https://status.waicore.com/#56a1f95c2ad825201dfef4f913c62a0e0e8975bcf5a58ab8905ee79057df1912 my.waicore.com recovered https://status.waicore.com/ Sun, 11 Jan 2026 04:03:48 +0000 https://status.waicore.com/#56a1f95c2ad825201dfef4f913c62a0e0e8975bcf5a58ab8905ee79057df1912 my.waicore.com went down https://status.waicore.com/ Thu, 01 Jan 2026 15:24:00 +0000 https://status.waicore.com/#2dfe894a3724292a585976670879752b226ab294bb3c1cfae097e56daf615849 vm.waicore.com recovered https://status.waicore.com/ Thu, 01 Jan 2026 15:14:54 +0000 https://status.waicore.com/#2dfe894a3724292a585976670879752b226ab294bb3c1cfae097e56daf615849 vm.waicore.com went down https://status.waicore.com/ Thu, 01 Jan 2026 07:59:42 +0000 https://status.waicore.com/#1415ee164f9a465c2c0d6624e6957703872431e9a206babfb74ec9c106b56d1e my.waicore.com recovered https://status.waicore.com/ Thu, 01 Jan 2026 07:54:21 +0000 https://status.waicore.com/#1415ee164f9a465c2c0d6624e6957703872431e9a206babfb74ec9c106b56d1e my.waicore.com went down https://status.waicore.com/ Thu, 01 Jan 2026 06:56:44 +0000 https://status.waicore.com/#27f643c46799f4f359e573abdf0009bbbe1253bffcbce68859842114b1cafb70 my.waicore.com recovered https://status.waicore.com/ Thu, 01 Jan 2026 06:51:30 +0000 https://status.waicore.com/#27f643c46799f4f359e573abdf0009bbbe1253bffcbce68859842114b1cafb70 my.waicore.com went down https://status.waicore.com/ Thu, 01 Jan 2026 06:39:13 +0000 https://status.waicore.com/#390d99d2e034ec10d8b28ec6c6fdc244db50211030b7656ec407391c0ec74e5f vm.waicore.com recovered https://status.waicore.com/ Thu, 01 Jan 2026 06:38:58 +0000 https://status.waicore.com/#0ad17693baad84019e059253d1559e06d214d53a89472d5e4583f6ed013d6df1 my.waicore.com recovered https://status.waicore.com/ Thu, 01 Jan 2026 06:31:58 +0000 https://status.waicore.com/#390d99d2e034ec10d8b28ec6c6fdc244db50211030b7656ec407391c0ec74e5f vm.waicore.com went down https://status.waicore.com/ Thu, 01 Jan 2026 06:30:24 +0000 https://status.waicore.com/#0ad17693baad84019e059253d1559e06d214d53a89472d5e4583f6ed013d6df1 my.waicore.com went down https://status.waicore.com/ Thu, 01 Jan 2026 00:35:42 +0000 https://status.waicore.com/#d5d9be8db64672ac480cbd43bcb98cc6f314212fbce7c6100075ce90b80e97dd my.waicore.com recovered https://status.waicore.com/ Thu, 01 Jan 2026 00:30:24 +0000 https://status.waicore.com/#d5d9be8db64672ac480cbd43bcb98cc6f314212fbce7c6100075ce90b80e97dd my.waicore.com went down https://status.waicore.com/ Wed, 31 Dec 2025 22:12:04 +0000 https://status.waicore.com/#ca3158ec7d3a6e70ea09bbf7d6c7a69fef4c0f66fa3fef0636446728d7124461 vm.waicore.com recovered https://status.waicore.com/ Wed, 31 Dec 2025 22:04:55 +0000 https://status.waicore.com/#ca3158ec7d3a6e70ea09bbf7d6c7a69fef4c0f66fa3fef0636446728d7124461 vm.waicore.com went down https://status.waicore.com/ Wed, 31 Dec 2025 21:53:46 +0000 https://status.waicore.com/#ec97a710a1721a61f6374c9aa277e433ca7b0efdd48016b75a1bf375d1477356 my.waicore.com recovered https://status.waicore.com/ Wed, 31 Dec 2025 21:48:00 +0000 https://status.waicore.com/#ec97a710a1721a61f6374c9aa277e433ca7b0efdd48016b75a1bf375d1477356 my.waicore.com went down https://status.waicore.com/ Mon, 22 Dec 2025 11:14:23 +0000 https://status.waicore.com/#7bf5239567b395a67c7cfb9494a75227e21a5992870e300c5b8b2ea9e73b7c5c waicore.com recovered https://status.waicore.com/ Mon, 22 Dec 2025 10:42:29 +0000 https://status.waicore.com/#a23bc217ac8af4ce9ec9a8b4bd8a4f32fa0b436493100ebc4429e20265047ee8 vm.waicore.com recovered https://status.waicore.com/ Mon, 22 Dec 2025 10:31:53 +0000 https://status.waicore.com/#a23bc217ac8af4ce9ec9a8b4bd8a4f32fa0b436493100ebc4429e20265047ee8 vm.waicore.com went down https://status.waicore.com/ Mon, 22 Dec 2025 10:30:24 +0000 https://status.waicore.com/#7bf5239567b395a67c7cfb9494a75227e21a5992870e300c5b8b2ea9e73b7c5c waicore.com went down https://status.waicore.com/ Thu, 11 Dec 2025 09:35:30 +0000 https://status.waicore.com/#481814fafe618c5e887682b6e03490de77b0ef2e6abe421ffd5017eabdb2f8cc waicore.com recovered https://status.waicore.com/ Thu, 11 Dec 2025 09:18:03 +0000 https://status.waicore.com/#76b3569ea95bb10d41feeb75df37da230c80bbe73f11af82c20770c4e1864629 vm.waicore.com recovered https://status.waicore.com/ Thu, 11 Dec 2025 08:10:47 +0000 https://status.waicore.com/#76b3569ea95bb10d41feeb75df37da230c80bbe73f11af82c20770c4e1864629 vm.waicore.com went down https://status.waicore.com/ Thu, 11 Dec 2025 08:09:18 +0000 https://status.waicore.com/#481814fafe618c5e887682b6e03490de77b0ef2e6abe421ffd5017eabdb2f8cc waicore.com went down https://status.waicore.com/ Tue, 09 Dec 2025 07:23:32 +0000 https://status.waicore.com/#81a939cbcad80cbce80b155ceaf338924422f8fba602f570f57f8ae5c0eb1ad2 waicore.com recovered https://status.waicore.com/ Tue, 09 Dec 2025 07:17:42 +0000 https://status.waicore.com/#81a939cbcad80cbce80b155ceaf338924422f8fba602f570f57f8ae5c0eb1ad2 waicore.com went down https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:18:00 -0000 https://status.waicore.com/incident/688133#34b45afb7f0308af8b2f4238637dca50b3e4dcaa79d336f658b4b61746ef066a As of 03:18 (UTC+3), all services have been fully restored and traffic flows have normalized. The network is operating nominally, with elevated monitoring in place. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/688133 Sat, 02 Aug 2025 00:13:00 -0000 https://status.waicore.com/incident/688133#b0a7104207b2c263cbccb76e7e739119c8e12df6ab3e1c6d9b6d316e5a37c6e5 Summary: During a scheduled upgrade of the network infrastructure and the activation of the second network core, an unexpected routing flap occurred on the external edge. This led to a brief traffic degradation and partial inaccessibility across several destinations. Root Cause: While integrating changes into the core, one of the upstream providers began announcing incomplete or unstable routes, which introduced inconsistency into the global routing table. The faulty upstream provider was immediately disabled and will remain offline until we receive a formal explanation and confirmation of routing stability on their end. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 14:45:00 -0000 https://status.waicore.com/incident/599475#17a364b382e44d653be9300a631c3fe318d45ad0ea4ea394d0345f11a500be9a The software update helped to rectify the situation and at the moment the load on the software part has been reduced to a minimum. However, we are still considering replacing the Juniper stack with another one in the near future. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 14:45:00 -0000 https://status.waicore.com/incident/599475#17a364b382e44d653be9300a631c3fe318d45ad0ea4ea394d0345f11a500be9a The software update helped to rectify the situation and at the moment the load on the software part has been reduced to a minimum. However, we are still considering replacing the Juniper stack with another one in the near future. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 14:45:00 -0000 https://status.waicore.com/incident/599475#17a364b382e44d653be9300a631c3fe318d45ad0ea4ea394d0345f11a500be9a The software update helped to rectify the situation and at the moment the load on the software part has been reduced to a minimum. However, we are still considering replacing the Juniper stack with another one in the near future. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 14:45:00 -0000 https://status.waicore.com/incident/599475#17a364b382e44d653be9300a631c3fe318d45ad0ea4ea394d0345f11a500be9a The software update helped to rectify the situation and at the moment the load on the software part has been reduced to a minimum. However, we are still considering replacing the Juniper stack with another one in the near future. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 14:45:00 -0000 https://status.waicore.com/incident/599475#17a364b382e44d653be9300a631c3fe318d45ad0ea4ea394d0345f11a500be9a The software update helped to rectify the situation and at the moment the load on the software part has been reduced to a minimum. However, we are still considering replacing the Juniper stack with another one in the near future. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 12:27:00 -0000 https://status.waicore.com/incident/599475#f2f34b1d772870eda60eed3b5cd16a9ed68feb32e8f26bb7eef9f98b24631e63 We experienced a disruption due to a failure in a Juniper core switch, which was further exacerbated by a DDoS attack. The device stopped responding to requests due to a software-level issue. A reboot has been initiated to restore service. We are actively monitoring the situation. A long-term resolution is planned — we are in the process of replacing the current Juniper stack. This transition will take some time. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 12:27:00 -0000 https://status.waicore.com/incident/599475#f2f34b1d772870eda60eed3b5cd16a9ed68feb32e8f26bb7eef9f98b24631e63 We experienced a disruption due to a failure in a Juniper core switch, which was further exacerbated by a DDoS attack. The device stopped responding to requests due to a software-level issue. A reboot has been initiated to restore service. We are actively monitoring the situation. A long-term resolution is planned — we are in the process of replacing the current Juniper stack. This transition will take some time. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 12:27:00 -0000 https://status.waicore.com/incident/599475#f2f34b1d772870eda60eed3b5cd16a9ed68feb32e8f26bb7eef9f98b24631e63 We experienced a disruption due to a failure in a Juniper core switch, which was further exacerbated by a DDoS attack. The device stopped responding to requests due to a software-level issue. A reboot has been initiated to restore service. We are actively monitoring the situation. A long-term resolution is planned — we are in the process of replacing the current Juniper stack. This transition will take some time. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 12:27:00 -0000 https://status.waicore.com/incident/599475#f2f34b1d772870eda60eed3b5cd16a9ed68feb32e8f26bb7eef9f98b24631e63 We experienced a disruption due to a failure in a Juniper core switch, which was further exacerbated by a DDoS attack. The device stopped responding to requests due to a software-level issue. A reboot has been initiated to restore service. We are actively monitoring the situation. A long-term resolution is planned — we are in the process of replacing the current Juniper stack. This transition will take some time. https://status.waicore.com/incident/599475 Mon, 09 Jun 2025 12:27:00 -0000 https://status.waicore.com/incident/599475#f2f34b1d772870eda60eed3b5cd16a9ed68feb32e8f26bb7eef9f98b24631e63 We experienced a disruption due to a failure in a Juniper core switch, which was further exacerbated by a DDoS attack. The device stopped responding to requests due to a software-level issue. A reboot has been initiated to restore service. We are actively monitoring the situation. A long-term resolution is planned — we are in the process of replacing the current Juniper stack. This transition will take some time. https://status.waicore.com/incident/597733 Thu, 05 Jun 2025 21:57:00 -0000 https://status.waicore.com/incident/597733#38c8a12797fd50fdb5ffcef27cd6146468b46512f36f30652dcd0fb1120890b9 After a more thorough inspection, our engineer identified a faulty motherboard. It has been replaced, and the server is currently active — no recurrence is expected. The faulty motherboard will be sent to the vendor for further analysis to help prevent similar incidents in the future. https://status.waicore.com/incident/597733 Thu, 05 Jun 2025 19:50:00 -0000 https://status.waicore.com/incident/597733#92e36fbbff98c85759419e9da46c673d7e7c2d3ab584407a4ce19cc8c7a98194 Engineer is on his way to the data center to review the situation in more detail on the spot. We will share additional information as soon as we receive a response from him. Thank you for supporting us! https://status.waicore.com/incident/597733 Thu, 05 Jun 2025 18:58:00 -0000 https://status.waicore.com/incident/597733#6e04fe2d765d32d1aeb12c584047f25f530655763e4dc68fb037d05fc75aee91 We're currently experiencing an issue affecting one node in the RX-Line cluster (Ryzen 9 9950X). Our engineering team is aware of the problem and is actively investigating the root cause. We'll provide updates as soon as more information becomes available. Thank you for your patience. https://status.waicore.com/incident/570380 Sun, 18 May 2025 21:05:00 -0000 https://status.waicore.com/incident/570380#0f9495ea602de0868bcfef4e7691c9460afa63f355fa6aba56cd8b0471a066ba Our monitoring systems recorded a sharp increase in the w_await indicator on some servers of the RX cluster. This indicator reflects the response time of NVMe drives during write operations. Since we use RAID1 on our servers to increase the reliability of data storage, its speed depends on the "slowest disk" itself. If at least one disk from the array starts working incorrectly, this is reflected in the entire array. During an internal investigation, we found that all the problematic drives belong to a single batch, which was received by an engineer at the data center and assembled the servers. We have ordered a new batch and expect it to be delivered next week. No downtime is expected during the work on replacing storage devices, and virtual machines from these nodes will be migrated to other servers in order to service emergency nodes. We continue to monitor the situation and apologize for any inconvenience. https://status.waicore.com/incident/555556 Sat, 03 May 2025 16:03:00 -0000 https://status.waicore.com/incident/555556#aa261f0f2d521c6318cfe1058bef773ba64a6abea6a6b257dde052234f1f3e31 Since we did not receive a clear response from CloudFlare, what exactly is the reason for this incident, we decided to replace the IP addresses with others. The replacement was successful, this subnet has been decommissioned, and customers have no problems working with the CloudFlare network. https://status.waicore.com/incident/555556 Fri, 02 May 2025 16:00:00 -0000 https://status.waicore.com/incident/555556#54f2927f844733079e1937b8efd28a4d05658b51528a3d592c7f7c4d76191a0e On one of our subnets - 176.98.191.0/24 - seeing a loss of connectivity with the CloudFlare network. This does not affect the availability of other resources, but the fact that CloudFlare controls a very significant amount of worldwide Internet traffic can have a negative impact on daily use. We have contacted the CloudFlare peering team to clarify the situation and fix it as soon as possible. https://status.waicore.com/incident/554300 Wed, 30 Apr 2025 09:05:00 -0000 https://status.waicore.com/incident/554300#f1e61433343d604cf805cb006f2a57921f6f50d3691e7b4a5d4a07d554c64d6a The issue affecting system performance due to a bug in the BillManager software has been resolved. The abnormal CPU usage has returned to normal levels, and service response times have stabilized. We continue to monitor the situation closely. The root cause has been identified as a microcode bug in BillManager, and the incident is under further analysis by ISPsystem. No further impact is expected at this time. We apologize for the inconvenience caused and thank you for your understanding. https://status.waicore.com/incident/554300 Tue, 29 Apr 2025 23:39:00 -0000 https://status.waicore.com/incident/554300#09d7a151aff864636c13193a408ba1dffb354789a9e205048b165397ff74eebe We are currently experiencing degraded performance across our platform due to an issue in the BillManager software provided by ISPsystem. A bug in the application’s microcode is causing abnormally high CPU usage (up to 100%) in our cloud infrastructure. As a result, user requests are being processed with significant delays (20–30 seconds). Our team is actively investigating the issue and working with the vendor to resolve it. We will provide further updates as soon as more information becomes available. Thank you for your patience. https://status.waicore.com/incident/552717 Mon, 28 Apr 2025 09:52:00 -0000 https://status.waicore.com/incident/552717#f93bf7d74ed7238e7d402abcb8fb25bda1642a454007c99bd812f7a9f1bc6f6f At the moment, the incident has been resolved, no repeats are expected. https://status.waicore.com/incident/552717 Mon, 28 Apr 2025 09:52:00 -0000 https://status.waicore.com/incident/552717#f93bf7d74ed7238e7d402abcb8fb25bda1642a454007c99bd812f7a9f1bc6f6f At the moment, the incident has been resolved, no repeats are expected. https://status.waicore.com/incident/552717 Mon, 28 Apr 2025 06:35:00 -0000 https://status.waicore.com/incident/552717#10ed28a994000fdd360c223847df40a0f552201573e2c96ffd7672652ff11444 StormWall made a new one when trying to fix an incident. Many users also received an error when trying to query. https://status.waicore.com/incident/552717 Mon, 28 Apr 2025 06:35:00 -0000 https://status.waicore.com/incident/552717#10ed28a994000fdd360c223847df40a0f552201573e2c96ffd7672652ff11444 StormWall made a new one when trying to fix an incident. Many users also received an error when trying to query. https://status.waicore.com/incident/552717 Sun, 27 Apr 2025 20:15:00 -0000 https://status.waicore.com/incident/552717#4e63171dfc047ed434a7926aef0aa432ce5e8fbf385ca2048c8fb0ebc02550ed Protection mode has been switched, and access to the website and billing has been restored. Awaiting further comments from StormWall. https://status.waicore.com/incident/552717 Sun, 27 Apr 2025 20:15:00 -0000 https://status.waicore.com/incident/552717#4e63171dfc047ed434a7926aef0aa432ce5e8fbf385ca2048c8fb0ebc02550ed Protection mode has been switched, and access to the website and billing has been restored. Awaiting further comments from StormWall. https://status.waicore.com/incident/552717 Sun, 27 Apr 2025 20:00:00 -0000 https://status.waicore.com/incident/552717#f5872f1ef72026c4d4703e666a86a4152da940b6479c48fba3365d27e6109230 Some requests to the website and billing system may return 405 Not Allowed errors due to a problem with our web protection provider. StormWall has been contacted, and resolution is in progress. Updates will follow. Thank you for your patience! https://status.waicore.com/incident/552717 Sun, 27 Apr 2025 20:00:00 -0000 https://status.waicore.com/incident/552717#f5872f1ef72026c4d4703e666a86a4152da940b6479c48fba3365d27e6109230 Some requests to the website and billing system may return 405 Not Allowed errors due to a problem with our web protection provider. StormWall has been contacted, and resolution is in progress. Updates will follow. Thank you for your patience! https://status.waicore.com/incident/552316 Sat, 26 Apr 2025 23:54:13 -0000 https://status.waicore.com/incident/552316#94a53f521cefe75f652c4905a0c9c49d263ecee3dc9936d84d6b583a2ce0dfa8 Maintenance completed https://status.waicore.com/incident/552316 Sat, 26 Apr 2025 23:00:00 -0000 https://status.waicore.com/incident/552316#b49087021c339324e91d5fd373577fcbdfbdab9f6b52dbd9923ef0d445e48ef1 We have scheduled technical work to connect an additional GlobalNet routing path, specifically limited to routes within the Russian Federation, in order to enhance connectivity and network performance within the region. https://status.waicore.com/incident/552316 Sat, 26 Apr 2025 23:00:00 -0000 https://status.waicore.com/incident/552316#b49087021c339324e91d5fd373577fcbdfbdab9f6b52dbd9923ef0d445e48ef1 We have scheduled technical work to connect an additional GlobalNet routing path, specifically limited to routes within the Russian Federation, in order to enhance connectivity and network performance within the region.