This incident has been resolved. A temporary issue on Microsoft's side (Microsoft Container Registry) briefly delayed new compute nodes from starting in Azure NE, so some jobs waited longer than usual before running. No jobs failed or were lost - they only started later and completed normally once the registry recovered.
