Azure container registry is not working. Any one facing this issue south east asia region?

Thrimal Avishka - There is an ongoing service degradation affecting Azure Resource Manager (ARM) and Azure Container Registry (ACR).

At present, customers in Southeast Asia and multiple other regions may experience:

1. Increased error rates
2. Request timeouts
3. Intermittent failures (including 504 Gateway Timeout / Service Unavailable responses)

Our engineering teams has investigated the issue and working on mitigation efforts to restore normal service as quickly as possible.

We will continue to keep you informed as we receive further updates. In the meantime, we recommend retrying failed operations, as some requests may succeed intermittently. Issue should be mitigated now If you have any further queries, let me know. If the information is helpful, please click on Upvote and Accept Answer on it.

hi Thrimal Avishka & thanks for join me here at Q&A portal,

so its look like a possible regional service issue, especially because both the portal and cli operations are failing with 504 gatewaytimeout, serviceunavailable, and microsoft.containerregistry failed to return collection response.

So... look the azure status and more importantly, azure service health inside the affected subscription. The public azure status page only shows broad platform incidents, while service health is the authoritative place for subscription-specific and regional impact.

MSFT describes service health as the place to view service incidents, planned maintenance, impact to your resources, and guidance.

lets try to checks it

az acr show -n <registryname> -g <resourcegroup>

az acr check-health -n <registryname> --yes

az acr repository list -n <registryname>

az account set --subscription <subscriptionid>

az provider show -n microsoft.containerregistry

if az acr list, az acr login, and the portal all fail only in southeast asia but other regions work, i would raise a support ticket against azure container registry with region, registry name, timestamp, correlation id, cli version, and full error output.

i wouldn't treat this as a local docker issue yet. When the resource provider itself cannot return collection responses, that smells much more like a control-plane or regional acr service problem than your laptop had a mood swing. ))))

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal