UptimeUptime Wiki

Uptime v0.1.11 (Early Access)

First update since launch, straight from your feedback: garage pacing and money, CPU contention that was crying wolf, and a batch of placement and console fixes. Keep it coming on Discord: discord.gg/V7YVmA2Fux.


Economy and pacing

  • The garage now pays properly. Each customer is worth more while you are still in the garage, so the opening funds itself on per-customer revenue instead of forcing you to onboard a crowd. Later sites settle back to the standard rate as your scale grows.
  • New customers arrive at a steadier pace in the garage. The intro faucet was running about twice too fast and could bury a garage in dozens of tenants before you had found your feet. It is now paced so the opening builds instead of floods, and the advance-to-basement goal is a milestone you grow into rather than blow past.

Contention and incidents

  • CPU contention alerts no longer pile up or cry wolf. A "CPU contended" incident now opens only when a host is genuinely over capacity and a customer on it is actually breaching its service level. A host that is busy but keeping up is shown as a state on the host console, not raised as an incident.
  • Contention incidents now clear on their own once the host recovers, load drops, or you migrate work off it. Previously they were opened but never resolved, so they accumulated forever.
  • Contention severity now reflects real impact (money at risk and service level), not how long the alert has been open. A minor, long-standing contention no longer escalates itself to the top "existential" severity.
  • Incident headlines now use the name you gave a server. A renamed host reads as "Server01 CPU contended" instead of "host 27," so you are sent to the box you actually named.

Placement and migration

  • New workloads now balance across your fleet. New virtual machines are placed on the least-loaded eligible host instead of piling onto the first one that fits, so adding a server actually spreads load onto it rather than new customers landing on an already-busy host.
  • You can now migrate a virtual machine onto a host that still has room under its overcommit ceiling. The migration check used to ignore the overcommit dial and measure against raw physical CPU, so it refused hosts that clearly had space to sell.
  • A migration that cannot be placed is no longer silent. If there is no host with room (or the target is offline or incompatible), you get a clear message and the machine stays exactly where it was, instead of appearing to move and then snapping back.

Host console

  • The CPU resource bar now shows live load (actual demand against physical cores) rather than how much is reserved, so a genuinely busy host reads high and a packed-but-idle host reads its real, lower load.
  • The workloads list now includes a "Control plane + host services" row. The platform's own CPU use (the control plane and per-host agents) used to be invisible, which made the CPU figure look like it disagreed with the listed workloads.

On this page