DNS propagation delays in Common Runtime and Private Spaces

We are still communicating with upstream provider for the resolution progress and platform is stable since 01:22 UTC, We will post another update in 120 minutes, or as soon as one is available.

Engineers continue to monitor the status and remained stable since 01:22 UTC but we have not considered the incident as cleared until our upstream provider confirms they’re out of impact. We will post another update in 60 minutes, or as soon as one is available.

Engineers have confirmed that our monitoring shows we’re out of impact as of 01:22 UTC. We remain in monitoring phase until our provider update for the resolution. We will post another update in 60 minutes, or as soon as one is available

Engineers are still in communication with upstream provider, and they have an estimated ETA of 2 hours for a full recovery. We will post another update in 60 minutes, or as soon as one is available.

Engineers are still communicating with our upstream service provider and we are seeing some improvements towards the resolution. We will post another update in 60 minutes, or as soon as one is available.

Engineers remain in communication with our upstream service provider to pursue a resolution. We will post another update in 60 minutes, or as soon as one is available.

Engineers are still working with our upstream service provider to resolve the issue. We will post another update in 60 minutes, or as soon as one is available.

Engineers are still in communication with our upstream service provider to expedite a resolution. We'll provide the next update within 30 minutes, or as soon as one is available.

Engineers are working with our upstream service provider to expedite a resolution. We'll provide the next update within 30 minutes, or as soon as one is available.

Engineers are investigating delays with DNS propagation for new domains (both custom and default) in Private Spaces and Common Runtime, in the EU and US regions.