Our systems have detected unusual traffic from your computer network. Please try your request again later. Why did this happen? IP address: 2a09:bac1:6520:8::279:5d 2a09:bac6:d69c:18d2::279:5d Time: 2026-03-04T06:04:17Z issue

The message shown is generated by Google, not by Microsoft Edge or Windows 10. It indicates that Google has temporarily flagged traffic from the current network as unusual (for example, due to many automated or rapid requests, VPN/proxy use, or shared IP addresses). When this happens, Google may block or challenge access to its pages, including support and Gmail-related URLs.

To address this from the Microsoft side, focus on network and browser conditions that can trigger such checks:

1. Disable or change VPN/proxy
   • If connected through a VPN, corporate proxy, or privacy tool that changes the IP address frequently or shares it with many users, disconnect from it and try again using a direct connection.
   • If using a corporate network, contact the network/IT administrator so they can check for automated traffic or misconfigured security tools that might be sending many requests to Google.
2. Check firewall or security software
   • Ensure local firewall, antivirus, or web-filtering tools are not repeatedly retrying or scanning Google URLs in a way that looks automated.
   • If such tools are present, temporarily disable their web-filtering/inspection component (if allowed by policy) and test again.
3. Clear browser data and test in a clean profile
   • In Microsoft Edge, clear cookies and cached data for Google domains, then retry.
   • Test in an InPrivate window or a new Edge profile with no extensions to rule out extensions generating automated traffic.
4. Ensure cookies and scripts are allowed
   • Some Google protection pages require cookies and JavaScript to complete the verification step. If cookies or scripts are blocked, the page may loop.
   • In Edge or Chrome, allow cookies and do not block JavaScript for Google sites. For Chrome, similar cookie settings are described in the sign-in troubleshooting guidance: allow cookies and avoid blocking third-party cookies when accessing Microsoft 365; the same principle applies when Google needs to set cookies for verification.
5. Wait and retry
   • Google’s “unusual traffic” blocks are often temporary. After reducing automated-looking traffic and fixing browser/network conditions, wait some time and then try the URL again.

If the issue persists only on a managed (work/school) device or network, the administrator should review outbound traffic and any proxies or content filters that might be causing Google to see abnormal request patterns.

References:

• Troubleshoot-signing-in