Google Meet is updating its Enterprise Content Delivery Network (eCDN) rules to improve admin management experiences. These changes primarily affect how custom rules handle overlapping IP ranges. Previously, blocking matches would override allowing matches, regardless of order. The new system evaluates custom rules sequentially from top to bottom, using the first match encountered. This means the order in which IP ranges are listed in custom rules is now critical for accurate matching. Admins should list smaller, more specific IP ranges before larger encompassing ranges. Additionally, the eCDN will now consider all private IP addresses configured on a viewer's device for matching, not just a single prioritized one. The Random peering policy has been renamed to Testing peering policy to better reflect its intended use. Viewers using the Testing peering policy will now appear in the Meet Quality Tool eCDN table. These updates aim to simplify rule management and ensure more predictable behavior. The rollout for these changes begins in October 2025.