Quick answer
Is Nameless Proxy down?
Check this page and the dashboard banner: Nameless Proxy posts every incident and planned maintenance in both places. It monitors 7 components, from the gateway and the residential pool to 4G/5G ports and crypto top-ups for each of 6 coins. No uptime percentage is shown until a measured history exists.
In brief
- Where to look: this page and a banner in the dashboard, with start time in UTC, impact and updates.
- What is monitored: gateway, residential pool, dedicated mobile ports, rotating mobile pool, crypto top-ups, dashboard and API.
- No uptime figure yet: records start on 5 October 2026, and Nameless Proxy does not publish numbers nobody measured.
- Not incidents: a sticky IP ending early, a target site blocking you, a rotation that returns the same IP.
- Report: [email protected] or a technical ticket; Email replies within 12 hours, 7 days a week.
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; Nameless Proxy will not publish figures Nameless Proxy has 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 Nameless Proxy works on it, and the time it was resolved.
Planned maintenance is posted before it starts whenever Nameless Proxy 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. Nameless Proxy will not show a green "all systems operational" badge or a percentage that nobody measured.
Nameless Proxy's 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 Nameless Proxy publishes availability figures, this page will state how and over which period they were measured.
Nameless Proxy checked its public incident log on 13 November 2026: it holds one entry, the opening of the log on 5 October 2026, and no outage has been posted since.
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 the 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.** Nameless Proxy replies 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 Nameless Proxy publishes no uptime percentage and makes no uptime promise. The Terms of Service describe availability. When Nameless Proxy has measured data, Nameless Proxy 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 the refund policy: within 72 hours of purchase, a residential or rotating-mobile plan is credited back to your balance if you used less than 20% of its traffic and no more than 1 GB; a plan that does not work, and that support cannot fix within 24 hours, is credited back in full. Dedicated ports: within 24 hours of delivery (2 hours for a 1-day port), the port is credited back to your balance in full if it does not work and Nameless Proxy cannot fix or replace it, or if it has carried less than 500 MB. A port Nameless Proxy cannot deliver within 24 hours is credited back in full. If a port stops working later and support cannot fix it within 24 hours, the lost days are credited back. Top-ups are not paid back, except where the law requires it; the part added only to reach the minimum top-up is refundable on request within 30 days, in USDT or USDC, if unspent. If an incident affected your service, contact support with the details, and Nameless Proxy will look at your case under that policy and the Terms of Service.
Verdict
- Nameless Proxy is the better choice if you want incidents written per component and per coin, with no invented uptime badge: check here first, then email support.
- A provider with a long measured uptime history fits better if your contract needs a signed SLA percentage, which Nameless Proxy does not offer.
Something not working?
Check the quick-start troubleshooting table, then email [email protected].