Scheduled Maintenance: Linux Kernel Upgrade – May 20–22, 2026

Tweet

Hello everyone,

We will be performing a Linux kernel upgrade across all Ultra.cc nodes over the course of three days, starting this Wednesday, May 20. The upgrades will be carried out in batches, with a maintenance window of 09:00 AM – 09:00 PM UTC each day.

During this timeframe, each individual node will undergo an upgrade of the Linux kernel, which will require a reboot once the kernel upgrade is complete.

UPGRADE SCHEDULE

• Batch 1 – Wednesday, May 20, 2026
• Batch 2 – Thursday, May 21, 2026
• Batch 3 – Friday, May 22, 2026

You can check which batch your node is in below:

Batch 1 (May 20): zebra, matrix, ocean, baron, quest, topaz, frost, botanic, iceberg, joker, karma, pixel, dagger, unity, vapor, gorgon, laser, lumen, omega, citadel, flux, gizmo, tulip, pulse, axiom, reindeer, oak, peak, maze, aura, sage, apex, cactus, hive, huck, aiko, keiko, fox, katong, hen, manitoba, diamond, dragon, wolf, terra, thefiend, tix, zed, lua, zen, dog, tofino, palawan, luna, sol

Batch 2 (May 21): jett, blaze, nexus, aero, thor, yukon, calgary, spider, pyramid, nunavut, merlion, obelisk, skyron, winnipeg, shadow, huron, cupcake, niagara, bedok, ghost, nebula, orbit, nova, niobe, eclipse, gandalf, infinity, comet, solaris, galaxy, proton, lw900, lw901, lw902, lw903, aglaia, antares, apoc, apollo, arcturus, ares, atlas, canopus, capella, chaos, cypher, deimos, delia, deneb, eos, erato, eros, hades, hebe

Batch 3 (May 22): hera, hermes, hyperion, ismene, janus, kallisto, larissa, leda, leto, lycus, melete, midas, mimas, moon, morpheus, myles, neo, nephele, nyx, oberon, oblivion, oracle, orion, pan, phoebe, pistis, pluto, pollux, priam, psyche, spica, theia, titan, trinity, triton, vega, zion, rigel, castor, hadar, altair, polaris, onyx, spinel, jasper, agate, crux, amber, axinite, beryl, lyra, emerald, oasis, epidote

IMPORTANT: WHAT TO EXPECT AFTER YOUR NODE REBOOTS

Please be aware of the following once your node has been rebooted:

1. Applications in a stopped state may be automatically restarted. Please check your services after the maintenance window if you have apps you intentionally kept stopped.

2. Custom-installed applications that are not configured as a systemd service will not start automatically. You will need to manually restart these yourself after the reboot.

We expect the impact to be minimal and brief. If you experience any issues after the maintenance window for your batch, please don't hesitate to reach out to our support team.

Thank you for your patience.

Best regards,

Team Ultra