Status

Status of each part of the service.

All operational.

Part	Status
Address delivery	Operational
IP authentication	Operational
Payment	Operational
Tools	Operational

The table above is declared part by part and covers the whole service: it is not a live measurement of every address. The measurement of your address is the one you run in the tools yourself.

How we measure

We measure what a customer can also measure: whether the port answers, which address the destination saw, how long the answer took and how many lists carry the address. Third-party measurements come with their source named, and anything unmeasured never becomes a number.

Outbound portTCP connection on 20001 (HTTP) and on 20481 (SOCKS5), with the user and password of the line.

Address seen by the destinationRead from the echo: it is the address the other side received, not what the panel promises.

Response timeThree measurements per address — minimum, average and maximum — from your side of the connection.

ReputationFourteen public block lists in a single round, with the ones that did not answer reported as not checked.

ReplacementOne address every 24 hours and the whole package every 30 minutes, counted by the panel.

Performance report

The commitment is to publish, once continuous measurement exists, the response time per location group and the number of replacements per day, with the date and the method next to each number. Until then, no number is published.

Real content pending.

Before contacting support

Run the proxy test and the block list check on your address. The result shows whether the port opens, where the traffic comes out and which lists carry the address, and that answers most tickets. If the problem remains, open the ticket with the result pasted in.

Test proxy · Blocklists · Contact