This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 6%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDH%3C/text%3E%3C/svg%3E)
Our Dev SKU API Management has been displaying "The compute node that powers your API Management instance is being rebooted. A reboot of the API Management's underlying compute node is most likely triggered by an automatic upgrade" for several days now. We need to update the APIM, but we cannot take any actions against it, although the API endpoints appear to be functioning on the existing configuration. Is there any way to either check on the progress of the update or remove the APIM so that it can be recreated?
Hi, Dustin; the Gateway plane runs separately from the management plane, which could be why your APIs are still serving traffic, but you are unable to manage it.
Is there anything in the Activity Log that indicates any errors?
You could try switching from the Developer tier to Basic, then back to Developer to force the change, but it will cause an outage.
@Luke Murray I switched to premium SKU due to the need for VNET, but the problem is still there. The message has changed to "Your API Management service is down due to an unknown reason. Your API Management service is down due to an unknown reason."
The activity log shows a GetToken error with "Failed to connect to Management endpoint Port 3443 at endpoint apimaimdevueapis.management.azure-api.net for the service." which is what I've seen in the past when it entered the rebooting for update process, but then that would clear after the reboot was done and everything came back online.
Hi, Dustin - yes, something is definitely a miss!
Your best bet is to contact Microsoft Support directly and raise a support ticket so they can investigate in the backend. Let us know how you get on!