VoxiHost - Notice history

All systems operational

Notice history

2025/11

Node Reboot for Guaranteed CPU Performance Baseline
  • Update
    2025/11/04 at 23:12:00UTC
    Update
    2025/11/04 at 23:12:00UTC

    Hey, Daniel here!


    I wanted to add a small additional note regarding the maintenance i performed. Today, I observed some weird behavior with the CPU frequency on the server node specifically, the clock speed was dropping dramatically, sometimes as low as 400 MHz, before instantly jumping back up to 4 GHz+.

    I traced this issue to the default Energy Performance Preference (EPP) settings, which were aggressively trying to save power during minimal idle times. While good for laptops, on a server with many running VPS instances, this rapid frequency oscillation was causing a noticeable increase in latency and unpredictable performance.

    I decided to fix this immediately, performing the necessary kernel changes overnight to only affect a small customer base during EU hours.

    As my goal is to guarantee the best, most consistent performance possible for all our VPS customers, I have overridden the default power profile. The server is now locked to a high-performance profile with a guaranteed minimum baseline of 4.2 GHz, ensuring zero lag and maximum stability for your services.

  • Completed
    2025/11/04 at 23:11:00UTC
    Completed
    2025/11/04 at 23:11:00UTC

    The scheduled infrastructure maintenance is now complete. The Node's CPU control settings were updated successfully.

    Maintenance Summary

    The system's power-saving profile was switched to a guaranteed high-performance profile.

    • Minimum Frequency (Baseline): 4.2 GHz

    • Maximum Frequency (Turbo): 5.759 GHz

    Benefit Summary

    • Zero Latency Jitter: The deep idle state was eliminated, ensuring services receive instantaneous power when requested.

    • Predictable Consistency: The Node now maintains a 4.2 GHz baseline, minimizing performance variance across all virtual machines.

  • Update
    2025/11/04 at 23:10:00UTC
    Update
    2025/11/04 at 23:10:00UTC

    We are making sure that configuration was applied correctly, all VPS servers are back working.

  • In progress
    2025/11/04 at 23:00:01UTC
    In progress
    2025/11/04 at 23:00:01UTC
    Maintenance is now in progress
  • Planned
    2025/11/04 at 23:00:00UTC
    Planned
    2025/11/04 at 23:00:00UTC

    Impact: Users will experience a brief, single service interruption as the server node performs a necessary reboot.

    Reason for Reboot: We are updating the server's kernel configuration to switch the CPU from an energy-saving profile to a performance-guaranteed profile. This crucial change ensures the system strictly maintains a 4.2 GHz minimum clock speed for predictable, low-latency VM performance. Crucially, the system retains the ability to dynamically boost up to 5.7 GHz when needed for demanding tasks.

    We apologize for the brief downtime and are committed to maximizing the reliability of your services.

2025/10

NeoProtect, outage
  • Postmortem
    UTC
    Postmortem

    A major service interruption occurred starting at 21:45:00 on October 30th. The root cause was an external, critical failure at our former DDoS Protection vendor, NeoProtect Remote Shield.

    NeoProtect's upstream provider, CDN77 / Datapacket, disabled all active BGP sessions towards the NeoProtect network, instantly causing all services protected by their Remote Shield to become unrouteable and unavailable.

    Our resolution involved an emergency network migration:

    1. We attempted to route raw network traffic via Amsterdam as a temporary fix, but complex routing issues prevented immediate deployment overnight.

    2. We successfully established contact with a new DDoS Protection partner, PletX.net, and performed a full, critical network swap.

    3. Service was fully restored at 13:53:24 on October 31st.

    Outcome: VoxiHost has permanently migrated to PletX.net for DDoS protection as NeoProtect has since discontinued its Remote Shield service. We are implementing a raw-network standby failover with our DC provider to prevent future external vendor failures from causing extended downtime.

  • Resolved
    UTC
    Resolved

    This incident has been resolved. As from now on we will be using PletX.net DDoS Protection. Soon there will be postmortem about this incident and more information for the summary.

  • Monitoring
    UTC
    Monitoring

    We are currently, on PletX protection & networking. Everything should be back to normal!

  • Update
    UTC
    Update

    We are looking forward into having this issue solved in the morning EU time, we will be trying to get it replaced as soon as possible once PletX team wakes up and can preform the setup. This issue with NeoProtect wasn't expected at all, since their provider pulled a 'plug' on them and disconnected BGP sessions leaving us completely stranded and many other companies.

    We hope for full understanding from our customers, and we will take all important steps to provide compensation & make stuff right after this hard time...

  • Update
    UTC
    Update

    We are awaiting for PletX.net routing & whitelist to be configured, to replace NeoProtect.

  • Update
    UTC
    Update

    Provided information by NeoProtect: "Our Upstream CDN77 / Datapacket has deactivated all BGP sessions towards our network. This results in full downtime of all associated services such as all Remote Shield customers (aside from XC customers in AMS).
    The ETR given by them at this time is "tomorrow", we are trying to get this reconsidered but we do not estimate for reconsideration to happen in our favor."

    We are trying our best to get around this and deploy PletX DDoS Protection with will replace NeoProtect

  • Identified
    UTC
    Identified

    We have identified to be a global outage from NeoProtect

    https://status.neoprotect.net/incidents/kdmtx0wk3h1l

  • Investigating
    UTC
    Investigating
    We are currently investigating this incident.

2025/09 to 2025/11

Next