C-Servers | The Pub

cservers

Thread to bring out some news regarding C-Servers, general chit-chat, and some good talks on the rocks. Some good campaigns and coupons may land here as well.

web.c-servers.co.uk

yoursunny

We don’t buy C-Servers unless it’s the 99-year plan.

kf5ydu

I think it’s good for users to have control over selecting what resources they need. So long as it actually provides a discount and isn’t used to raise prices of existing resources like a lot of large companies would do.

As long as a company is transparent on their pricing and comparisons I think it’s an excellent solution. That’s one of the things I love about this forum, we can actually talk to the people selling us things.

cservers

Nothing that the FULL15 coupon is still working and will continue to work until the end of the month; and that new coupon codes and percentages will be provided here shortly.

We also continue improving geolocation and looking forward to improve peerings to specific peers on our ASN.

cservers

We are aware of a networking fault at Delta1 which is causing the server to be inaccessible since 06AM and have escalated to the correspondent agent in order to sort the issue out as soon as possible.

There seems to be no hardware fault as consumption has continued during this period.

EDIT: Seems the counter is not correct. Power maintenance at Telehouse until 6PM. We do apologize. https://status.23m.com/maintenance-windows/63671

edmarhub

@cservers said:
We are aware of a networking fault at Delta1 which is causing the server to be inaccessible since 06AM and have escalated to the correspondent agent in order to sort the issue out as soon as possible.

There seems to be no hardware fault as consumption has continued during this period.

EDIT: Seems the counter is not correct. Power maintenance at Telehouse until 6PM. We do apologize. https://status.23m.com/maintenance-windows/63671

@cservers can you check your Amsterdam Full VPS I think it is down for a couple of hours already, also the ai support is bugging can't proceed the login!

cservers

@edmarhub said:

@cservers said:
We are aware of a networking fault at Delta1 which is causing the server to be inaccessible since 06AM and have escalated to the correspondent agent in order to sort the issue out as soon as possible.

There seems to be no hardware fault as consumption has continued during this period.

EDIT: Seems the counter is not correct. Power maintenance at Telehouse until 6PM. We do apologize. https://status.23m.com/maintenance-windows/63671

@cservers can you check your Amsterdam Full VPS I think it is down for a couple of hours already, also the ai support is bugging can't proceed the login!

We do have a hardware fault at Amsterdam. It was already escalated to the upstream, which acknowledged the message we've sent and will be checking in order to sort it out. Over the past week things were progressively less stable due to one of the RAM ECC sticks there posting more errors than usual (without corruption risk - all were corrected) and probably that module has now packed up for good - will need a replacement. That had been detected already on September 20th and a ticket had already been proactively opened.

Peerings may be slower as well at AS214566, temporarily, for the same reason.

We do apologize for the inconvenience. All updates first-hand at https://portal.cfld.uk/status.

Scioner

@cservers said:
We do have a hardware fault at Amsterdam. It was already escalated to the upstream, which acknowledged the message we've sent and will be checking in order to sort it out. Over the past week things were progressively less stable due to one of the RAM ECC sticks there posting more errors than usual (without corruption risk - all were corrected) and probably that module has now packed up for good - will need a replacement. That had been detected already on September 20th and a ticket had already been proactively opened.

Peerings may be slower as well at AS214566, temporarily, for the same reason.

We do apologize for the inconvenience. All updates first-hand at https://portal.cfld.uk/status.

Btw, AI chat bot escalated my issue to the ticket the moment it checks it can't access the server, even though I didn't ask for escalation. I'm pretty sure there was already a pile of tickets like that, as I waited relatively long before even talking to the bot.

Probably there should be something like "bot database", which records recent issues. This way bot can answer with "we had reports about that, thank you".

cservers

@Scioner said:

@cservers said:
We do have a hardware fault at Amsterdam. It was already escalated to the upstream, which acknowledged the message we've sent and will be checking in order to sort it out. Over the past week things were progressively less stable due to one of the RAM ECC sticks there posting more errors than usual (without corruption risk - all were corrected) and probably that module has now packed up for good - will need a replacement. That had been detected already on September 20th and a ticket had already been proactively opened.

Peerings may be slower as well at AS214566, temporarily, for the same reason.

We do apologize for the inconvenience. All updates first-hand at https://portal.cfld.uk/status.

Btw, AI chat bot escalated my issue to the ticket the moment it checks it can't access the server, even though I didn't ask for escalation. I'm pretty sure there was already a pile of tickets like that, as I waited relatively long before even talking to the bot.

Probably there should be something like "bot database", which records recent issues. This way bot can answer with "we had reports about that, thank you".

That is actually an excellent idea - the agent can search the topics of existing tickets and if there is a majority of the same topic it can simply state that and notify the systems department

There was indeed a certain ticket peak at that time. Per usual whenever a fault like these happens... at all providers.

We think it's somewhat inefficient having all tickets talking about the same... only adds pressure to something the provider is already aware of. And time spent answering the tickets can be better spent pushing ahead to fix the issue as soon as possible. Probably a good use of automation there.

Wonder_Woman

Hey @cservers, I hope you're doing well!

I just went to check on the status of a ticket that the chat said it had opened for me almost a week ago, and I was surprised to see there's no ticket! I'm trying to talk with the chat bot again now, and all I'm getting is:

"Sorry, I'm having some issues. Can you try asking your question again?"

Repeated, no matter what I type.

cservers

@Wonder_Woman said:
Hey @cservers, I hope you're doing well!

I just went to check on the status of a ticket that the chat said it had opened for me almost a week ago, and I was surprised to see there's no ticket! I'm trying to talk with the chat bot again now, and all I'm getting is:

"Sorry, I'm having some issues. Can you try asking your question again?"

Repeated, no matter what I type.

Hello! We've been getting tickets yesterday and today - this could be sometimes a temporary unavailability from the underlying AI platform but should clear out on itself. We've just tested and it's bringing answers as of right now.

edmarhub

@cservers said:

@edmarhub said:

@cservers said:
We are aware of a networking fault at Delta1 which is causing the server to be inaccessible since 06AM and have escalated to the correspondent agent in order to sort the issue out as soon as possible.

There seems to be no hardware fault as consumption has continued during this period.

EDIT: Seems the counter is not correct. Power maintenance at Telehouse until 6PM. We do apologize. https://status.23m.com/maintenance-windows/63671

@cservers can you check your Amsterdam Full VPS I think it is down for a couple of hours already, also the ai support is bugging can't proceed the login!

We do have a hardware fault at Amsterdam. It was already escalated to the upstream, which acknowledged the message we've sent and will be checking in order to sort it out. Over the past week things were progressively less stable due to one of the RAM ECC sticks there posting more errors than usual (without corruption risk - all were corrected) and probably that module has now packed up for good - will need a replacement. That had been detected already on September 20th and a ticket had already been proactively opened.

Peerings may be slower as well at AS214566, temporarily, for the same reason.

We do apologize for the inconvenience. All updates first-hand at https://portal.cfld.uk/status.

Any ETA? Seems like it is 3days and 6hrs already since the last time I got a probe response from the server? Any plan compensation like extended expiration while the maintenance is on progress?

cservers

@edmarhub said:

@cservers said:

@edmarhub said:

@cservers said:
We are aware of a networking fault at Delta1 which is causing the server to be inaccessible since 06AM and have escalated to the correspondent agent in order to sort the issue out as soon as possible.

There seems to be no hardware fault as consumption has continued during this period.

EDIT: Seems the counter is not correct. Power maintenance at Telehouse until 6PM. We do apologize. https://status.23m.com/maintenance-windows/63671

@cservers can you check your Amsterdam Full VPS I think it is down for a couple of hours already, also the ai support is bugging can't proceed the login!

We do have a hardware fault at Amsterdam. It was already escalated to the upstream, which acknowledged the message we've sent and will be checking in order to sort it out. Over the past week things were progressively less stable due to one of the RAM ECC sticks there posting more errors than usual (without corruption risk - all were corrected) and probably that module has now packed up for good - will need a replacement. That had been detected already on September 20th and a ticket had already been proactively opened.

Peerings may be slower as well at AS214566, temporarily, for the same reason.

We do apologize for the inconvenience. All updates first-hand at https://portal.cfld.uk/status.

Any ETA? Seems like it is 3days and 6hrs already since the last time I got a probe response from the server? Any plan compensation like extended expiration while the maintenance is on progress?

Yes, extended expiration is a possibility, additional days are a possibility, and so it goes.

Pinged the upstream for this one. We want this up and working as soon as possible.

cservers

Alpha1 Amsterdam back online, but with two caveats I'm mentioning here:

