That looks like a classic Microsoft Azure Front Door or Cloudflare WAF (Web Application Firewall) blocking page.

When you see a flat "Service unavailable / The request is blocked" paired with that specific timestamp and reference string format (20260523T111046Z-...), it means your request was intercepted and dropped by the edge security layer before it even reached the actual website's hosting server.

Here is the quick checklist to figure out why it's blocking you and how to bypass it:

1. The Immediate Fixes

• Check your VPN/Proxy: Security firewalls aggressively block specific IP ranges known for data center or VPN traffic. If you're on a VPN, disconnect or switch servers and try refreshing.
• Clear Session Cookies / Try Incognito: Sometimes an expired, corrupted, or bloated session cookie triggers a "bad request" rule in the firewall. Testing in a private window isolates this instantly.
• Corporate Network / Zscaler: If you're on a corporate network or behind an aggressive web gateway, the firewall on the other end might be tripping over headers inserted by your company's security software. Switch to a mobile hotspot to test.

2. The Browser Clean-Up

If it's only happening in one specific browser, a quick cache and cookie wipe for that specific domain usually clears the flag.

Note on that Reference String: If you are managing this application or need to open a ticket with the service provider's IT support, save that exact long string. It acts as a unique transaction ID in their firewall logs. Their admin can paste that token into their security portal to see exactly which automated rule (e.g., SQL injection false positive, cross-site scripting rule, or geo-blocking) triggered the block.