Incidents reported on status page for Vultam https://status.vultam.net/ https://d1lppblt9t2x15.cloudfront.net/logos/2ac767ebefcc78af01130d9862fb6462.png https://status.vultam.net/ en https://status.vultam.net/incident/298439 Tue, 12 Dec 2023 09:00:00 +0000 https://status.vultam.net/incident/298439#b49283ce6ba7c4a0f8b981373f5a5d875a699c0ff05ad88d0270db6893df9b34 Maintenance completed https://status.vultam.net/incident/298439 Tue, 12 Dec 2023 05:00:00 -0000 https://status.vultam.net/incident/298439#83cf23e2fb5feb5de817cf5f902433234d71cca0fef8f3715c3b5e656eb67109 On December 10th, node MIA-41 experienced downtime. Following intervention by an on-site technician, the server did not respond to power actions locally. The server was subsequently disconnected and unracked for testing. After verifying its stability, it was racked again and brought back online. We assume that the issue could have been just the server getting hung up. However, to conduct a more thorough investigation, we have scheduled a hardware test to verify the integrity of all hardware components and prevent potential future downtime caused by hardware malfunctions. The hardware test is expected to take approximately 3-4 hours, and the node will be offline during this period. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 18:39:00 -0000 https://status.vultam.net/incident/277384#098ec23ad244a6e25758a53241b9823d75f28946c974543169accc3adc091a4d The issue seems to be solved now, and all servers are reachable . Affected customers can request compensation as per our SLA by opening a ticket in our client area. We deeply appreciate your patience and understanding in this matter. Should you have any further questions or concerns, please do not hesitate to reach out to us. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 18:39:00 -0000 https://status.vultam.net/incident/277384#098ec23ad244a6e25758a53241b9823d75f28946c974543169accc3adc091a4d The issue seems to be solved now, and all servers are reachable . Affected customers can request compensation as per our SLA by opening a ticket in our client area. We deeply appreciate your patience and understanding in this matter. Should you have any further questions or concerns, please do not hesitate to reach out to us. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 18:39:00 -0000 https://status.vultam.net/incident/277384#098ec23ad244a6e25758a53241b9823d75f28946c974543169accc3adc091a4d The issue seems to be solved now, and all servers are reachable . Affected customers can request compensation as per our SLA by opening a ticket in our client area. We deeply appreciate your patience and understanding in this matter. Should you have any further questions or concerns, please do not hesitate to reach out to us. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 17:16:00 -0000 https://status.vultam.net/incident/277384#38591b449698a62391fc679c12f190ce8af0ffe7247f344d0af67517a0a3d84a The Zayo OSP team has located the additional damage and has begun repairs. As they complete the splicing services should begin to restore. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 17:16:00 -0000 https://status.vultam.net/incident/277384#38591b449698a62391fc679c12f190ce8af0ffe7247f344d0af67517a0a3d84a The Zayo OSP team has located the additional damage and has begun repairs. As they complete the splicing services should begin to restore. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 17:16:00 -0000 https://status.vultam.net/incident/277384#38591b449698a62391fc679c12f190ce8af0ffe7247f344d0af67517a0a3d84a The Zayo OSP team has located the additional damage and has begun repairs. As they complete the splicing services should begin to restore. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 15:35:00 -0000 https://status.vultam.net/incident/277384#e381f5163e8b32c769e41ff5b15ff3a1aa3b2cd2e4ce597dce3aaccc3812f91e Zayo OSP continues to trouble shoot to locate a suspected second fault along the route. Our datacenter is working on bringing alternate transit online as soon as possible. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 15:35:00 -0000 https://status.vultam.net/incident/277384#e381f5163e8b32c769e41ff5b15ff3a1aa3b2cd2e4ce597dce3aaccc3812f91e Zayo OSP continues to trouble shoot to locate a suspected second fault along the route. Our datacenter is working on bringing alternate transit online as soon as possible. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 15:35:00 -0000 https://status.vultam.net/incident/277384#e381f5163e8b32c769e41ff5b15ff3a1aa3b2cd2e4ce597dce3aaccc3812f91e Zayo OSP continues to trouble shoot to locate a suspected second fault along the route. Our datacenter is working on bringing alternate transit online as soon as possible. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 13:52:00 -0000 https://status.vultam.net/incident/277384#a8f04a238218097ff6b92d6aa33243736b1f2c1f11d32ec020c66a0737068f57 An update from Zayo: Zayo OSP crews continue to work to identify the fault. The work on the original damage has been completed, but we are not seeing any restoration of services. The Zayo OSP team is working to identify any additional fault that exists so we can repair it and restore services. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 13:52:00 -0000 https://status.vultam.net/incident/277384#a8f04a238218097ff6b92d6aa33243736b1f2c1f11d32ec020c66a0737068f57 An update from Zayo: Zayo OSP crews continue to work to identify the fault. The work on the original damage has been completed, but we are not seeing any restoration of services. The Zayo OSP team is working to identify any additional fault that exists so we can repair it and restore services. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 13:52:00 -0000 https://status.vultam.net/incident/277384#a8f04a238218097ff6b92d6aa33243736b1f2c1f11d32ec020c66a0737068f57 An update from Zayo: Zayo OSP crews continue to work to identify the fault. The work on the original damage has been completed, but we are not seeing any restoration of services. The Zayo OSP team is working to identify any additional fault that exists so we can repair it and restore services. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 11:10:00 -0000 https://status.vultam.net/incident/277384#2e40fcdc2fe0803ff80560560f50bac9d504bdff185a62cdc4034d28ce15965d An update from Zayo: The crew is now moving on to 6th and final set of 12 ribbons(out of 6 sets). https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 11:10:00 -0000 https://status.vultam.net/incident/277384#2e40fcdc2fe0803ff80560560f50bac9d504bdff185a62cdc4034d28ce15965d An update from Zayo: The crew is now moving on to 6th and final set of 12 ribbons(out of 6 sets). https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 11:10:00 -0000 https://status.vultam.net/incident/277384#2e40fcdc2fe0803ff80560560f50bac9d504bdff185a62cdc4034d28ce15965d An update from Zayo: The crew is now moving on to 6th and final set of 12 ribbons(out of 6 sets). https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 10:02:00 -0000 https://status.vultam.net/incident/277384#c35436f0a57d98cf1cdac7f81d7dc83ac9d2033938f34b46db4a2856a87bf97a An update from Zayo: The 4th set of 12 ribbons is now completed. The crew is now moving on to 5th set of 12 ribbons(out of 6 sets). https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 10:02:00 -0000 https://status.vultam.net/incident/277384#c35436f0a57d98cf1cdac7f81d7dc83ac9d2033938f34b46db4a2856a87bf97a An update from Zayo: The 4th set of 12 ribbons is now completed. The crew is now moving on to 5th set of 12 ribbons(out of 6 sets). https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 10:02:00 -0000 https://status.vultam.net/incident/277384#c35436f0a57d98cf1cdac7f81d7dc83ac9d2033938f34b46db4a2856a87bf97a An update from Zayo: The 4th set of 12 ribbons is now completed. The crew is now moving on to 5th set of 12 ribbons(out of 6 sets). https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 09:08:00 -0000 https://status.vultam.net/incident/277384#b8d376b0e13b0f38d7e95e46daac8d8f5368bd1407521201f8a92562f7795960 Zayo, the company responsible for the fiber maintenance, is providing regular updates at: https://tranzact.zayo.com/#!/case-detail/5004z00001tVV9sAAG/TTN-0007089358/ Currently, 3 sets (out of 6) of 12 fiber ribbons have been restored. They are currently working on the 4th set. The estimated time of restoration is 10:30 Eastern Time. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 09:08:00 -0000 https://status.vultam.net/incident/277384#b8d376b0e13b0f38d7e95e46daac8d8f5368bd1407521201f8a92562f7795960 Zayo, the company responsible for the fiber maintenance, is providing regular updates at: https://tranzact.zayo.com/#!/case-detail/5004z00001tVV9sAAG/TTN-0007089358/ Currently, 3 sets (out of 6) of 12 fiber ribbons have been restored. They are currently working on the 4th set. The estimated time of restoration is 10:30 Eastern Time. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 09:08:00 -0000 https://status.vultam.net/incident/277384#b8d376b0e13b0f38d7e95e46daac8d8f5368bd1407521201f8a92562f7795960 Zayo, the company responsible for the fiber maintenance, is providing regular updates at: https://tranzact.zayo.com/#!/case-detail/5004z00001tVV9sAAG/TTN-0007089358/ Currently, 3 sets (out of 6) of 12 fiber ribbons have been restored. They are currently working on the 4th set. The estimated time of restoration is 10:30 Eastern Time. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 08:08:00 -0000 https://status.vultam.net/incident/277384#f8d05e76d2d705ed839651ed726ce82dd3b6e1aaab44db2fb4851a9c7b38bece We are aware of all our New York nodes and website being down at this moment. This is due to a partial outage in our New York datacenter, caused by a fiber break between PNJ and 165 Halsey datacenters. The ring has been taken offline to perform a repair. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 08:08:00 -0000 https://status.vultam.net/incident/277384#f8d05e76d2d705ed839651ed726ce82dd3b6e1aaab44db2fb4851a9c7b38bece We are aware of all our New York nodes and website being down at this moment. This is due to a partial outage in our New York datacenter, caused by a fiber break between PNJ and 165 Halsey datacenters. The ring has been taken offline to perform a repair. https://status.vultam.net/incident/277384 Wed, 25 Oct 2023 08:08:00 -0000 https://status.vultam.net/incident/277384#f8d05e76d2d705ed839651ed726ce82dd3b6e1aaab44db2fb4851a9c7b38bece We are aware of all our New York nodes and website being down at this moment. This is due to a partial outage in our New York datacenter, caused by a fiber break between PNJ and 165 Halsey datacenters. The ring has been taken offline to perform a repair. https://status.vultam.net/incident/206967 Mon, 12 Jun 2023 13:00:00 +0000 https://status.vultam.net/incident/206967#ad4dde6c1d4d0fa1cbe9a81e9b2d5c289bee17aa633b484b3a6c4828f333cdc6 Maintenance completed https://status.vultam.net/incident/206967 Mon, 12 Jun 2023 04:00:00 -0000 https://status.vultam.net/incident/206967#f7c75cba79a4b54fcd00b5fa99cc47202ef300126a697ac9838525f89093011b The dark fiber provider of our Miami datacenter will be performing an equipment upgrade. They plan to perform a hot cut between equipment. During this time, you may experience brief periods of poor routing or complete unavailability on your Miami services. https://status.vultam.net/incident/207152 Sun, 14 May 2023 03:00:00 +0000 https://status.vultam.net/incident/207152#e2d142e3a4ec82443ea7ead449add887e7c63a109216d7fad86b94b9ac1ad097 Maintenance completed https://status.vultam.net/incident/207152 Sun, 14 May 2023 02:00:00 -0000 https://status.vultam.net/incident/207152#d7bfb4db09f82444e9a40d72e855164d9a6c8fa9f51350217181dd8be0af5566 A failing switch will be replaced by a new pre-configured switch to resolve issues and reduce potential future downtime. We do not expect this maintenance to last the entire maintenance window. Maintenance window: May 13, 22:00 - 23:00 EDT Nodes affected: MIA-21, MIA-41, MIA-42 https://status.vultam.net/incident/189383 Mon, 27 Mar 2023 14:12:50 +0000 https://status.vultam.net/incident/189383#2db209c3485a72197978bffa3683ac01de6a8413efed945ff5d95a76ecf8e064 Maintenance completed https://status.vultam.net/incident/189383 Mon, 27 Mar 2023 14:12:50 -0000 https://status.vultam.net/incident/189383#788eba872b30d805ae5048874da1b70058d98062045c756e6dfe70fc3a96f5b2 The automated monitoring system has detected errors in VBAT modules on node MIA-08. The server will be powered down to run diagnostics and replace the battery if needed. We do not expect downtime for the entire maintenance window. Maintenance window: 9:30 AM EST - 10:30 AM EST https://status.vultam.net/incident/189383 Mon, 27 Mar 2023 13:30:00 -0000 https://status.vultam.net/incident/189383#788eba872b30d805ae5048874da1b70058d98062045c756e6dfe70fc3a96f5b2 The automated monitoring system has detected errors in VBAT modules on node MIA-08. The server will be powered down to run diagnostics and replace the battery if needed. We do not expect downtime for the entire maintenance window. Maintenance window: 9:30 AM EST - 10:30 AM EST https://status.vultam.net/incident/182155 Tue, 07 Mar 2023 11:22:37 +0000 https://status.vultam.net/incident/182155#8d22ce8b751394ad5f392b043ce74b969fd712af0b1d216c235785977b4e97f7 Maintenance completed https://status.vultam.net/incident/182155 Tue, 07 Mar 2023 11:22:37 -0000 https://status.vultam.net/incident/182155#3ea16dac8d467cdf8c398cc609f409cbeff45e4714fdaee0310e1d170c9a774d We will be taking offline nodes MIA-28, MIA-30, and MIA-37 to migrate the data to new nodes. The expected downtime is around 15-30 minutes per node. This won't affect your servers in any way, apart from being offline during the maintenance. Maintenance window: 07/03/2023 10:00 AM UTC - 12:00 PM UTC https://status.vultam.net/incident/182155 Tue, 07 Mar 2023 10:00:00 -0000 https://status.vultam.net/incident/182155#3ea16dac8d467cdf8c398cc609f409cbeff45e4714fdaee0310e1d170c9a774d We will be taking offline nodes MIA-28, MIA-30, and MIA-37 to migrate the data to new nodes. The expected downtime is around 15-30 minutes per node. This won't affect your servers in any way, apart from being offline during the maintenance. Maintenance window: 07/03/2023 10:00 AM UTC - 12:00 PM UTC https://status.vultam.net/incident/180411 Fri, 03 Mar 2023 11:13:55 +0000 https://status.vultam.net/incident/180411#2be9287ccb8326a5d8ef97a00104708009b48a97b5c532e74126fb291b21091a Maintenance completed https://status.vultam.net/incident/180411 Fri, 03 Mar 2023 11:13:55 -0000 https://status.vultam.net/incident/180411#89a5cf9f7ff944b73c89e268201d8b8ed5947630cc046c47de4007fde0e16f2f We will be taking offline nodes MIA-25, MIA-26, and MIA-32 to migrate the data to new nodes. The expected downtime is around 15-30 minutes per node. This won't affect your servers in any way, apart from being offline during the maintenance. Maintenance window: 03/03/2023 10:00 AM UTC - 12:00 PM UTC https://status.vultam.net/incident/180411 Fri, 03 Mar 2023 10:00:00 -0000 https://status.vultam.net/incident/180411#89a5cf9f7ff944b73c89e268201d8b8ed5947630cc046c47de4007fde0e16f2f We will be taking offline nodes MIA-25, MIA-26, and MIA-32 to migrate the data to new nodes. The expected downtime is around 15-30 minutes per node. This won't affect your servers in any way, apart from being offline during the maintenance. Maintenance window: 03/03/2023 10:00 AM UTC - 12:00 PM UTC https://status.vultam.net/incident/176883 Wed, 22 Feb 2023 23:15:46 +0000 https://status.vultam.net/incident/176883#091cb7d95e81be7ba63ea685a40d08658819413f26ce7a7d6c112fdf51b4e776 Maintenance completed https://status.vultam.net/incident/176883 Wed, 22 Feb 2023 23:15:46 -0000 https://status.vultam.net/incident/176883#f5cb6ebaa439cd230f97a7e8b4b4c19f1187e43812d1aebf534fb977dc13e019 Node MIA-31 will be taken offline as the server will be physically moved to another data center, Equinix MI1 data. We do not expect downtime for the entire maintenance window. Maintenance window: 22/02/2023 3:00 PM EST - 7:00 PM EST https://status.vultam.net/incident/176883 Wed, 22 Feb 2023 20:00:00 -0000 https://status.vultam.net/incident/176883#f5cb6ebaa439cd230f97a7e8b4b4c19f1187e43812d1aebf534fb977dc13e019 Node MIA-31 will be taken offline as the server will be physically moved to another data center, Equinix MI1 data. We do not expect downtime for the entire maintenance window. Maintenance window: 22/02/2023 3:00 PM EST - 7:00 PM EST https://status.vultam.net/incident/174468 Sun, 12 Feb 2023 16:50:08 +0000 https://status.vultam.net/incident/174468#90581679d3eaa36f058d39a433baaf60576bbf2c11663f5e30aff2163596f377 Maintenance completed https://status.vultam.net/incident/174468 Sun, 12 Feb 2023 16:50:08 -0000 https://status.vultam.net/incident/174468#82eac062f0bfd7fae1b694eecd5f4741d049066ebee9afac0576c9cf2789295d Our monitoring system has detected errors on the drive of node NY-05. We will be taking the server offline to install a new drive and transfer all the data, to anticipate a possible drive failure and prevent data loss. The expected downtime is 1-2 hours. Maintenance window: February 12th, 15:00 PM UTC - 17:00 PM UTC. https://status.vultam.net/incident/174468 Sun, 12 Feb 2023 15:00:00 -0000 https://status.vultam.net/incident/174468#82eac062f0bfd7fae1b694eecd5f4741d049066ebee9afac0576c9cf2789295d Our monitoring system has detected errors on the drive of node NY-05. We will be taking the server offline to install a new drive and transfer all the data, to anticipate a possible drive failure and prevent data loss. The expected downtime is 1-2 hours. Maintenance window: February 12th, 15:00 PM UTC - 17:00 PM UTC. https://status.vultam.net/incident/172220 Tue, 07 Feb 2023 12:02:39 +0000 https://status.vultam.net/incident/172220#be60fd079e99295c4a657ff0aeaf9e5fd524a47639fa38f79b641a2449ab093d Maintenance completed https://status.vultam.net/incident/172220 Tue, 07 Feb 2023 12:02:39 -0000 https://status.vultam.net/incident/172220#f8d0fe86c441a6660c7e67b9bc957463c2ff090d8b021af303f77771ef21e746 Servers on node MIA-19 will be powered off momentarily to apply a software patch. Downtime should be less than 5 minutes. https://status.vultam.net/incident/172220 Tue, 07 Feb 2023 12:00:00 -0000 https://status.vultam.net/incident/172220#f8d0fe86c441a6660c7e67b9bc957463c2ff090d8b021af303f77771ef21e746 Servers on node MIA-19 will be powered off momentarily to apply a software patch. Downtime should be less than 5 minutes. https://status.vultam.net/incident/172197 Tue, 07 Feb 2023 10:39:24 +0000 https://status.vultam.net/incident/172197#a8ca4ff2cc5a7654bfd4472024df26772354ce26d2cf6e9e1180191b10e49fac Maintenance completed https://status.vultam.net/incident/172197 Tue, 07 Feb 2023 10:39:24 -0000 https://status.vultam.net/incident/172197#6a9b89799012bd68f20b81d6d19231189cfdad5fbc5131a447230e7deeed9a32 We will be taking offline node MIA-38 to migrate the data to a new node (MIA-42), as we are discontinuing the current node. The expected downtime is around 20-40 minutes. https://status.vultam.net/incident/172197 Tue, 07 Feb 2023 10:00:00 -0000 https://status.vultam.net/incident/172197#6a9b89799012bd68f20b81d6d19231189cfdad5fbc5131a447230e7deeed9a32 We will be taking offline node MIA-38 to migrate the data to a new node (MIA-42), as we are discontinuing the current node. The expected downtime is around 20-40 minutes. https://status.vultam.net/incident/171665 Mon, 06 Feb 2023 10:58:43 +0000 https://status.vultam.net/incident/171665#43c10875cd3860ae213be5db1a7587eadc4e140600b28c8f5da2a7413a322b29 Maintenance completed https://status.vultam.net/incident/171665 Mon, 06 Feb 2023 10:58:43 -0000 https://status.vultam.net/incident/171665#856ac2b625f3f1327f489a076a059933618eda144e53b02879397bd58457e7af We will be taking offline node MIA-36 to migrate the data to a new node (MIA-41), as we are discontinuing the current node. The expected downtime is around 20-40 minutes. https://status.vultam.net/incident/171665 Mon, 06 Feb 2023 10:00:00 -0000 https://status.vultam.net/incident/171665#856ac2b625f3f1327f489a076a059933618eda144e53b02879397bd58457e7af We will be taking offline node MIA-36 to migrate the data to a new node (MIA-41), as we are discontinuing the current node. The expected downtime is around 20-40 minutes. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 20:17:00 -0000 https://status.vultam.net/incident/167073#0c807886d223869c6c0e9a18916696f20e41ff1528f5a2bb1a0e805d874396b0 The issue has been resolved, and all nodes are back online. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 20:17:00 -0000 https://status.vultam.net/incident/167073#0c807886d223869c6c0e9a18916696f20e41ff1528f5a2bb1a0e805d874396b0 The issue has been resolved, and all nodes are back online. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 20:17:00 -0000 https://status.vultam.net/incident/167073#0c807886d223869c6c0e9a18916696f20e41ff1528f5a2bb1a0e805d874396b0 The issue has been resolved, and all nodes are back online. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 19:04:00 -0000 https://status.vultam.net/incident/167073#47bb0e54a605d6e3e4f8dd1eaa834b1c2ff7d749242cfb8267be6189c607bafc We have been provided an ETA of 4 PM Eastern for when replacement equipment is expected to be installed. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 19:04:00 -0000 https://status.vultam.net/incident/167073#47bb0e54a605d6e3e4f8dd1eaa834b1c2ff7d749242cfb8267be6189c607bafc We have been provided an ETA of 4 PM Eastern for when replacement equipment is expected to be installed. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 19:04:00 -0000 https://status.vultam.net/incident/167073#47bb0e54a605d6e3e4f8dd1eaa834b1c2ff7d749242cfb8267be6189c607bafc We have been provided an ETA of 4 PM Eastern for when replacement equipment is expected to be installed. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 17:57:00 -0000 https://status.vultam.net/incident/167073#aa1824f1db765da0361c5c2b18041876eb875687047201b1f87ed7bf7e421592 Replacement equipment is currently being set up and will be replaced shortly after. We haven't been given an ETA, but we expect to be online in the next few hours. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 17:57:00 -0000 https://status.vultam.net/incident/167073#aa1824f1db765da0361c5c2b18041876eb875687047201b1f87ed7bf7e421592 Replacement equipment is currently being set up and will be replaced shortly after. We haven't been given an ETA, but we expect to be online in the next few hours. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 17:57:00 -0000 https://status.vultam.net/incident/167073#aa1824f1db765da0361c5c2b18041876eb875687047201b1f87ed7bf7e421592 Replacement equipment is currently being set up and will be replaced shortly after. We haven't been given an ETA, but we expect to be online in the next few hours. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 17:44:00 -0000 https://status.vultam.net/incident/167073#9fd5aa5ec2e8f8097229a97753cb19f0aa0b4350c2d25cd263e2364334c6fa0f The issue at 165 Halsey has been isolated to specific equipment. We are waiting for more details and an ETA. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 17:44:00 -0000 https://status.vultam.net/incident/167073#9fd5aa5ec2e8f8097229a97753cb19f0aa0b4350c2d25cd263e2364334c6fa0f The issue at 165 Halsey has been isolated to specific equipment. We are waiting for more details and an ETA. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 17:44:00 -0000 https://status.vultam.net/incident/167073#9fd5aa5ec2e8f8097229a97753cb19f0aa0b4350c2d25cd263e2364334c6fa0f The issue at 165 Halsey has been isolated to specific equipment. We are waiting for more details and an ETA. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 16:51:00 -0000 https://status.vultam.net/incident/167073#473bf7ff18be8c59b855230edff79fdc8292f4c7607e0d49772abd2563cb5ffa The issue has been isolated to 165 Halsey (not our data center) as they are currently experiencing data center wide issues affecting major carriers and providers. We are waiting for further updates from the data center. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 16:51:00 -0000 https://status.vultam.net/incident/167073#473bf7ff18be8c59b855230edff79fdc8292f4c7607e0d49772abd2563cb5ffa The issue has been isolated to 165 Halsey (not our data center) as they are currently experiencing data center wide issues affecting major carriers and providers. We are waiting for further updates from the data center. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 16:51:00 -0000 https://status.vultam.net/incident/167073#473bf7ff18be8c59b855230edff79fdc8292f4c7607e0d49772abd2563cb5ffa The issue has been isolated to 165 Halsey (not our data center) as they are currently experiencing data center wide issues affecting major carriers and providers. We are waiting for further updates from the data center. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 15:45:00 -0000 https://status.vultam.net/incident/167073#22aeeaa833e35822f17c443e32dcc390a075de685f3061721591fd625020daf7 We are aware of all our New York nodes being down due to an outage in the New York datacenter, related to an issue with backhaul causing unavailability through certain routes. This also made our website and client area unavailable. Datacenter technicians are investigating the issue. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 15:45:00 -0000 https://status.vultam.net/incident/167073#22aeeaa833e35822f17c443e32dcc390a075de685f3061721591fd625020daf7 We are aware of all our New York nodes being down due to an outage in the New York datacenter, related to an issue with backhaul causing unavailability through certain routes. This also made our website and client area unavailable. Datacenter technicians are investigating the issue. https://status.vultam.net/incident/167073 Sun, 22 Jan 2023 15:45:00 -0000 https://status.vultam.net/incident/167073#22aeeaa833e35822f17c443e32dcc390a075de685f3061721591fd625020daf7 We are aware of all our New York nodes being down due to an outage in the New York datacenter, related to an issue with backhaul causing unavailability through certain routes. This also made our website and client area unavailable. Datacenter technicians are investigating the issue. https://status.vultam.net/incident/149086 Thu, 29 Dec 2022 10:56:17 -0000 https://status.vultam.net/incident/149086#ec99ba08221dbcc3ab973d7a76e2138bca96820fc44e2b4176396d2a6b02a31f We will be taking offline node MIA-07 to migrate the data to a new node (MIA-40), as we are discontinuing the current node. The expected downtime is around 1-2 hours. This won't affect your server in any way, apart from being offline during the maintenance. https://status.vultam.net/incident/149086 Thu, 29 Dec 2022 10:56:17 +0000 https://status.vultam.net/incident/149086#bfb7bf83f0fe63eda3702acd398d62791531ab16c419ea75702c72326d66ca29 Maintenance completed https://status.vultam.net/incident/149086 Thu, 29 Dec 2022 10:00:00 -0000 https://status.vultam.net/incident/149086#ec99ba08221dbcc3ab973d7a76e2138bca96820fc44e2b4176396d2a6b02a31f We will be taking offline node MIA-07 to migrate the data to a new node (MIA-40), as we are discontinuing the current node. The expected downtime is around 1-2 hours. This won't affect your server in any way, apart from being offline during the maintenance. https://status.vultam.net/incident/146071 Wed, 21 Dec 2022 01:00:00 +0000 https://status.vultam.net/incident/146071#4d2df5006eb92b1ebaab5038c8f0f6ede405de1fdc6dc970ecdb273a013022c3 Maintenance completed https://status.vultam.net/incident/146071 Tue, 20 Dec 2022 20:00:00 -0000 https://status.vultam.net/incident/146071#e04309da08c5b316db09ef0df32dd29df934db319b7e77a3e6f4e2ede6caeec7 Node MIA-23 will be taken offline as the server will be moved to another datacenter, Equinix MI1 data. We do not expect downtime for the entire maintenance window. https://status.vultam.net/incident/146073 Mon, 19 Dec 2022 12:30:00 +0000 https://status.vultam.net/incident/146073#bc811d952cd618499b96c209659d97c88a4b18e5a06c058ad5a52f0f80c86c3d Maintenance completed https://status.vultam.net/incident/146073 Mon, 19 Dec 2022 10:30:00 -0000 https://status.vultam.net/incident/146073#2ec87501aff4c35a02ca908301b198406d34b946865e78b4230f95a15ed7d70d The game control panel (panel.vultam.net) will be momentarily down to apply updates. Panel downtime shouldn't take all the maintenance window, just a few minutes. The maintenance window includes other tasks we will be doing in the background, but may cause disruptions. Your servers won't be affected and will remain online during the entire maintenance.