• the session with AS214481 is temporarily down, so we're rerouting with Hop179 also in AMS as a fallback temporarily, and it's all temporarily limited to 1 Gbps. We could have prioritized Coventry for that, but it would have added latency and we preferred location over speed, given that the plans were announced already with 2 Gbps maximum.

• the server is not yet stable, as the defective RAM module - or the server change - was not dealt with over the weekend, due to being the weekend (as we suspected and mentioned beforehand on the Status portal). Therefore, we have tested the defective RAM module, and found that selectively limiting the RAM blocks used to around 50% of the capacity lowers errors to at least a level where VM downtimes don't (or shouldn't) occur. But it's not okay - it's not a long-term viable procedure nor is it a replacement for any change. Just a stop-gap solution to avoid having the VMs offline and falling periodically. No data is at risk, the errors are all corrected as well, but we're watching this one.

EDIT: nope, it's not right, just locked up again; we're preventively stopping all VMs at Alpha1 for security reasons.

cservers

Okay, this time hopefully for good stability-wise: after a long journey and hard work, Alpha1 Amsterdam is back online with all VMs, and all pending orders for Alpha1 were fulfilled.

The caveat for AS214481 continues to apply, so we're rereouting to Hop179 in the meantime as a fallback, limiting things to 1 Gbps.

The server, however, is now stabilized temporarily, with several management actions taken on our end:

• we're putting all VM loads on the remaining working RAM, forcing them to never go to the defective module, deliberately;
• several RAM contention management measures were applied on our end to ensure this would work, the most visible of which will be a temporary and one-off 20% balooning, to ensure contention/shared memory and some added stability/uptime, for all users with 936 MiB / 1GB RAM or more - those with the 512MB plans already have little of it, we're leaving them at 0;
• ZFS ARC (cache for the internal filesystem we use) was limited to the minimum possible, as it can't be contained to exclude a single RAM module, and this will mean disk speeds will be lower for now in tradeoff for the natural stability that brings on RAM access;
• tests were done pre and post-raise of the VMs, and naturally because we're not using the defective module, we're seeing 80x less errors in runtime, and a satisfatory level of errors at present which ensures peace of mind for everyone.

We're also suspending temporarily the sales for 6GB and 8GB RAM plans for Alpha1.

We'll continue to work with the upstream to fix both technical faults occurring on their end. As soon as we are able to ensure a normal service level again, things will get back to normal on all fronts.

cservers

RAM replaced at Alpha1 with zero errors, server 100% working.

As soon as we get the connectivity with AS214481 up and running again speeds will improve in accordance.

2423750524

Hello, when will the server speed of Alpha1 Amsterdam be restored? The speed to various locations seems to be a bit slow now

cservers

@2423750524 said:
Hello, when will the server speed of Alpha1 Amsterdam be restored? The speed to various locations seems to be a bit slow now

Hey! IPv4 had already been restored with 10 Gbps at the ASN - we have been waiting on the upstream for the IPv6 session to go accordingly restored as well, and that one's still at 1 Gbps for now.

cservers

Support over AI will get a major overhaul and improvement, with a different model: AI starts to be the intermediary, not the final destination, and will start to be humanly supervised on the support channels.

Also, all Live Chat conversations will start to have a reference assigned, just like they were a ticket, for the sub-12 USD customers.

More on that to be divulged later today (08/10).

For the same reason, you may experience today several periods of unavailability and instability on the Live Chat and the ticketing section, while we implement these changes.

This is one of the few relevant occasional painpoints with our services that are remaining - that ends today.

mioakash

