FNDCPGSC Service Failure & Connectivity Issue (30-MAR-2026 20:58 UTC)

Question

We are seeing a failure with the FNDCPGSC service around 30-MAR-2026 20:58:01, where the PingProcess call failed. At the same time, the VM was unable to connect to reach vip

Could you please check and let us know if anything happened around that time (network issues, outages, changes, or maintenance activities)?

Answer 1

Hi Hemanta,

Thank you for the clear report with the exact timestamp — that helps narrow things down quickly.

Brief summary

• No platform-wide outage, maintenance, or known issue was active for Azure Virtual Machines around 30-MAR-2026 20:58 UTC.
• The simultaneous “PingProcess call failed” + “VM unable to reach VIP” is a classic symptom of temporary loss of connectivity from the VM to Azure’s internal WireServer VIP (168.63.129.16).
• Many customer services (including custom health/monitoring processes like yours) rely on this VIP for agent communication, heartbeat checks, and platform services. A brief routing, NSG, or DHCP blip can cause exactly this failure.

Recommended next steps (start here)

1. Verify connectivity to the WireServer VIP from inside the affected VM: PowerShell

      Test-NetConnection -ComputerName 168.63.129.16 -Port 80 -InformationLevel Quiet
   

   It should return True. If it fails, the issue is confirmed at the network layer.
2. Check Network Security Group (NSG) effective rules on the VM’s NIC/subnet for outbound traffic to 168.63.129.16 (port 80/443/32526).
3. Review effective routes (Azure portal → VM → Networking → Effective routes) to ensure no custom User-Defined Route (UDR) is overriding the default system route to the WireServer.
4. Restart the Azure Guest Agent service inside the VM and re-test the PingProcess.

Links:
https://learn.microsoft.com/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16?tabs=windows

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/windows/windows-azure-guest-agent

Thanks,
Manish.