Quick answer
Is Broadband Proxies working right now?
Test the Broadband Proxies gateway with one command: curl -x http://USERNAME-country-us:[email protected]:7777 https://api.ipify.org. If it prints a US IP, the gateway works, and the issue lies with the target or with the ISP or city you asked for. No incidents logged since the site opened (18 October 2026). Support: [email protected].
Components
| Component | What it does | State | Check it yourself |
|---|---|---|---|
| Gateway, HTTP and HTTPS | gw.broadbandproxies.com:7777 | Operational: no incident logged | curl -v -x http://USERNAME-country-us:[email protected]:7777 https://api.ipify.org |
| Gateway, SOCKS5 | gw.broadbandproxies.com:7778 | Operational: no incident logged | curl --socks5-hostname gw.broadbandproxies.com:7778 -U USERNAME-country-us:PASSWORD https://api.ipify.org |
| Client area and checkout | Account, balance, plans and sub-users | Operational: no incident logged | Sign in at /app/ |
| API | /api/v1 on this domain | Operational: no incident logged | Request your balance with your API key |
| Crypto payment detection | Finding top-ups and counting network confirmations | Operational: no incident logged | The payment page shows the confirmations received |
"Operational" only means that no incident is logged for the component. It is not an uptime figure.
Incident log
| Date | Component | What happened | Resolved |
|---|---|---|---|
| 18 October 2026 | — | No incidents logged since the site opened (18 October 2026) | — |
Is it the gateway, the target or ASN availability?
- The gateway returns a US IP, but the target fails. The gateway works. The target may be slow, may rate-limit you, or may be on our blocked list. Refused targets include: Banking, government and payment-portal sites, plus SMTP (email-sending) ports 25, 465 and 587.
- Plain US targeting works, but one ASN or city fails. That is an availability gap, not an outage. ASN availability varies by network, city and time of day; the checkout shows what is online, and no IP count per ISP is published. Try a nearby city, drop the ZIP code, or try again later.
- Every request returns 407. The username or password is wrong, or your IP is missing from the allowlist.
- Every request times out. Check the host, the port and your own network, then contact support.
To confirm which network an exit belongs to, follow how to check the ASN of your exit IP.
How are incidents recorded?
Each incident gets one line with its date, the component, what users saw and when it was fixed. Lines stay in the log after the fix, so the history remains complete. Short gaps on a single ISP or city are not incidents, because supply on one network changes through the day.
How do I report a problem?
Email [email protected] with the time in UTC, the proxy username without the password, the target and the error. For a payment, add the coin, the network and the TXID. Email replies within 12 hours, 7 days a week.