Heartbeat IT migrating from Eygelshoven

terrorgen · July 25

Got this from Hearbeat IT @mxmla

Hi!

Due to ongoing network issues with our infrastructure in our Netherlands location we are conducting an emergency data center migration from Skylink in Eygelshoven to Databarn in Amsterdam on 29.07.2025 08:00 CEST

We are aware that the Emergency Data Center Migration happens on short notice, but we have to weigh up the ongoing network issues and the impact of a short-notice migration.

The last few weeks we prepared the infrastructure in our new Netherlands location in Amsterdam. For more details regarding the data center, check out https://www.databarn.nl

Please ensure you have up to date backups at hand before the shutdown of the servers for the migration.

More details regarding the Emergency Data Center Migration:

On 29.07.2025 at 08:00 CEST we will start shutting down servers and packaging them.

At around 11:00 CEST we expect to start the journey towards Amsterdam and expect to arrive at 15:00 CEST.

We start installing the servers after our arrival and expect to be done at around 22:00 CEST.

Your service will be started by us automatically after the migration.

Updates will be available at https://status.heartbeat-it.com

The client area will be under maintenance during the migration. You will receive 7 days towards your due date as compensation.

Thank you for your ongoing support. We strive to get back to better standards and back to the service quality we were able to offer in the past.

If you have questions regarding the migration, please feel free to contact us via support ticket.

Kind Regards, 

heartbeat IT - Team

heartbeat_IT · July 25

Thanks for posting!

terrorgen · July 25

congratulations on your first post! :P

jokes aside, I have never had any problems at Eygelshoven, but, I am not a heavy user there.

Fritz · July 25

Should I be worried @heartbeat_IT ?

AuroraZero · July 25

@Fritz said:
Should I be worried @heartbeat_IT ?

Worry now not later !!

benz · July 25

That took longer than expected.
Great to hear they're finally leaving Skylink again.

Would've leaved them months ago, if Computebox would support custom ISO installs.

Freek · July 25

I have been reporting packet loss for almost 7 months now and have submitted countless MTRs. And now, suddenly, it’s considered an emergency… Better late than never, I guess.

@heartbeat_IT Will IP addresses remain the same? Thank you.

daffy · July 25

@Freek said:
I have been reporting packet loss for almost 7 months now and have submitted countless MTRs. And now, suddenly, it’s considered an emergency… Better late than never, I guess.

@heartbeat_IT Will IP addresses remain the same? Thank you.

Freeeeek! Hope you're doing well mate 💪

remy · July 25

No experience with databarn DC
but I guess it can’t be worse than Skylink, am I wrong?

That said, their services are really good except network recently

cmeerw · July 26

@remy said:
No experience with databarn DC
but I guess it can’t be worse than Skylink, am I wrong?

But is SkyLink really the problem here? I have a VPS with KTS24 (also hosted at SkyLink) and not seeing any network issues.

remy · July 26

@cmeerw said:

@remy said:
No experience with databarn DC
but I guess it can’t be worse than Skylink, am I wrong?

But is SkyLink really the problem here? I have a VPS with KTS24 (also hosted at SkyLink) and not seeing any network issues.

Are they using skylink as upstream ?
Maybe they use another transit provider

Explanations posted on OGF:

Our network uses Syklink's Transport towards Nikhef and Skylink IP Transit as backup. Skylink uses it's Transport towards for their IP Transit as well. Main issues in the past weeks / months were issues with this Transport (maintenance, repeater issue, transport offline and so on). During issues with the Transport nearly all clients of Skylink using the Transport use Skylink IP Transit so congestion leads to packet loss.

So yes skylink is part of the problem

mizzik · July 26

Let's hear what @RapToN has to say

RapToN · July 26

@remy said:

@cmeerw said:

@remy said:
No experience with databarn DC
but I guess it can’t be worse than Skylink, am I wrong?

But is SkyLink really the problem here? I have a VPS with KTS24 (also hosted at SkyLink) and not seeing any network issues.

Are they using skylink as upstream ?
Maybe they use another transit provider

