Create 2025-05-05-private-health-monitoring-methods.mdx (#22216)

* Create 2025-05-05-private-health-monitoring-methods.mdx

* change date

bump date by 1

* Apply suggestions from code review

* tweaks

* Cleanup

* Remove release-notes file

---------

Co-authored-by: Kody Jackson <[email protected]>
Co-authored-by: kodster28 <[email protected]>

Author: ncrouch-cflare

public/__redirects

@@ -23,6 +23,7 @@
 /cloudflare-one/changelog/tunnel/index.xml /changelog/rss/cloudflare-tunnel.xml 301
 /dns/changelog/index.xml /changelog/rss/dns.xml 301
 /fundamentals/changelog/index.xml /changelog/rss/fundamentals.xml 301
+/load-balancing/changelog/index.xml /changelog/rss/load-balancing.xml 301
 /logs/changelog/index.xml /changelog/rss/logs.xml 301
 /magic-cloud-networking/changelog/index.xml /changelog/rss/magic-cloud-networking.xml 301
 /magic-firewall/changelog/index.xml /changelog/rss/magic-firewall.xml 301

src/content/changelog/load-balancing/2025-05-06-private-health-monitoring-methods.mdx

@@ -0,0 +1,17 @@
+---
+title: UDP and ICMP Monitor Support for Private Load Balancing Endpoints
+description: Use UDP or ICMP to monitor the health of your private IP-based applications.
+date: 2025-05-06
+---
+
+Cloudflare Load Balancing now supports **UDP (Layer 4)** and **ICMP (Layer 3)** health monitors for **private endpoints**. This makes it simple to track the health and availability of internal services that don’t respond to HTTP, TCP, or other protocol probes.
+
+### What you can do:
+
+- Set up **ICMP ping monitors** to check if your private endpoints are reachable.
+- Use **UDP monitors** for lightweight health checks on non-TCP workloads, such as DNS, VoIP, or custom UDP-based services.
+- Gain better visibility and uptime guarantees for services running behind **Private Network Load Balancing**, without requiring public IP addresses.
+
+This enhancement is ideal for internal applications that rely on low-level protocols, especially when used in conjunction with [**Cloudflare Tunnel**](/cloudflare-one/connections/connect-networks/), [**WARP**](/cloudflare-one/connections/connect-devices/warp/), and [**Magic WAN**](/magic-wan/) to create a secure and observable private network.
+
+Learn more about [Private Network Load Balancing](/load-balancing/private-network/) or view the full list of [supported health monitor protocols](/load-balancing/monitors/#supported-protocols).

src/content/docs/load-balancing/changelog.mdx

@@ -1,14 +1,54 @@
 ---
 pcx_content_type: changelog
 title: Changelog
-release_notes_file_name:
-  - load-balancing
 sidebar:
   order: 153
 ---
 
-import { ProductReleaseNotes } from "~/components";
+import { ProductChangelog } from "~/components";
 
-{/* <!-- Actual content lives in /src/content/release-notes/waiting-room.yaml. Update the file there for new entries to appear here. For more details, refer to https://developers.cloudflare.com/style-guide/documentation-content-strategy/content-types/changelog/#yaml-file --> */}
+{/* <!-- Actual content lives in /src/content/changelog/load-balancing/. Update the file there for new entries to appear here. */}
 
-<ProductReleaseNotes />
+<ProductChangelog product="load-balancing" />
+
+## 2025-04-15
+
+**Introducing Support for Orange-Clouded Origin Resolution**
+
+Newly created Cloudflare Load Balancers will resolve orange-clouded origin addresses, provided the origins belong to the same account and zone as the Load Balancer. Existing Load Balancers will continue using the current resolution method. If ownership validation fails, the new system falls back to the existing behavior and defaults to a gray-clouded (DNS-only) lookup, typically resolving to anycast addresses.
+
+## 2025-03-13
+
+**Update to Load Balancing analytics**
+
+Load Balancing request rates in analytics may decrease for some customers as an improvement is made to our infrastructure. This decrease in Load Balancing analytics does not indicate a decrease in HTTP requests received.
+
+## 2025-02-20
+
+**Zone name added to Load Balancing API responses**
+
+Load Balancing API responses for Load Balancers now include a `zone_name` property, which provides the name of the zone in the response data.
+
+## 2025-02-10
+
+**Fix for Cloudflare Tunnel Consistency**
+
+Fixes to improve the consistency of Cloudflare Tunnel handling within Cloudflare Load Balancers. These changes ensure more reliable and predictable routing, particularly when tunnels are involved.
+
+## 2025-01-24
+
+**Update to Cloudflare Tunnel Steering**
+
+Introduced changes to the resolution of proxied domains that are backed by Cloudflare Tunnels on the same zone. These changes correct how orange-clouded records are steered to Cloudflare Tunnels via Cloudflare Load Balancers.
+
+## 2025-01-16
+
+**Update to Pool Health Monitoring**
+
+We made changes to how we resolve and monitor proxied origins to assess pool health. Our analysis indicates no impact to customer configurations or operations. Contact customer support if you notice any unexpected behavior.
+
+## 2024-12-20
+
+**Load Balancing with the China Network**
+
+You can now enable load balancers to be deployed to the [China Network](/china-network/). Refer to the [documentation](/load-balancing/additional-options/load-balancing-china/) for more details.