Incidents reported on status page for Nasulex Networks https://status.nasulex.net/ https://d1lppblt9t2x15.cloudfront.net/logos/c6ab18bba804a5265d914e239de0e7c5.png https://status.nasulex.net/ en https://status.nasulex.net/incident/606545 Wed, 25 Jun 2025 10:00:32 +0000 https://status.nasulex.net/incident/606545#68c14ed4f096e5a6fed6df1983344963711c8937865b6cd849ead4386e636a3a Maintenance completed https://status.nasulex.net/ Wed, 25 Jun 2025 08:11:22 +0000 https://status.nasulex.net/#87819fe3d7449a5d00929d9298a43c58213f6c8aa03cd12a870ef43bd467bafe Chicago AMD Epyc VPS hosting recovered https://status.nasulex.net/ Wed, 25 Jun 2025 08:02:24 +0000 https://status.nasulex.net/#87819fe3d7449a5d00929d9298a43c58213f6c8aa03cd12a870ef43bd467bafe Chicago AMD Epyc VPS hosting went down https://status.nasulex.net/ Wed, 25 Jun 2025 07:14:24 +0000 https://status.nasulex.net/#79f66ea625792a07989996fb15c7ca25727aca921cf04bfa724595280f42591e Chicago AMD Epyc VPS hosting recovered https://status.nasulex.net/ Wed, 25 Jun 2025 07:08:38 +0000 https://status.nasulex.net/#79f66ea625792a07989996fb15c7ca25727aca921cf04bfa724595280f42591e Chicago AMD Epyc VPS hosting went down https://status.nasulex.net/incident/606545 Wed, 25 Jun 2025 07:00:16 -0000 https://status.nasulex.net/incident/606545#b68af9eba96da97c894d6d4088fc9e7909df5d73236a3c2796ea685bf688865a GTT is performing maintenance in Chicago which may result in disruptions. https://status.nasulex.net/incident/603671 Wed, 18 Jun 2025 02:00:00 +0000 https://status.nasulex.net/incident/603671#d7de8a3b2a53d67faaf8bbddb5f44199f2401c17153e44626f6261aebb23d3f4 Maintenance completed https://status.nasulex.net/incident/603671 Tue, 17 Jun 2025 21:00:30 -0000 https://status.nasulex.net/incident/603671#2bec24fb131f2257af49cf1c30c9fac1bad0343c4088518ae5206c20fd3def89 An upstream provider is performing maintenance on their routers in London and you may notice elevated latency and have intermittent drops during the duration. https://status.nasulex.net/incident/597112 Wed, 11 Jun 2025 06:00:43 +0000 https://status.nasulex.net/incident/597112#dbd181d20699cc4c9f1111a67f77624c0a0301bf4341a54cc8d6785880dbef68 Maintenance completed https://status.nasulex.net/ Wed, 11 Jun 2025 04:54:31 +0000 https://status.nasulex.net/#9888b3593bab001cae7ca993f49167ecb441f8ca243d04ed0f5494ba6fab3fd9 NYC Ryzen VPS hosting recovered https://status.nasulex.net/ Wed, 11 Jun 2025 04:42:40 +0000 https://status.nasulex.net/#9888b3593bab001cae7ca993f49167ecb441f8ca243d04ed0f5494ba6fab3fd9 NYC Ryzen VPS hosting went down https://status.nasulex.net/incident/597112 Wed, 11 Jun 2025 04:00:43 -0000 https://status.nasulex.net/incident/597112#6b9b2cdb6016fb8771307a652022965bc91538426eb43935fdb1f866d512539d "The router software will be upgraded to fix a known firmware bug that can potentially cause unplanned downtime. During this time, there will be multiple reboot events, lasting up to an estimated 15 minutes each, causing network inaccessibility." https://status.nasulex.net/ Mon, 09 Jun 2025 10:11:26 +0000 https://status.nasulex.net/#f33a7cdd2fd360108dc1a2f963874be7dea4f9df91a384f8c7355e8a3312d026 London Ryzen Node recovered https://status.nasulex.net/ Mon, 09 Jun 2025 08:02:48 +0000 https://status.nasulex.net/#f33a7cdd2fd360108dc1a2f963874be7dea4f9df91a384f8c7355e8a3312d026 London Ryzen Node went down https://status.nasulex.net/ Mon, 09 Jun 2025 01:26:27 +0000 https://status.nasulex.net/#5bbd0265aceddeaaf1fa385c03601217294ce879fd7914646f614d033b3db468 London Ryzen Node recovered https://status.nasulex.net/ Mon, 09 Jun 2025 01:23:48 +0000 https://status.nasulex.net/#5bbd0265aceddeaaf1fa385c03601217294ce879fd7914646f614d033b3db468 London Ryzen Node went down https://status.nasulex.net/incident/372112 Thu, 23 May 2024 20:00:00 +0000 https://status.nasulex.net/incident/372112#ecc8c380c82b3e8addacbee7dc1a4407de748fb67887fa153970031b2ecbecc0 Maintenance completed https://status.nasulex.net/incident/372112 Thu, 23 May 2024 20:00:00 +0000 https://status.nasulex.net/incident/372112#ecc8c380c82b3e8addacbee7dc1a4407de748fb67887fa153970031b2ecbecc0 Maintenance completed https://status.nasulex.net/incident/372112 Thu, 23 May 2024 20:00:00 +0000 https://status.nasulex.net/incident/372112#ecc8c380c82b3e8addacbee7dc1a4407de748fb67887fa153970031b2ecbecc0 Maintenance completed https://status.nasulex.net/incident/372112 Thu, 23 May 2024 20:00:00 +0000 https://status.nasulex.net/incident/372112#ecc8c380c82b3e8addacbee7dc1a4407de748fb67887fa153970031b2ecbecc0 Maintenance completed https://status.nasulex.net/incident/372112 Thu, 23 May 2024 16:00:00 -0000 https://status.nasulex.net/incident/372112#70073f26f2ac282d30fb31c9b743fb7ab18f2ea1e2fae3f0dc56287b3caf8e5e Our upstream provider where the server is located is performing maintenance on core network infrastructure. https://status.nasulex.net/incident/372112 Thu, 23 May 2024 16:00:00 -0000 https://status.nasulex.net/incident/372112#70073f26f2ac282d30fb31c9b743fb7ab18f2ea1e2fae3f0dc56287b3caf8e5e Our upstream provider where the server is located is performing maintenance on core network infrastructure. https://status.nasulex.net/incident/372112 Thu, 23 May 2024 16:00:00 -0000 https://status.nasulex.net/incident/372112#70073f26f2ac282d30fb31c9b743fb7ab18f2ea1e2fae3f0dc56287b3caf8e5e Our upstream provider where the server is located is performing maintenance on core network infrastructure. https://status.nasulex.net/incident/372112 Thu, 23 May 2024 16:00:00 -0000 https://status.nasulex.net/incident/372112#70073f26f2ac282d30fb31c9b743fb7ab18f2ea1e2fae3f0dc56287b3caf8e5e Our upstream provider where the server is located is performing maintenance on core network infrastructure. https://status.nasulex.net/incident/340299 Wed, 13 Mar 2024 12:09:00 -0000 https://status.nasulex.net/incident/340299#b0802192f3334670cc4ad78a4882fc73abe51b4626c4055d4724bfd0120a5f37 This morning DECIX NYC went offline and affected connectivity between the mitigation provider and the machine https://status.nasulex.net/incident/332627 Tue, 27 Feb 2024 08:00:00 -0000 https://status.nasulex.net/incident/332627#a589caf0c20f409260b1a5d849e866575a88044a35fc6ae5900676c5cce596d0 Power to the machine itself was not lost because it has a+b power. https://status.nasulex.net/incident/332627 Tue, 27 Feb 2024 08:00:00 -0000 https://status.nasulex.net/incident/332627#a589caf0c20f409260b1a5d849e866575a88044a35fc6ae5900676c5cce596d0 Power to the machine itself was not lost because it has a+b power. https://status.nasulex.net/incident/332627 Tue, 27 Feb 2024 08:00:00 -0000 https://status.nasulex.net/incident/332627#a589caf0c20f409260b1a5d849e866575a88044a35fc6ae5900676c5cce596d0 Power to the machine itself was not lost because it has a+b power. https://status.nasulex.net/incident/332627 Tue, 27 Feb 2024 08:00:00 -0000 https://status.nasulex.net/incident/332627#a589caf0c20f409260b1a5d849e866575a88044a35fc6ae5900676c5cce596d0 Power to the machine itself was not lost because it has a+b power.