We use the Skylink ASN and have never had the need to look for another network provider.
Of course there have been problems there too, but where not? (I haven't always had such good experiences, especially with rather inexpensive data centers, in the past)

Freek · July 26

@daffy said:

@Freek said:
I have been reporting packet loss for almost 7 months now and have submitted countless MTRs. And now, suddenly, it’s considered an emergency… Better late than never, I guess.

@heartbeat_IT Will IP addresses remain the same? Thank you.

Freeeeek! Hope you're doing well mate 💪

I'm still alive and kicking !

Calypso · July 27

@Freek said:
I have been reporting packet loss for almost 7 months now and have submitted countless MTRs. And now, suddenly, it’s considered an emergency… Better late than never, I guess.

@heartbeat_IT Will IP addresses remain the same? Thank you.

Well, not entirely true in defend of @Heartbeat_IT. They've announced that they were looking at other DCs in the Netherlands some time ago because of the issues. And I know that more providers in that DC are doing the same, just haven't announced it yet.

Calypso · July 27

@terrorgen said:
congratulations on your first post! :P

jokes aside, I have never had any problems at Eygelshoven, but, I am not a heavy user there.

Are you monitoring? They've had several issues that affected most if not all users. E.g. a power issue some time ago. Main issue is with connectivity though that affected lots of users: migrations to new network stack that took way longer as announced (days instead of "a few hours"), defects on equipment and as Freek mentioned strange packet loss - sometimes accounted for as being DDoSsed.

I Don't know the organisational structure of the DC though, but I know that HeartBeat_IT does business with a subcontractor that they say is lacking responsiveness in solving issues regarding hardware, and that it is also a major reason for moving out. Heard the same comment from other providers in the DC.

cpsd · July 28

i hope the new DC works better. I am a happy customer since a few years already

terrorgen · July 28

@Calypso said:

@terrorgen said:
congratulations on your first post! :P

jokes aside, I have never had any problems at Eygelshoven, but, I am not a heavy user there.

Are you monitoring?

I have an uptime kuma monitoring my VPS instance there, but I don't remember seeing any downtime.

Fritz · July 29

@terrorgen said:

@Calypso said:

@terrorgen said:
congratulations on your first post! :P

jokes aside, I have never had any problems at Eygelshoven, but, I am not a heavy user there.

Are you monitoring?

I have an uptime kuma monitoring my VPS instance there, but I don't remember seeing any downtime.

Same here, didn't see any downtime for the past 6 months.

Jab · July 29

As those were 'micro' outages it's hard to catch it on monitoring (until you do tcp + live).
With something like 1 minute / 5 minutes cycle (and trigger only on repeat) you most likely won't see it.
But if you ever wanted to visit your website hosted on HB thing (and/or via Cloudflare for example) and it ended with some random timeout error and 20 seconds later after "WTF IS THIS, is this up, my monitoring says it's up, let's F5/CTRL + R" it's back... then it wasn't timeout error, it was this micro disconnect :-D

Calypso · July 29

@Jab said:
As those were 'micro' outages it's hard to catch it on monitoring (until you do tcp + live).
With something like 1 minute / 5 minutes cycle (and trigger only on repeat) you most likely won't see it.
But if you ever wanted to visit your website hosted on HB thing (and/or via Cloudflare for example) and it ended with some random timeout error and 20 seconds later after "WTF IS THIS, is this up, my monitoring says it's up, let's F5/CTRL + R" it's back... then it wasn't timeout error, it was this micro disconnect :-D

True - but there are possibilities in monitoring to have a bigger chance of catching them. Anyway, I had an SQL node in Eygelshoven and it had to resync quite a few times a day because of short periods of no connection to the other nodes. Had to withdraw that VPS of the cluster and use it for other purposes that aren't that critical.

Freek · July 30

@Calypso said:

@Freek said:
I have been reporting packet loss for almost 7 months now and have submitted countless MTRs. And now, suddenly, it’s considered an emergency… Better late than never, I guess.

@heartbeat_IT Will IP addresses remain the same? Thank you.

Well, not entirely true in defend of @Heartbeat_IT. They've announced that they were looking at other DCs in the Netherlands some time ago because of the issues. And I know that more providers in that DC are doing the same, just haven't announced it yet.

Ah, I wasn't aware of that. I must admit I've stopped following the saga after they ghosted my ticket. It would've been nice to know.

Even after the migration, I'm still observing packet loss. At this point, I'm seriously doubting whether it was Skylink's network after all.

cochon · July 30

@Freek said:
Even after the migration, I'm still observing packet loss. At this point, I'm seriously doubting whether it was Skylink's network after all.

Ditto but seems to have settled down for me since 15:00 UTC. Maybe give them 24 hours to bed in.

Heartbeat IT migrating from Eygelshoven

Comments