Grok Bot computer is US AWS-only; NZ trade sites behind Imperva hard-block it

Ideas Feature Requests
, , ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

Grok Bot’s persistent computer egresses from AWS us-west-2 (Oregon, US). New Zealand B2B sites that sit behind Imperva/Incapsula hard-block that traffic before a login form is shown.

Example: BNT EzyParts at https://ezyparts.bntnz.co.nz/

This is not a Chrome fingerprint / automation-stealth issue. It is datacentre IP reputation (and US geo). A NZ cloud IP would likely still fail. What NZ trade users need is selectable region or non-datacentre/NZ ISP egress for the Agent Computer.

Without that, Grok Bot cannot be used for a core NZ wholesale workflow (parts ordering on trade portals). Sites that do not WAF cloud IPs still work. EzyParts does not.

Steps to Reproduce

  1. From Grok Bot’s cloud computer, open ezyparts.bntnz.co.nz
  2. Site redirects to ezyparts.bntnz.co.nz/login
  3. Imperva returns a hard block (no captcha, no login form)

Error:
Access denied
Error 16
ezyparts.bntnz.co.nz
2026-08-13 09:24:09 UTC
This request was blocked by our security service
Your IP: 32.188.55.103
Proxy IP: 45.60.44.16 (ID 102103-100)
Incident ID: 2104000730093379518-120543127793046093
Powered by imperva

Public IP lookup on the Agent Computer (ipinfo): AWS EC2 in Boardman, Oregon, US, AS16509 Amazon.com, Inc. Hostnames include ec2-*.us-west-2.compute.amazonaws.com.

Expected Behavior

NZ subscribers should be able to use NZ trade sites from Grok Bot. Please add a NZ (or non-datacentre) egress option for the Agent Computer, or region selection so Imperva/WAF-protected NZ wholesalers are reachable.

Operating System

Linux

Version Information

Grok Bot Agent Computer (cloud, AWS us-west-2); Cursor web/app version not applicable

Additional Information

  • Bot name: New Bot
  • Time: 2026-08-13 09:24 UTC (9:24pm NZST)
  • Updating/rebuilding the Agent Computer would not help; it still lands on US AWS
  • There is no in-app setting to pick computer region

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

4

Screenshot of the Imperva Error 16 block from Grok Bot’s cloud computer (AWS us-west-2) against ezyparts.bntnz.co.nz.

ezyparts-imperva-block
ezyparts-imperva-block1042×632 25.7 KB

6

Thanks for the detailed report!

You’re right, the Agent Computer currently egresses from US cloud infrastructure and there’s no region selection today. Sites with strict IP-reputation rules can hard-block that traffic before login. This class of blocking is a known limitation we’re actively working to improve!