VibeGAMES Outage History

Started Mar 14, 2025, 10:37 AM UTC· resolved Mar 14, 2025, 12:57 PM UTC

1. investigating Mar 14, 2025, 10:37 AM UTC

   We experience some connection issues in Sydney as result of a problem at Gcore. International traffic is unable to reach this sites but local traffic is still working.

2. resolved Mar 14, 2025, 12:57 PM UTC

   The issue has been resolved and was caused by a backbone issue between NA/EU and Australia at a third party.

Read the full incident report →

Started Feb 28, 2025, 11:15 AM UTC· resolved Mar 01, 2025, 08:21 PM UTC

1. investigating Feb 28, 2025, 11:15 AM UTC

   We currently have a network outage in Miami, Dallas, Chicago, New York, Sydney, and Johannesburg.

2. resolved Mar 01, 2025, 08:21 PM UTC

   Sydney traffic is routed back over Gcore now.

Read the full incident report →

Started Feb 20, 2025, 10:37 PM UTC· resolved Feb 20, 2025, 10:41 PM UTC

1. investigating Feb 20, 2025, 10:37 PM UTC

   Our upstream CDN77 is having an outage in Singapore. They are working on a fix. We have no other information at the moment.

2. resolved Feb 20, 2025, 10:41 PM UTC

   Singapore is back up. CDN77 resolved the issue. We will update you once we have more info about the cause.

Read the full incident report →

Started Feb 12, 2025, 03:18 PM UTC· resolved Feb 12, 2025, 03:40 PM UTC

1. investigating Feb 12, 2025, 03:18 PM UTC

   We encountered an issue in our Singapore region at 15:18 UTC, resulting in a player drop. Our team is actively investigating the cause. Thank you for your patience.

2. resolved Feb 12, 2025, 03:40 PM UTC

   The issue in our Singapore region has been resolved. The cause was a hardware failure on one of Gcore’s load balancers. It has been removed from the pool, and the network is now stable again. Thank you for your patience.

Read the full incident report →

Started Jan 23, 2025, 07:21 PM UTC· resolved Feb 01, 2025, 01:55 PM UTC

1. investigating Jan 23, 2025, 07:21 PM UTC

   Path.net is down in Miami at the moment caused the location to be unreachable at the moment

2. resolved Feb 01, 2025, 01:55 PM UTC

   Thank you for your patience. We appreciate that most of our affected Miami customers have been understanding during this situation. We've been working tirelessly to find the best possible solution for everyone following yesterday's news about Path.net. What happened? On January 23rd, our Miami location went down due to a complete outage of the Path.net network. Since our servers were colocated in the same rack as Path.net, they were directly affected. For the first five days, we received no meaningful updates from the Path team. Eventually, after a series of false promises, we were informed of an "electrical issue" in their cabinet. Shortly after, other Path.net locations—including Singapore, Tokyo, Madrid, Chicago, San Jose, and Phoenix—also went offline. Yesterday, Path.net finally made an official statement confirming what we had already suspected based on the information we received before: they failed to meet their financial obligations to Equinix, leading to power being cut from their racks. Fortunately, Miami was the last location where we were still using Path.net; all other locations had already been migrated to a new network. What’s next? We’ve been working around the clock to deploy replacement servers, and we’re happy to announce that they are now fully operational. To compensate for the downtime, all affected Miami customers will receive one month of free hosting, in accordance with our ToS. Additionally, we’ve upgraded all Miami servers from AMD Ryzen 5950X to AMD Ryzen 7950X3D, delivering a significant performance boost. New login details will be sent via email shortly so customers can regain access to their servers. What about the data? At this time, the status of your previous data remains uncertain. Path.net has stated that they plan to "relocate datacenters soon," but they have provided no ETA. While the data is still intact and has not been removed, we have serious doubts about their ability to restore access. Given Path.net’s lack of transparency throughout this process, we cannot guarantee any timeline or outcome. If the data becomes available again, affected customers will have the option to request it be attached as a secondary drive to their new server, allowing them to recover their files. Or if you have a backup yourself you can obviously restore that on the new server. Final Thoughts We deeply regret the situation and the impact it has had on our customers. Throughout this process, we have done our best to keep you informed and to resolve the issue as efficiently as possible. We appreciate your support and understanding, and we hope the actions we've taken help make up for this unexpected disruption. Thank you, VibeGAMES Team

3. investigating Feb 01, 2025, 01:55 PM UTC

   Thank you for your patience. We appreciate that most of our affected Miami customers have been understanding during this situation. We've been working tirelessly to find the best possible solution for everyone following yesterday's news about Path.net. What happened? On January 23rd, our Miami location went down due to a complete outage of the Path.net network. Since our servers were colocated in the same rack as Path.net, they were directly affected. For the first five days, we received no meaningful updates from the Path team. Eventually, after a series of false promises, we were informed of an "electrical issue" in their cabinet. Shortly after, other Path.net locations—including Singapore, Tokyo, Madrid, Chicago, San Jose, and Phoenix—also went offline. Yesterday, Path.net finally made an official statement confirming what we had already suspected based on the information we received before: they failed to meet their financial obligations to Equinix, leading to power being cut from their racks. Fortunately, Miami was the last location where we were still using Path.net; all other locations had already been migrated to a new network. What’s next? We’ve been working around the clock to deploy replacement servers, and we’re happy to announce that they are now fully operational. To compensate for the downtime, all affected Miami customers will receive one month of free hosting, in accordance with our ToS. Additionally, we’ve upgraded all Miami servers from AMD Ryzen 5950X to AMD Ryzen 7950X3D, delivering a significant performance boost. New login details will be sent via email shortly so customers can regain access to their servers. What about the data? At this time, the status of your previous data remains uncertain. Path.net has stated that they plan to "relocate datacenters soon," but they have provided no ETA. While the data is still intact and has not been removed, we have serious doubts about their ability to restore access. Given Path.net’s lack of transparency throughout this process, we cannot guarantee any timeline or outcome. If the data becomes available again, affected customers will have the option to request it be attached as a secondary drive to their new server, allowing them to recover their files. Or if you have a backup yourself you can obviously restore that on the new server. Final Thoughts We deeply regret the situation and the impact it has had on our customers. Throughout this process, we have done our best to keep you informed and to resolve the issue as efficiently as possible. We appreciate your support and understanding, and we hope the actions we've taken help make up for this unexpected disruption. Thank you, VibeGAMES Team

Read the full incident report →

Started Nov 08, 2024, 01:11 AM UTC· resolved Nov 08, 2024, 01:35 AM UTC

1. investigating Nov 08, 2024, 01:11 AM UTC

   We currently experience an outage in Amsterdam. We are investigating the issue.

2. resolved Nov 08, 2024, 01:35 AM UTC

   The issue was caused by an outage in our wave to Nikhef Amstedam. We switched to our backup route and the location is back up and fully operational.

3. investigating Nov 08, 2024, 01:35 AM UTC

   The issue was caused by an outage in our wave to Nikhef Amstedam. We switched to our backup route and the location is back up and fully operational.

Read the full incident report →