Cloudflare Error 1016 “Origin DNS error” on api.openai.com at 2026-01-07 11:43 UTC

Hi all,

I encountered a repeated Cloudflare Error 1016 (Origin DNS error) when calling the OpenAI API from AWS West Coast servers.

Details:

What I think happened:
Cloudflare edge node(s) failed to resolve the origin DNS, resulting in an undocumented transient failure. The official status page didn’t show an incident at this morning timeframe.

Steps taken:

Questions:

  1. Has anyone seen similar Cloudflare DNS errors with the OpenAI API?
  2. Does this match known edge / regional DNS issues not tracked on status.openai.com?

Thanks in advance for any insights!

The likely cause: the edge worker (rate limiter etc) that runs on Cloudflare had a DNS server outage, failing to lookup a resource (like "get api_key’s active status, etc), and is configured in reverse-proxy because OpenAI doesn’t want Cloudflare to be their complete DNS host, then maybe some name change propagation issues for a short while?

It is good to report, but likely net monkeys doing changes with unavoidable impact done in the middle of their night.

1 Like