Incidents reported on status page for WAIcore Hosting https://status.waicore.com/ en 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/ Fri, 05 Dec 2025 23:39:10 +0000 https://status.waicore.com/#425e84673a25a404c278eff76310e5087bd34604d516560b7dc468c9af121443 my.waicore.com recovered https://status.waicore.com/ Fri, 05 Dec 2025 23:28:10 +0000 https://status.waicore.com/#425e84673a25a404c278eff76310e5087bd34604d516560b7dc468c9af121443 my.waicore.com went down https://status.waicore.com/ Wed, 03 Dec 2025 01:19:09 +0000 https://status.waicore.com/#ff8bd30c80ef5821ec73b68570b7c36de77c843200bf9214e2bbeb5691177b22 my.waicore.com recovered https://status.waicore.com/ Wed, 03 Dec 2025 01:07:58 +0000 https://status.waicore.com/#ff8bd30c80ef5821ec73b68570b7c36de77c843200bf9214e2bbeb5691177b22 my.waicore.com went down https://status.waicore.com/ Sun, 30 Nov 2025 00:09:00 +0000 https://status.waicore.com/#df997f30078e1b895776e039343bf3041175e6eec60986cb8e6db1e04ac1ba52 waicore.com recovered https://status.waicore.com/ Sun, 30 Nov 2025 00:03:51 +0000 https://status.waicore.com/#df997f30078e1b895776e039343bf3041175e6eec60986cb8e6db1e04ac1ba52 waicore.com went down https://status.waicore.com/ Fri, 21 Nov 2025 10:42:47 +0000 https://status.waicore.com/#3dd11f33cc8a2112b8a40233b853e6d17f80d046c6841390f2b2389e06713545 waicore.com recovered https://status.waicore.com/ Fri, 21 Nov 2025 09:24:48 +0000 https://status.waicore.com/#3dd11f33cc8a2112b8a40233b853e6d17f80d046c6841390f2b2389e06713545 waicore.com went down https://status.waicore.com/ Thu, 06 Nov 2025 13:46:35 +0000 https://status.waicore.com/#60ca7752aa11eef37fffa7da2f0c46b6b36429f3c0a811d657ace50f5835e463 my.waicore.com recovered https://status.waicore.com/ Thu, 06 Nov 2025 13:29:21 +0000 https://status.waicore.com/#60ca7752aa11eef37fffa7da2f0c46b6b36429f3c0a811d657ace50f5835e463 my.waicore.com went down https://status.waicore.com/ Thu, 06 Nov 2025 13:26:35 +0000 https://status.waicore.com/#fa14d5aa7a69ee4ce2bba57ca4042d8b7190835a670e9fbefcc46e3819e4b7f9 my.waicore.com recovered https://status.waicore.com/ Thu, 06 Nov 2025 12:47:04 +0000 https://status.waicore.com/#fa14d5aa7a69ee4ce2bba57ca4042d8b7190835a670e9fbefcc46e3819e4b7f9 my.waicore.com went down https://status.waicore.com/ Tue, 28 Oct 2025 22:40:04 +0000 https://status.waicore.com/#3db54fbd771a4be29bc94c7a2b5c96a4238da43e25ae2440db8fc2182a2b6cfe my.waicore.com recovered https://status.waicore.com/ Tue, 28 Oct 2025 22:19:38 +0000 https://status.waicore.com/#3db54fbd771a4be29bc94c7a2b5c96a4238da43e25ae2440db8fc2182a2b6cfe my.waicore.com went down https://status.waicore.com/ Sun, 26 Oct 2025 18:06:11 +0000 https://status.waicore.com/#5aafe7554576b6d028b159890aa83126783aa70ed272df3f017cebbc698fc147 my.waicore.com recovered https://status.waicore.com/ Sun, 26 Oct 2025 17:31:12 +0000 https://status.waicore.com/#5aafe7554576b6d028b159890aa83126783aa70ed272df3f017cebbc698fc147 my.waicore.com went down https://status.waicore.com/ Sun, 26 Oct 2025 17:18:17 +0000 https://status.waicore.com/#5877fabf37e8a292bca51a03bce67c1e7efc4ac861165894c4a212b9cadcb7b3 my.waicore.com recovered https://status.waicore.com/ Sun, 26 Oct 2025 17:07:11 +0000 https://status.waicore.com/#5877fabf37e8a292bca51a03bce67c1e7efc4ac861165894c4a212b9cadcb7b3 my.waicore.com went down https://status.waicore.com/ Wed, 22 Oct 2025 06:12:35 +0000 https://status.waicore.com/#aabb9f2ae0f35d372247ee0422bbde7041d35175fe6f57019fe12f2c616a6ddd vm.waicore.com recovered https://status.waicore.com/ Wed, 22 Oct 2025 06:12:06 +0000 https://status.waicore.com/#19ece406eaf84db4b256d43199dbefa19609cb171cab96198c6dc7d0f9078049 waicore.com recovered https://status.waicore.com/ Wed, 22 Oct 2025 05:22:10 +0000 https://status.waicore.com/#19ece406eaf84db4b256d43199dbefa19609cb171cab96198c6dc7d0f9078049 waicore.com went down https://status.waicore.com/ Wed, 22 Oct 2025 05:20:26 +0000 https://status.waicore.com/#aabb9f2ae0f35d372247ee0422bbde7041d35175fe6f57019fe12f2c616a6ddd vm.waicore.com went down https://status.waicore.com/ Thu, 16 Oct 2025 18:24:31 +0000 https://status.waicore.com/#bf5d47a673a90876cc71b363a45257d3ff989d548eace17a00f6638e4ed3a245 my.waicore.com recovered https://status.waicore.com/ Thu, 16 Oct 2025 18:10:31 +0000 https://status.waicore.com/#bf5d47a673a90876cc71b363a45257d3ff989d548eace17a00f6638e4ed3a245 my.waicore.com went down https://status.waicore.com/ Tue, 14 Oct 2025 08:02:43 +0000 https://status.waicore.com/#9bf632235ee621a88857b7196510ea344e61b2ca5bf9229589fc700a2c236b1e vm.waicore.com recovered https://status.waicore.com/ Tue, 14 Oct 2025 07:55:19 +0000 https://status.waicore.com/#9bf632235ee621a88857b7196510ea344e61b2ca5bf9229589fc700a2c236b1e vm.waicore.com went down https://status.waicore.com/ Thu, 09 Oct 2025 12:28:22 +0000 https://status.waicore.com/#fdea1ee4ab4cdd2d6338716589e3e59e3fb6f5652d9a9333b9d4b612f2c0e537 waicore.com recovered https://status.waicore.com/ Thu, 09 Oct 2025 12:20:17 +0000 https://status.waicore.com/#fdea1ee4ab4cdd2d6338716589e3e59e3fb6f5652d9a9333b9d4b612f2c0e537 waicore.com went down https://status.waicore.com/ Fri, 03 Oct 2025 18:44:03 +0000 https://status.waicore.com/#5e14374399162f94fb55fb961725099fde6bf71dc147803cb22dfecfcfdfe905 vm.waicore.com recovered https://status.waicore.com/ Fri, 03 Oct 2025 18:35:03 +0000 https://status.waicore.com/#5e14374399162f94fb55fb961725099fde6bf71dc147803cb22dfecfcfdfe905 vm.waicore.com went down https://status.waicore.com/ Mon, 29 Sep 2025 16:59:49 +0000 https://status.waicore.com/#8140dbfa1c4adcf281eaaabe00cf0dc08936d64ace05054656db8b20d82bf518 my.waicore.com recovered https://status.waicore.com/ Mon, 29 Sep 2025 16:27:51 +0000 https://status.waicore.com/#8140dbfa1c4adcf281eaaabe00cf0dc08936d64ace05054656db8b20d82bf518 my.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.