Quick answer
Is Nameless Proxy down?
Check this page and the banner in your dashboard: Nameless Proxy, a no-KYC proxy provider paid in crypto, posts incidents and planned maintenance in both places. We monitor the proxy gateway, the residential pool, 4G/5G mobile ports, crypto top-ups for each coin, the dashboard and the API. We publish no uptime percentage until we have a measured figure for this service, with its method and period. Report problems to [email protected]; we reply within 12 hours.
Status at a glance
| Where incidents appear | This page and a banner in the dashboard |
|---|---|
| Components monitored | Gateway, residential pool, dedicated mobile ports, rotating mobile pool, crypto top-ups per coin, dashboard, API |
| Records start | 5 October 2026 (start of public log) |
| Uptime figures | None published yet; we will not publish figures we have not measured |
| Report a problem | [email protected] · reply within 12 hours |
| Product changes | Listed in the changelog, not here |
What does Nameless Proxy monitor?
Seven components, each with the symptom you would notice if it failed.
| Component | What it covers | What you would notice |
|---|---|---|
| Proxy gateway | gw.namelessproxy.com, ports 7777 (HTTP/HTTPS) and 7778 (SOCKS5), authentication | Connection refused, timeouts or 407 errors with correct credentials |
| Residential pool | Available exit IPs by country and city | No IP in a country or city that the dashboard listed as in stock |
| Dedicated mobile ports | Modems online, carrier connection, rotation by link, API and timer | Port shown offline, or rotations that fail after the 30-second wait |
| Rotating mobile pool | Available carrier IPs by country | No mobile IP in a country offered at checkout |
| Crypto top-ups | Top-up creation, payment detection and confirmations for BTC, USDT, USDC, ETH, SOL, LTC, on every network shown on the top-up screen | A top-up that does not detect a payment already visible on-chain |
| Dashboard | Login with the account number, orders, credentials, tickets | Login or order pages that fail to load |
| API | namelessproxy.com/api, including the mobile rotation link | Errors on calls that worked before, other than 429 rate limits |
How are incidents and maintenance announced?
On this page and as a banner in the dashboard. Each incident entry gives:
- the start time, in UTC;
- the affected component and, where relevant, the country, carrier or coin;
- the impact on customers;
- updates while we work on it, and the time it was resolved.
Planned maintenance is posted before it starts whenever we can plan it. Product and price changes are not incidents; they go to the changelog.
Why is there no uptime percentage on this page?
Because an uptime figure needs a measured history, a method and a period, and this page starts its records on 5 October 2026. We will not show a green "all systems operational" badge or a percentage that nobody measured.
Our service also depends on partner networks and mobile carriers. A single residential IP going offline is normal and is not an incident; an outage of the gateway or of a whole country is. When we publish availability figures, this page will state how and over which period they were measured.
What is not an incident?
Some errors are expected behaviour, not outages:
- A sticky session ends early. Residential devices can go offline before the session ttl; your software should handle a new IP.
- A target site blocks or rate-limits you. That depends on the target, your request rate and your setup.
- A rotation returns the same IP. Carriers share address pools, so this can happen occasionally.
- 429 on rotation. Each mobile port accepts one rotation per 30 seconds; wait for the time in the
Retry-Afterheader. - A blocked target. Banking, payment and government portals, crypto-exchange account pages and SMTP ports are blocked by our Acceptable Use Policy.
- A top-up waiting for confirmations. A top-up is credited after the network confirmations shown on the top-up screen.
How do I report a problem?
Email [email protected] or open a technical ticket in the dashboard. We reply within 12 hours. Include:
- the time of the problem, with timezone;
- the product (residential, dedicated port or rotating mobile) and the country, city or carrier;
- the exact error, or
curl -voutput with the password removed; - for top-ups, the payment ID, the coin, the network and the exact amount sent.
Before you write, the troubleshooting table in the quick-start guide covers the most common errors, such as 407, timeouts and wrong-country exits.
Incident history
Newest first. Records start on 5 October 2026; nothing is backdated.
| Date (UTC) | Component | Type | Summary |
|---|---|---|---|
| 2026-10-05 | All | Log start | Status page published. No incident entries have been posted yet. |
Service status: FAQ
Where can I see if Nameless Proxy has an outage?
On this page and in the banner at the top of your dashboard. Both show current incidents and planned maintenance, with the affected component, the start time in UTC and updates until the problem is resolved. Product changes are listed separately in the changelog, so this page stays focused on service problems.
Does Nameless Proxy promise a minimum uptime?
No. This page has no measured history yet to base a figure on, so we publish no uptime percentage and make no uptime promise. Our Terms of Service describe availability. When we have measured data, we will publish it here with the method and the period.
My top-up is not credited. Are payments down?
Usually not. A top-up is credited after the network confirmations shown on the top-up screen, for example 2 for Bitcoin and 12 for Ethereum, and a busy network can be slow. If the transaction has those confirmations and your balance still shows nothing, email support with the payment ID, coin, network and the exact amount sent.
Will I get compensation for downtime?
Compensation is not automatic. Refunds follow our refund policy: full refund within 24 hours of purchase if less than 100 MB of the pack was used; a dedicated port that cannot deliver a working IP is refunded in full. If an incident affected your service, contact support with the details, and we will look at your case under that policy and our Terms of Service.
Something not working?
Email [email protected]. We reply within 12 hours.