Our subnet is blocked by all services hosted in azure

Question

Our subnet is blocked by all services hosted in azure

erw per 0

Hello, for a while now, we haven't been able to access services hosted on the Azure platform. It's as if we're blocked by the Azure firewall. Some Azure-hosted service providers claim that we're not blocked by them and that this is Azure's fault.

Our impacted subnet is 179.61.174.0/24.

Best regards

Thanmayi Godithi 635 Reputation points Microsoft External Staff Moderator

2025-08-26T18:54:57.27+00:00
Hello @erw per,

Thank you for reaching out on Microsoft Q&A forum.

To better understand and assist with the issue you're experiencing — where subnet 179.61.174.0/24 is unable to access Azure-hosted services — I’d like to clarify a few key points first:

1.Based on the subnet range you provided, it appears this may be a public/ISP-owned subnet; however, could you please confirm whether it’s public or an Azure VNet subnet?”

2.Are you observing the access issue when connecting from:

On-premises or ISP networks, or

Within Azure resources (e.g., VMs or services hosted in your Azure environment)?

3.Have you run any basic network diagnostics such as:

tracert or ping to the affected Azure service domains?

nslookup to verify DNS resolution? If so, could you share where the traffic appears to be failing (e.g., at the edge, mid-hop, or destination)?

These details will help us determine whether the issue is likely due to:

A platform-level restriction (such as an IP reputation block on a public subnet), or

A network configuration issue within your Azure environment (such as NSG rules, Azure Firewall, or routing misconfigurations).

Once we have this clarity, we’ll be able to provide more targeted next steps and supporting documentation.

Looking forward to your response so we can assist you further.

1 answer

Your answer

Thanmayi Godithi 635 Reputation points Microsoft External Staff Moderator

2025-08-26T18:54:57.27+00:00

Hello @erw per,

Thank you for reaching out on Microsoft Q&A forum.

To better understand and assist with the issue you're experiencing — where subnet 179.61.174.0/24 is unable to access Azure-hosted services — I’d like to clarify a few key points first:

1.Based on the subnet range you provided, it appears this may be a public/ISP-owned subnet; however, could you please confirm whether it’s public or an Azure VNet subnet?”

2.Are you observing the access issue when connecting from:

On-premises or ISP networks, or

Within Azure resources (e.g., VMs or services hosted in your Azure environment)?

3.Have you run any basic network diagnostics such as:

tracert or ping to the affected Azure service domains?

nslookup to verify DNS resolution? If so, could you share where the traffic appears to be failing (e.g., at the edge, mid-hop, or destination)?

These details will help us determine whether the issue is likely due to:

A platform-level restriction (such as an IP reputation block on a public subnet), or

A network configuration issue within your Azure environment (such as NSG rules, Azure Firewall, or routing misconfigurations).

Once we have this clarity, we’ll be able to provide more targeted next steps and supporting documentation.

Looking forward to your response so we can assist you further.

Answer 1

Hi, It's not "an Azure firewall" blocking you: your /24 has most likely ended up on Threat Intelligence (reputation) lists that many Azure customers use in Front Door/WAF/Application Gateway/Azure Firewall. To verify this: try reaching multiple Azure endpoints and ask a vendor for logs—if they see ThreatIntel/MaliciousIP/BotProtection or 403 from the WAF, it's confirmed.

What to do: Immediate workaround → Log out with a different IP (new NAT/ISP/VPN). Permanent fix → Have one of the vendors open a ticket with Microsoft ("Threat Intelligence false positive – unblock 179.61.174.0/24"), attaching the IP, timestamp, and request ID for delisting. Prevention → Verify that scans/spam aren't being launched from your network, fix WHOIS/rDNS, and check and remove any public blocklists.

Share via

Our subnet is blocked by all services hosted in azure

1 answer

Your answer