Quick answer
Is CrawlRelay down?
This page lists every confirmed CrawlRelay incident and maintenance window with its date and time in UTC; no incident is recorded on this page as of 13 October 2026. If your requests fail, first test the gateway with curl -v against https://api.ipify.org: if that works, the problem is on the target side. Support: [email protected].
Components
| Component | What it does | How to test it |
|---|---|---|
| Gateway, HTTP | gw.crawlrelay.com:7777, HTTP and HTTPS through CONNECT | curl -v -x http://USERNAME:[email protected]:7777 https://api.ipify.org |
| Gateway, SOCKS5 | gw.crawlrelay.com:7778 | curl --socks5-hostname gw.crawlrelay.com:7778 -U USERNAME:PASSWORD https://api.ipify.org |
| Client area | Account, plans, sub-users, usage | Sign in at /app/ |
| API | https://crawlrelay.com/api/v1 | A GET on your balance with your API key |
| Crypto payments | Matching top-ups by exact amount, and confirmations | Top-up status in the client area |
Incident log
| Date (UTC) | Component | What happened | Status |
|---|---|---|---|
| 2026-10-13 | All | No incident recorded as of this date. | — |
New incidents are added at the top with start time, end time and cause once known.
Is it the gateway or the target?
- The curl test fails with a connection error: the gateway is unreachable from your network, or your network blocks the port. See ERR_PROXY_CONNECTION_FAILED.
- The curl test returns 407: your credentials are wrong or your plan has no traffic left. See 407.
- The curl test works but your target fails: the target is down, slow, or refusing your requests. See 403, 429 and 503.
- Only one city or ZIP fails: narrow targeting can run short of exits; test the country alone.
How do I report a problem?
Email [email protected] with the time and time zone, the username suffix you used, the exact error and the output of the curl test above. Email replies within 12 hours, 7 days a week. We record confirmed incidents on this page and changes to the service in the changelog.