v6node down???

louiejordan

That's odd. My VPS shut down by itself, and then after I clicked the "start" button in the v6node control panel, it came back online. I've never experienced this before.

johndeo983

Support tickets are like raising your hand when you need help. Imagine you have a problem with a toy, like it’s not working. Instead of just saying “help!” to everyone, you write down your problem on a piece of paper and give it to someone who can fix it.

In the grown-up world, that piece of paper is called a "support ticket." It helps the helpers keep track of who needs help, what the problem is, and when they can fix it. So, it’s like asking for help in an organized way!

Arirang

@johndeo983 said:
Support tickets are like raising your hand when you need help. Imagine you have a problem with a toy, like it’s not working. Instead of just saying “help!” to everyone, you write down your problem on a piece of paper and give it to someone who can fix it.

In the grown-up world, that piece of paper is called a "support ticket." It helps the helpers keep track of who needs help, what the problem is, and when they can fix it. So, it’s like asking for help in an organized way!

Until just now, their site was down also. Seems back up now

ptreja

Mine shut itself down too and I had to manually restart it from the control panel, hasn't happened before. Did that happen to everyone?

Decicus

Looks like there was a power outage and failover power didn't trigger as it should've: https://status.v6node.com/cm4betnan001qhs9930s9av04

louiejordan

@Decicus said:
Looks like there was a power outage and failover power didn't trigger as it should've: https://status.v6node.com/cm4betnan001qhs9930s9av04

Yes, I received the email just now.

skorupion

RIP my uptime

v3ng

Hi,

Our FRA1 presence was affected by a power outage earlier today. Both the A and B feeds went completely down. In fact, the entire data center was impacted, not just our racks.

We’ve posted further details on our status page.

As communicated in an earlier post, we have decided to migrate all existing infrastructure to a new facility, effective in Q1 2025. This decision is based not only on this incident but also on unreliable remote hands and limited growth options.

Preparation has already begun, and we expect to activate the networking in early January or February.

We apologize for the inconveniences and would like to thank you for your understanding

qtwrk

Is it resolved? My vps is still not working and show error message as "node is locked" ...

noisycode

@v3ng said:
Hi,

Our FRA1 presence was affected by a power outage earlier today. Both the A and B feeds went completely down. In fact, the entire data center was impacted, not just our racks.

We’ve posted further details on our status page.

As communicated in an earlier post, we have decided to migrate all existing infrastructure to a new facility, effective in Q1 2025. This decision is based not only on this incident but also on unreliable remote hands and limited growth options.

Preparation has already begun, and we expect to activate the networking in early January or February.

We apologize for the inconveniences and would like to thank you for your understanding

No gala this BF?

v3ng

Hi,

We> @qtwrk said:

Is it resolved? My vps is still not working and show error message as "node is locked" ...

Yes this is resolved, can you please drop me a message with your node id? I’ll have a look

febryanvaldo

@skorupion said: RIP my uptime

LOL. Uptime warrior.

Levi

@febryanvaldo said:

@skorupion said: RIP my uptime

LOL. Uptime warrior.

When your goal is to idle, single metric that matters is uptime. So, we are all warriors.

dieterf

@v3ng said:
Hi,

Our FRA1 presence was affected by a power outage earlier today. Both the A and B feeds went completely down. In fact, the entire data center was impacted, not just our racks.

We’ve posted further details on our status page.

As communicated in an earlier post, we have decided to migrate all existing infrastructure to a new facility, effective in Q1 2025. This decision is based not only on this incident but also on unreliable remote hands and limited growth options.

Preparation has already begun, and we expect to activate the networking in early January or February.

We apologize for the inconveniences and would like to thank you for your understanding

In which data center will you move?