Logbook - 2022-05-13

Summary

The May 13, 2022 log records Fly.io changes and fixes from the preceding week, spanning infrastructure capacity, account self-service, API maintenance, documentation, and customer-facing behavior. New servers in syd, iad, and dfw, plus three workers in ord, addressed capacity shortages that had caused provisioning or deployment problems. The API moved to Ruby 3.1, with anticipated performance and security-patch benefits, while an internal Elixir UI guide and clearer app and machine name validation errors aimed to reduce development and debugging friction. Operational work permanently disabled consul-templaterb on fly-proxy nodes and fixed a fly-proxy memory leak, giving those nodes more CPU/RAM headroom; an MTU workaround was intended to improve IPv6 tunnel connectivity, while a larger fix remains. Other fixes covered account-deactivation guidance, personalized support email addresses for paid plans, billing, volume metrics, forum registration, and a minor “X daysago” display error.

Takeaways

1. 1

   New servers were provisioned in syd, iad, and dfw, and three workers were added to ord after capacity shortages caused deployment or provisioning problems.

2. 2

   The API was deployed with Ruby 3.1, while permanently disabling consul-templaterb and fixing a fly-proxy memory leak provided nodes with more CPU/RAM headroom.

3. 3

   An MTU workaround addressed IPv6 connection errors affecting tunnels and DSL users; a larger fix was still expected to require more work.