We experienced a DNS misconfiguration that caused the API to return a 302 redirect, depending on the region. Our internal monitoring service, based in a different region, did not detect the issue immediately. We rolled out monitoring services across all regions to ensure earlier detection in the future.