Changelog
Page 4 of 4.
The control plane records node state far less often
TL;DR: The control plane now saves each node's peer-discovery details only when they change, instead of on every heartbeat, cutting its routine database writes about sevenfold. Delivery is unchanged; two rare recovery cases behave slightly differently.
Card titles on the Workloads page are readable again
TL;DR: A styling conflict made some portal headings near-black on a dark background, most visibly the Content Delivery card title on the Workloads page. All 18 affected elements are fixed, and a test stops the conflict coming back.
Sites deployed from CI now appear in the portal
TL;DR: Sites published from CI or the command line served normally but left the portal's Files and Deployments tabs empty, and their traffic was missing from project analytics. New deploys now show up in the portal just as portal deploys do.
Payout requests now respect the minimum balance
TL;DR: The Earnings page offered a payout on any balance above zero, even though payouts have a minimum. Requests are now checked against the minimum, and the page tells you how far your balance is from it.
Docs and Support are one click away in the portal
TL;DR: The portal's top bar has a new Resources menu with links to Docs and Support. It opens the guides for whichever view you're in, Node Operator or customer, in a new tab. Available on desktop.
A new account menu and an always-visible view switcher in the portal
TL;DR: Your profile, account settings and sign-out now sit in a menu under your name, and the switch between the Node Operator and customer views is always shown. The Refer page also links the referral program terms directly.
Dashboard cards now open Earnings, the Leaderboard and your profile
TL;DR: The Earnings & Payouts, Local Leaderboard and Performance Index cards on the dashboard were dimmed and marked "Coming soon", though all three features were already live. Each card is now a link to its page.
Node details no longer reset after platform updates
TL;DR: Each platform release cleared details operators had entered about their nodes — hardware, ISP and connection speed — along with badges and activity streaks. Releases now leave them intact.
Refer other operators from the portal
TL;DR: Operators now have a personal referral link and a Refer page in the portal. When someone you refer keeps a verified node online for 60 days, you both earn a bonus. There's no cap on referrals.
Sites stay up when an edge node's credentials are rejected
TL;DR: When the control plane rejected an edge node's credentials, the node kept retrying them, and sites it served returned "domain not configured". Nodes now re-authenticate within seconds, and the visitor who triggers recovery still gets their page.
Static sites are now cached by browsers and crawlers
TL;DR: Sites served from their own domain were sent with no-cache on every file, so each visit re-downloaded everything. Build assets are now cached for a year, and pages revalidate in a single cheap round trip.
Healthy nodes no longer show single-digit uptime
TL;DR: When a node's activation date was missing, its uptime was measured against a full 30 days, so a node with two perfect days showed 6.67%. Uptime is now measured against the time we actually observed the node.
Installing the edge node on Windows now works end to end
TL;DR: The Windows installer failed to download the edge node, and beyond that registered a service that couldn't start while still reporting success. Installing, starting and uninstalling now all work, and failures are reported as failures.
Subscribe: all products · CDN · Edge Node · CLI · Portal