Hi @cservers,
My FullVPS-1024 Essential (#6849) is Active, but I can't start the VPS or install an OS. Both actions return EK errors.
The support bot acknowledges it's an infrastructure issue but won't open a ticket, saying I'm not eligible for human support.
I paid €10 with a coupon, but the regular annual price was over €12. I saw your earlier post confirming that FullVPS-1024 should be eligible for support.
Could you please look into this and help get my VPS working?
Thanks!

kf5ydu

My renewal is only applying the top40 promo code I initially used towards half of my order. Can you please assist with this?

kf5ydu

@kf5ydu said:
My renewal is only applying the top40 promo code I initially used towards half of my order. Can you please assist with this?

If it helps here is the original invoice.

cservers

@mioakash said:
Hi @cservers,
My FullVPS-1024 Essential (#6849) is Active, but I can't start the VPS or install an OS. Both actions return EK errors.
The support bot acknowledges it's an infrastructure issue but won't open a ticket, saying I'm not eligible for human support.
I paid €10 with a coupon, but the regular annual price was over €12. I saw your earlier post confirming that FullVPS-1024 should be eligible for support.
Could you please look into this and help get my VPS working?
Thanks!

Hello! Send us the e-mail or some data associated with the account via DM and we'll take a look. The Live Chat has been having some changes...

@kf5ydu said:
My renewal is only applying the top40 promo code I initially used towards half of my order. Can you please assist with this?

We've corrected all invoices with this error, including yours (a total of 3 were affected), and also corrected the code so that it doesn't happen again. Should be better now.

kf5ydu

@cservers said:

@mioakash said:
Hi @cservers,
My FullVPS-1024 Essential (#6849) is Active, but I can't start the VPS or install an OS. Both actions return EK errors.
The support bot acknowledges it's an infrastructure issue but won't open a ticket, saying I'm not eligible for human support.
I paid €10 with a coupon, but the regular annual price was over €12. I saw your earlier post confirming that FullVPS-1024 should be eligible for support.
Could you please look into this and help get my VPS working?
Thanks!

Hello! Send us the e-mail or some data associated with the account via DM and we'll take a look. The Live Chat has been having some changes...

@kf5ydu said:
My renewal is only applying the top40 promo code I initially used towards half of my order. Can you please assist with this?

We've corrected all invoices with this error, including yours (a total of 3 were affected), and also corrected the code so that it doesn't happen again. Should be better now.

Thank you so much! That worked and I was able to renew my plan.

I have a support ticket open for another server that I was hoping you could look into regarding adding additional IPv6 addresses.

Ticket 3612 for vps-6609

2423750524

Is Ashburn's server offline again?

kf5ydu

Still haven't heard anything back on Ticket 3612 for vps-6609

cservers

@kf5ydu said:
Still haven't heard anything back on Ticket 3612 for vps-6609

There is some backlog on the tickets this week due to the focus on multiple networking and automation improvements - sorry for that.

At the moment, these are:

• Stability and networking quality improvements in Ashburn through multiple technical changes to the network endpoint of Ashburn;
• We have started peering at an IXP for the first time, Frys-IX, with 10 Gbps, and with more to come;
• General network arrangements to improve intercommunication between multiple network endpoints, now all of them IPv6-based, and with endpoints with general increases (after optimizations) around +1-2 Gbps extra;
• We have started having transit at Frys-IX from HE, also 10 Gbps, over IPv6, and started to give more relevance to HE-based routes;
• General networking changes to concentrate more traffic primarily into Amsterdam, instead of Coventry, and to further tune and expand peerings accross the ASN;
• Improvements on IPv4 handling at Ashburn, including sorting out of a long-standing bug with Google's pinging which was going to Coventry and back;
• Live Chat is with a (still) closed beta and more delayed than originally expected, now expected between today and tomorrow, to allow for several controlled management of accounts and services - service upgrades, account credit invoices, general VPS operations, and general billing operations. E-mail funneling will also start to be partially automated soon, and agents at the Live Chat will be able to report back to the user on these topics via IMAP checking.
• Live Chat now has not 1, but six underlying AI models just for handling this service, improve uptime and avoid errors: one primary and one fallback agent, designed for all steps necessary (from writing to reviewing to authorizations), all from different makers altogether. All of them are done with ZDR and located with US or EU endpoints, and all of them aim to improve response quality and provide fast answers at the same time when applicable.

These were just over the last 5/6 days.

Amsterdam is now our primary hub for interconnections in mainland Europe.

cservers

Some further news:

• Live Chat has now a level of management for accounts and services. When a given issue exists at the Client area of EagleKey, but the hypervisors continue to operate, any user can now simply go to the Live Chat, authenticate themselves, and request power operations to their VM, or if necessary, full reinstalls. Billing is also now handled through the Live Chat for essential invoice adjustments. These are, in total, 14 new functions; the scope of these will be continuously expanding.
• Original ticket backlog was cleared, all pending issues until 19-10 were sorted out.

And regarding EagleKey:

• More than 290 bugs were corrected over the last 11 days. EagleKey is now at version 3.16.
• EagleKey now introduces Keybinds: available for all PC/Mac platforms, confirmed as working on Chromium and Firefox-based browsers, these allow users that only use the keyboard to operate the VPS platform, on what we believe is either a first or among the first panels to allow it. Several technical users like to operate their systems like that, without a mouse, and there's also the accessibility side of it where multiple users can't use a mouse at all - and if VMs are primarily CLI-focused, it doesn't make sense to have a whole VPS platform operating without catering to their primary use form. It's also much faster than using the mouse.
• Two operation modes for Keybinds: hold Alt (MacOS: Option) while navigating the different pages and sections, or hold-and-release Alt and then simply click on the letters or numbers belonging to each option. Works on everything, including VNC and console access, and it's very fast. Want to end operating that keyboard mode? Just release Alt if you were holding it, otherwise just click it again or change the page, and done. All of these instructions are intuitively shown on-screen as well.
• The Lite Mode was improved and has new functions to have it at greater parity with the full Client Area. And yes - this includes Keybinds.

Scioner

@cservers it seems like bot is down, as well as IPv4 for Zeta.9. And there's no info about it on the status page.

rcy026

@Scioner said:
@cservers it seems like bot is down, as well as IPv4 for Zeta.9. And there's no info about it on the status page.

I confirm this.
IP4 has been down for days and the chat bot just says "temporary error, please contact support". Kind of ironic since the only way to contact support is via the chat bot.

2423750524

The node Alpha1 Amsterdam seems to be down, and it cannot be found in their infrastructure nodes at present

Scioner

@2423750524 said:
The node Alpha1 Amsterdam seems to be down, and it cannot be found in their infrastructure nodes at present

There's ongoing issue with Alpha1 https://portal.cfld.uk/status

cservers

@rcy026 said:

@Scioner said:
@cservers it seems like bot is down, as well as IPv4 for Zeta.9. And there's no info about it on the status page.

I confirm this.
IP4 has been down for days and the chat bot just says "temporary error, please contact support". Kind of ironic since the only way to contact support is via the chat bot.

The fallback is probably not working as it should, but there are tickets being submitted. We'll understand what is causing these errors and sort them out at the chatbot as fast as possible.

As for IPv4 at Zeta.9, we'll also take a look and in the process understand the same thing for Ashburn.

Sorry for these issues.

Scioner

@cservers said:

@rcy026 said:

@Scioner said:
@cservers it seems like bot is down, as well as IPv4 for Zeta.9. And there's no info about it on the status page.

I confirm this.
IP4 has been down for days and the chat bot just says "temporary error, please contact support". Kind of ironic since the only way to contact support is via the chat bot.

The fallback is probably not working as it should, but there are tickets being submitted. We'll understand what is causing these errors and sort them out at the chatbot as fast as possible.

As for IPv4 at Zeta.9, we'll also take a look and in the process understand the same thing for Ashburn.

Sorry for these issues.

Tbf, I'm fine with some hiccups. It's a dirt cheap service, and it's really good while it works.

But being in the dark for a few days, while bot isn't working and IPv4 isn't working as well is sucks. Any message (even something vague like "there's issues, we are aware") on the status page could be really helpful honestly.

PS: Just out of curiosity. From time to time I'm being rate limited by CF gate while trying to access client area. I am absolutely sure there's no one beside me who uses this IP. And I'm absolutely sure I'm not doing anything harmful.

Wild guess: I'm usually trying to open client area if there's some issues. And in case EagleKey can't answer in the reasonable time - it keep sending request. So CF flagged my IP as harmful, therefore rate limit.

edmarhub

The KVM Netherlands is also down like 2days now already!

Scioner

@edmarhub said:
The KVM Netherlands is also down like 2days now already!

Oh... I'm really sorry, but sometimes I wonder if people really capable of reading.

Just three messages ahead. Link to the status.

cservers

@Scioner said:

@cservers said:

@rcy026 said:

@Scioner said:
@cservers it seems like bot is down, as well as IPv4 for Zeta.9. And there's no info about it on the status page.

I confirm this.
IP4 has been down for days and the chat bot just says "temporary error, please contact support". Kind of ironic since the only way to contact support is via the chat bot.

The fallback is probably not working as it should, but there are tickets being submitted. We'll understand what is causing these errors and sort them out at the chatbot as fast as possible.

As for IPv4 at Zeta.9, we'll also take a look and in the process understand the same thing for Ashburn.

Sorry for these issues.

Tbf, I'm fine with some hiccups. It's a dirt cheap service, and it's really good while it works.

But being in the dark for a few days, while bot isn't working and IPv4 isn't working as well is sucks. Any message (even something vague like "there's issues, we are aware") on the status page could be really helpful honestly.

PS: Just out of curiosity. From time to time I'm being rate limited by CF gate while trying to access client area. I am absolutely sure there's no one beside me who uses this IP. And I'm absolutely sure I'm not doing anything harmful.

Wild guess: I'm usually trying to open client area if there's some issues. And in case EagleKey can't answer in the reasonable time - it keep sending request. So CF flagged my IP as harmful, therefore rate limit.

Yeah, we understand it's inconvenient... we're doing all we possibly can for these.

Regarding the bots, we've done some further changes on the Live Chat side of things and it should be much better. As of this moment we've tested the chat and it's working correctly and reasonably fast - it does take a few seconds to get messages on screen but then these are more focused, so things should be better on that department.

We do have a message on the status page - did you mean having that on the Client Area as well? That is interesting.

As for that rate limitation, yes, it's not you doing anything harmful, don't worry - we had some DDoS a couple of months ago and these rate-limits were originally decided and tightened based on these attacks. We've adjusted that rate-limit with +33% and you shouldn't be hitting that (or nearly as much) now.

Btw, regarding this topic in Amsterdam - since we're traversing the weekend, we're considering to provide an alternative server with approximate specs in the meantime, while this issue isn't sorted out. IPv6 would always be available via AMS, IPv4 would only be partially via AMS with the remainder going via Coventry (+8ms).

rcy026

@cservers said:

We do have a message on the status page - did you mean having that on the Client Area as well? That is interesting.

My ip4 was down for several days and there was no mention of that anywhere, not even the status page.
Showing known problems as a message in the client area is not a bad idea, I really cant understand why this is not a nobrainer for every provider out there.

cservers

Okay, some news regarding Amsterdam, and being entirely open here:

• The upstream provider for that offer, Chunkserve, has not provided us with any further details or a solution since 23-10-2026 and has effectively not sorted out this issue in 7 days, since 21-10-2026.

• This mixture of communication difficulties we're feeling and lack of solutions from the upstream is absolutely unacceptable for us, and absolutely not par to the standard of service C-Servers wants to provide, in this case entirely due to a bug on the original hardware provided by the upstream, that apparently wasn't subject to testing and fixing prior to selling, something on the competence of the upstream.

• The track record for this server is also not acceptable, as a RAM module was defective at this server earlier on. The replacement occurred, but took more days than what we'd desire.

As such, we cannot continue with this, and are moving away from Chunkserve for Amsterdam services, effective on 28-10-2026.

After a very thorough vetting and search, and on the context of a inflated market with correspondent pricing to match making things harder, we are pleased to say that servers are going to be reprovisioned with a new upstream shortly on similar terms as to those originally dealt. There will be some differences:

• The processor will not be a Xeon Gold 6132, but a Xeon Gold 6138. Despite our best efforts, it was not possible to provide the exact CPU, but at least it's from a comparable family class.
• To compensate for that difference, two things will be better: the disk, which will now be upgraded to a NVMe SSD and not a SATA SSD (it's also newer!), and Internet speed, which will be updated from 2.0 to 2.5 Gbps, and it's expected to provide better latency to Central Europe.
• The underlying server brand also changes: it will not be a Lenovo, but a HP Gen10, the same exact family model we will be deploying on the upcoming Alpha3 Amsterdam.
• In order to deploy this new upstream and terms, and since there are two upgrades to one downgrade, pricing will stay the same for existing and new customers, and C-Servers had also to accept a 33% profit margin reduction with the accepted offer from the new upstream. This means that, effectively, we will be losing some money in comparison to the previous upstream as we will not be passing the costs to customers, in exchange for a longer-term partner, much more stable terms and hardware, and a better experience all along for both parties.

Whenever existant, original server backups from Alpha1 will be deployed for Alpha2.

Alpha2 Amsterdam is expected to enter into production in the next 24/48 hours and we do sincerely apologize for this.

jaehyun1122

Is today C-Servers' deadpool day? 💀

cservers

@jaehyun1122 said:

Is today C-Servers' deadpool day? 💀

Nope, those 4 machines have returned around 40 minutes ago. We wouldn't be designing an uptime counter to deadpool on the following day, would we?

And speaking of news: Alpha1 has actually returned and the upstream provider for Alpha2, contrary to what is on their own page, has refused BGP sessions for the server. The plot chickens. We're doing some tests and running a couple of errands and deciding on what to do today before we raise the VMs again.

Taking on the suggestions of @Scioner and @rcy026, we've also started to notify whenever a server is down because its hypervisor is down on the Notifications area, and putting that as well on the Uptime page.

jaehyun1122

@cservers said: those 4 machines have returned around 40 minutes ago.

cservers

Alpha1 now up and running again. Alpha2 was decided not to enter into operation due to the last-minute issues with that upstream preventing an adequate level of service and the utmost priority being to correct the issue and bring servers back online (plus server specifications were different and it could cause billing issues).

We have requested directly Chunkserve for BMC access to the system with an administrative user so we can operate and correct future issues like these at hand. This was a FRB2 timer racing condition directly correlated with a delay on virtual USB validation, hence the B4 error stepping. It's an internal configuration error on something that should have been a correct default configuration from Lenovo, not even C-Servers or Chunkserve.

Scioner

@cservers said:
Alpha1 now up and running again. Alpha2 was decided not to enter into operation due to the last-minute issues with that upstream preventing an adequate level of service and the utmost priority being to correct the issue and bring servers back online (plus server specifications were different and it could cause billing issues).

We have requested directly Chunkserve for BMC access to the system with an administrative user so we can operate and correct future issues like these at hand. This was a FRB2 timer racing condition directly correlated with a delay on virtual USB validation, hence the B4 error stepping. It's an internal configuration error on something that should have been a correct default configuration from Lenovo, not even C-Servers or Chunkserve.

Btw, two months ago I could just said it's a hiccup and it's fine, but for the last month topic on OGF about Chunkserve become... how should I say it... increasingly concerning.

They were fine before. Delayed answers, but fine. But for the last month or so it became shitshow of not answered tickets and not resolved issues. Not sure where it will go.

It's obviously yours and only yours choice to keep or not to keep working with them, but there's red signs.

Sad thing is I have two VPS with them.

PS: Thank you for detailed reports on the status page

cservers

@Scioner said:

@cservers said:
Alpha1 now up and running again. Alpha2 was decided not to enter into operation due to the last-minute issues with that upstream preventing an adequate level of service and the utmost priority being to correct the issue and bring servers back online (plus server specifications were different and it could cause billing issues).

We have requested directly Chunkserve for BMC access to the system with an administrative user so we can operate and correct future issues like these at hand. This was a FRB2 timer racing condition directly correlated with a delay on virtual USB validation, hence the B4 error stepping. It's an internal configuration error on something that should have been a correct default configuration from Lenovo, not even C-Servers or Chunkserve.

Btw, two months ago I could just said it's a hiccup and it's fine, but for the last month topic on OGF about Chunkserve become... how should I say it... increasingly concerning.

They were fine before. Delayed answers, but fine. But for the last month or so it became shitshow of not answered tickets and not resolved issues. Not sure where it will go.

It's obviously yours and only yours choice to keep or not to keep working with them, but there's red signs.

Sad thing is I have two VPS with them.

PS: Thank you for detailed reports on the status page

We do understand these concerns, and it's something naturally important to monitorize further - we'll stay vigilant on this.

We will be keeping regular backups of those servers elsewhere, so that they can be deployable on another dedicated server in a reasonable timeframe (much more reasonable than these days), should it be needed. Over time, we will take a look how things evolve, and in any case look forward to migrate these services to our own bare-metal in AMS (keeping the IPs, the data, and everything else).

As you may imagine, this is something we don't want to happen again - these have been truly hellish days - but we need to get some ponderation, some distance to the present events, in order to offer a better approach, something much more done our way. The top priority at this moment was for us to get things back online and stable; next, we'll execute prevention.

cservers

Sorry for the double post, but this one is good news.

As it is now reasonable to reinstate a promotion when the issues are resolved, two coupon codes are now active again:

• FULL15 (15% recurring discount) is now available again and extended until 15/11/2026
• OCT30 (30% recurring discount) is active again from today until 10/11/2026.

snake

@cservers said:

• OCT30 (30% recurring discount) is active again from today until 10/11/2026.

too generous!

friendlyguy12d

Hello please check ticket #4022.