We are aware of an emerging issue with the Edge DNS service.
We are actively investigating the issue. If you have questions or are experiencing impact due to this issue, please contact Akamai Technical Support. In the interest of time, we are providing you the most current information available, which is subject to changes, corrections, and updates.
So far it seems to be an Akamai internal DNS look up problem. That is, it seems if they need to resolve the hostname of the origin to serve a page they front for, it fails but I haven't seen any actual DNS failures on my side or other places, just inside Akamai-served pages saying they failed to resolve with an Akamai reference code.
Ah, I hadn't come across them. My feeling is still a minority of sites use Akamai's DNS for their public-facing names, so probably those sites would be affected that way. Although either way the site is down once the cache expires.
I can't speculate on cause, but it certainly is incredibly widespread. Just about every service shows a spike in problem reports: https://downdetector.com/
This appears to be an internal DNS lookup failure; the domain itself resolves but Akamai's internal network falls over. If this is the case, a DNS propagation check will not indicate any issues.
We are aware of an emerging issue with the Edge DNS service.
We are actively investigating the issue. If you have questions or are experiencing impact due to this issue, please contact Akamai Technical Support. In the interest of time, we are providing you the most current information available, which is subject to changes, corrections, and updates.
Jul 22, 16:09 UTC