Since yesterday, api[dot]openai[dot]com resolves to 172.x.x.x addresses globally, regardless of the DNS provider (1[dot]1[dot]1[dot]1, 8[dot]8[dot]8[dot]8, 9[dot]9[dot]9[dot]9). Result: OpenAI services are inaccessible in affected regions. Test results: nslookup api[dot]openai[dot]com 1[dot]1[dot]1[dot]1 → Returns 172.66.0.243 traceroute api[dot]openai[dot]com → Traffic gets stuck in Cloudflare’s network OpenAI’s status page reports no issues, but this DNS resolution seems incorrect.
What steps have you taken to resolve the issue?
Tested with different DNS providers (1[dot]1[dot]1[dot]1, 8[dot]8[dot]8[dot]8, 9[dot]9[dot]9[dot]9) – same result everywhere.
Used VPNs in multiple countries (EU, US) – issue persists globally.
Checked OpenAI’s status page – no incidents reported.
Looked for OpenAI support options – no direct way to report this problem.
What feature, service or problem is this related to?
DNS records
What are the steps to reproduce the issue?
Run nslookup api[dot]openai[dot]com 1[dot]1[dot]1[dot]1 → It resolves to 172.66.0.243
Run traceroute api[dot]openai[dot]com → Traffic gets stuck in Cloudflare
OpenAI services are completely unreachable in affected locations
172.66.0.243 is a Cloudflare IP address, it’s not in the private IP range (which is 172.16.0.0 to 172.31.255.255). Your screenshot shows the traceroute reaches the destination so that’s ok.
I don’t use the API myself, but I can reach it ok. Which locations do you think are affected?