new load balancing ui

[ncrouch-cflare]

changelog for new LB UI

Summary

changelog for LB UI

Screenshots (optional)

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[windsurf-bot]

Looks good to me 🤙

💡 To request another review, post a new comment with "/windsurf-review".

[Ky96262]

Dear Kody, ***@***.*** Thank you for announcing the new Load Balancing UI! I’m really excited about the centralized account-level management and the addition of Private Load Balancers. I believe these enhancements will significantly improve our user experience. Looking forward to exploring these changes! Best regards, [Your Name]

-------- Orijinal E-posta----------- İtibaren: Kody Jackson ***@***.***> Gönderilmiş: 4 Haziran 2025 21:10:06 GMT+03:00 İle: cloudflare/cloudflare-docs ***@***.***> Bilgi: Subscribed ***@***.***> Ders: Re: [cloudflare/cloudflare-docs] new load balancing ui (PR #22909) @kodster28 commented on this pull request.

@@ -0,0 +1,29 @@

+--- +title: New Account-Level Load Balancing UI and Private Load Balancers +description: You can now manage all of your load balancers in one place with the new Load Balancing UI. +date: 2025-06-04 +--- + +We're excited to announce a significant enhancement to the Cloudflare Load Balancing experience! We've launched a redesigned user interface, now centralized at the **account level**, and introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot. ```suggestion We've made two large changes to load balancing: - Redesigned the user interface, now centralized at the **account level**. - Introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot. ```

…

-- Reply to this email directly or view it on GitHub: #22909 (review) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[holopin-bot]

Congratulations @ncrouch-cflare, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cmbi9yelp572907juc3blv77t

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!

[Ky96262]

***@***.***

-------- Orijinal E-posta----------- İtibaren: ncrouch-cflare ***@***.***> Gönderilmiş: 4 Haziran 2025 21:16:19 GMT+03:00 İle: cloudflare/cloudflare-docs ***@***.***> Bilgi: Subscribed ***@***.***> Ders: Re: [cloudflare/cloudflare-docs] new load balancing ui (PR #22909) @ncrouch-cflare commented on this pull request.

+

+We've made two large changes to load balancing: +- Redesigned the user interface, now centralized at the **account level**. +- Introduced [**Private Load Balancers**](/load-balancing/private-network/) to the UI, enabling you to manage traffic for all of your external and internal applications in a single spot. + +This update streamlines how you manage load balancers across multiple zones and extends robust traffic management to your private network infrastructure. + + + +**Key Enhancements:** + +- **Account-Level UI Consolidation:** + + - **Unified Management:** Say goodbye to navigating individual zones for load balancing tasks. You can now view, configure, and monitor all your load balancers across every zone in your account from a single, intuitive interface at the account level. + + - **Improved Efficiency:** This centralized approach provides a more streamlined workflow, making it faster and easier to manage both your public-facing and internal traffic distribution. I think 1 speaks more to the overall experience, but 2 calls out specifically the internal traffic distribution

…

-- Reply to this email directly or view it on GitHub: #22909 (comment) You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>