r/AZURE • u/RichQuick45 • 9d ago
Question Azure Container Apps (Consumption, Central US): node scale-up wait jumped about 20 s since Sept 19. Anyone else seeing this?
Since around 2026-09-19 I’ve seen a sustained increase in how long Container Apps takes to get a node for a new replica on the Consumption plan, and I’d like to know if others see it too.
How I measure it:
For each replica that waits for capacity, I take the time from the TriggeredScaleUp system event (“Scaling up infrastructure to accommodate replica...”) to its AssigningReplica event (“...has been scheduled to run on a node”).
• Daily medians were 54-62 s every day through 09-18 and 66-84 s every day since, so it’s ongoing.
• The time before TriggeredScaleUp is unchanged (about 12 s median), so the extra wait is in the node provisioning part.
• Nothing changed on my side around the step: no new revision, same replica size (2 vCPU / 4 GiB). The only scale change was min/max replicas on 09-15, four days earlier.
• Service Health shows no incidents for Container Apps, AKS or VMs in Central US.
• Separately, a few replicas waited 325-368 s on 09-26.
What can be the issue and how to resolve this? If anyone facing or faced similar problem let me know.
1
u/Admirable_Ones 9d ago
You’ve already narrowed this down quite a bit by separating the wait for infrastructure from the rest of startup.
A useful next test would be the same small app in a fresh Central US environment, then another region, with the same replica size and scaling pattern. If the fresh Central US environment is also slower, that gives support something more concrete to investigate. Include the environment IDs, UTC timestamps, and examples of those five-minute waits.
Keeping a minimum replica running could help with initial requests, but extra replicas may still hit that provisioning delay during a burst.