Global Traffic Management with Route 53 Geoproximity Routing

Act as an AWS Network Architect. Create a highly sophisticated global traffic engineering blueprint for a latency-sensitive [APPLICATION_TYPE] (e.g., real-time VoIP or multiplayer gaming) utilizing AWS Route 53. Implement complex Geoproximity routing policies designed to steer global DNS queries mathematically based on the user's physical longitude/latitude. You must define a specific [REGION_BIAS] (e.g., artificially expanding the routing polygon of `us-east-2` to absorb traffic from `us-east-1` to reduce compute costs). Define the exact, unforgiving [HEALTH_CHECK_CRITERIA] (e.g., deep string matching on a `/healthz` endpoint) required to trigger instantaneous, automated regional failovers. Conclude by writing a technical justification for implementing the Route 53 Application Recovery Controller (ARC) to override automated routing control states, ensuring absolute manual governance over the blast radius during partial regional network outages.