Beginning yesterday morning, attempts to use Brave Search are refused. The message tells me to use different IPs, but I have been using the same IPv6 addresses for years longer than Brave has even existed. I rely on Hurricane Electric TunnelBroker because my previous ISP had nonexistent IPv6 support and my current one only has IPv6RD which is not a viable replacement. I tested from another VLAN that uses addresses from my routed /48 just to confirm that the block is not affecting only my /64.
Can you share whether my suspicion of this being a quiet policy change banning TunnelBroker address space is correct and whether this policy is permanent? If there are no plans to fix this issue, there is little point in me continuing to check whether Brave Search is working again. I sincerely hope that Brave Search is able to find an effective solution to whatever issue it is mitigating, without disrupting people who rely on TunnelBroker through collateral damage.
It’s certainly frustrating. Even when Reddit has gotten overly zealous about TunnelBroker, they at least have a way to sign in and still use their sevice.
I had to switch my default search to another provider. It would be nice of there was somewhere to reliably track this issue to know when I can resume using Brave Search again.
My Internet connection: Guest Wi-Fi + a VPN server
MacOS Terminal.app window:
Using command: curl -v --http1.1 https://search.brave.com
I suggest testing via the command, and comparing your results with the following … Result (not all of the result, but leading portion of it as follows):
$ curl -v --http1.1 https://search.brave.com
* Host search.brave.com:443 was resolved.
* IPv6: 2600:9000:2807:7600:5:a6ac:6100:93a1, 2600:9000:2807:200:5:a6ac:6100:93a1, 2600:9000:2807:8200:5:a6ac:6100:93a1, 2600:9000:2807:6a00:5:a6ac:6100:93a1, 2600:9000:2807:400:5:a6ac:6100:93a1, 2600:9000:2807:f200:5:a6ac:6100:93a1, 2600:9000:2807:ee00:5:a6ac:6100:93a1, 2600:9000:2807:5600:5:a6ac:6100:93a1
* IPv4: 3.168.102.77, 3.168.102.34, 3.168.102.104, 3.168.102.129
* Trying 3.168.102.77:443...
* Trying [2600:9000:2807:7600:5:a6ac:6100:93a1]:443...
* Immediate connect fail for 2600:9000:2807:7600:5:a6ac:6100:93a1: No route to host
* Trying [2600:9000:2807:200:5:a6ac:6100:93a1]:443...
* Immediate connect fail for 2600:9000:2807:200:5:a6ac:6100:93a1: No route to host
* Trying [2600:9000:2807:8200:5:a6ac:6100:93a1]:443...
* Immediate connect fail for 2600:9000:2807:8200:5:a6ac:6100:93a1: No route to host
* Trying [2600:9000:2807:6a00:5:a6ac:6100:93a1]:443...
* Immediate connect fail for 2600:9000:2807:6a00:5:a6ac:6100:93a1: No route to host
* Trying [2600:9000:2807:400:5:a6ac:6100:93a1]:443...
* Immediate connect fail for 2600:9000:2807:400:5:a6ac:6100:93a1: No route to host
* Connected to search.brave.com (3.168.102.77) port 443
* ALPN: curl offers http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256 / [blank] / UNDEF
* ALPN: server accepted http/1.1
* Server certificate:
* subject: CN=search.brave.com
* start date: Sep 1 00:00:00 2026 GMT
* expire date: Mar 17 23:59:59 2027 GMT
* subjectAltName: host "search.brave.com" matched cert's "search.brave.com"
* issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M04
* SSL certificate verify ok.
* using HTTP/1.x
> GET / HTTP/1.1
> Host: search.brave.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 200 OK
< Content-Type: text/html; charset=utf-8
< Content-Length: 809055
< Connection: keep-alive
< Date: Sun, 04 Oct 2026 05:48:59 GMT
< Onion-Location: https://search.brave4 ...
origin is the backend resource that CloudFront retrieves the content from. It could be:
the website’s actual web server;
an application server;
an AWS service such as S3; ← (Brave uses S3)
or another backend/CDN endpoint.
In my example, IPv6 failed but I do not force that; in fact, I usuallly (but not always) set up for IPv4 only. Also, in some other connection attempts (re other site testing for other issues) - I have encountered failure at the TLS layer.
You seem to be encountering failure at the IPv6 layer.
