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(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hello colleagues,
We are using an Internet breakout solution which looks like below:
Internet > AzureFw > Azure APPGW > LB > IPS > Azure vnet that contains Backends on which WebApps are being hosted, one of this applications for example is speedtest.mycompany.com which is working now, a request came to enable ICMP so user can do the ping(icmp) test to this URL so they see the response time etc ..., is it possible to implement?
is it possible to Ping URLs hosted in Azure?
An Azure service that provides a platform-managed, scalable, and highly available application delivery controller as a service.
An Azure service that provides protection for web apps.
Based on your setup, ICMP is not possible due to Application Gateway. There may be an alternative in terms of testing, but not when app gateway is included.
There is a community site which details latency based on region if that helps? https://azurespeedtest.azurewebsites.net/
Thanks for the reply, I tested https ping and seems it is working, I used it like this : ping speedtest.mycompnay.net:443 so I asked the application team to check if they can use it instead of icmp and hopefully it will work, as it also gives times ...
what do you think, can it be used a solution for our case?
Hi,
When you use ping speedtest.mycompnay.net:443 from your application, it doesn't use ICMP. Instead it uses TCP port 443.
ICMP doesn't have any ports. You cannot use ICMP, you can use any layer 4 connectivity tools.
Regards,
Karthik Srinivas
Hi I understand, but can it be used instead of icmp to do the same measurements and delays?
![](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(208, 44%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
Actually as of today ICMPv4 is supported on application gateway. Hope this helps someone else looking for clarity.
https://azure.microsoft.com/en-us/updates/general-availability-inbound-icmpv4-pings-are-now-supported-on-azure-load-balancer/
![](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(188.79999999999998, 22%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Azure load balancer works on TCP layer -4 which supports ICMP. But app gateways works on TCP layer-7 which supports only http/https protocol.