What the status page monitors
Each row on the live page is one component, with its current state, 90-day uptime, latency and a bar for every day. The components fall into three groups.
Platform
- Website and dashboard: nefo.net and the customer dashboard answer.
- API: the API process and its database answer a liveness call.
Entry gateways
- Europe gateway,
fr.nefo.net: a real proxied request through the European entry reaches a residential exit. - United States gateway,
us.nefo.net: the same check through the US entry. - Asia gateway,
sg.nefo.net: the same check through the Singapore entry.
Networks
- Residential network: at least one entry reached a residential exit, so the pool is serving.
- Mobile network: of the mobile ports the health loop dialled in the last 30 minutes, at least 90% answered.
- IP Vault: the relay that serves held addresses accepts connections on ports in use.
How the checks work
Once a minute, a prober on our monitoring host dials each regional entry with an ordinary customer login and reads the exit address it lands on, over HTTP and then SOCKS5. It also fetches the website and the API's liveness endpoint, and folds in the mobile and IP Vault health loops.
A component is marked down only after three consecutive failed checks, so one lost packet on the monitoring host's own route does not become an outage. A day is green at 99.5% and above. The bars use four colors: 99.5% and above, 95 to 99.5%, below 95%, and no samples that day.
How to read latency and uptime
The latency figure is a repeat request over a session that is already open, the median of the last fifteen minutes, not one cold dial. A first connection to any gateway takes longer than a repeat request, so expect real numbers to differ. The entry gateway you pick changes latency but not the exit country, which you set with the country token in the username, as explained in the API docs.
Nefo's overall gateway uptime is 99.9%. For 90-day and 30-day figures per component, open the live status page, which also publishes the same data as JSON at /api/status.
The incident log
The incident log covers the last 90 days and is written by the people who fixed each problem, as it was written at the time. Past examples are on the news page, such as a fixed gateway slowdown and a fixed DNS leak on the gateways.
Limits of the measurement
The probes run from one host. A problem between your network and ours can be real and still not show on the page. If you see one, tell us and we will check from where you are.
Before reporting, try another gateway: gw.nefo.net picks the nearest one, and fr.nefo.net, us.nefo.net and sg.nefo.net are the regional options. A new credential takes about a minute to activate, and a stopped proxy often means the bandwidth balance has run out; see the guide for the usual causes.
Where to learn more or report a problem
- How the network is built: the network
- Report a problem: contact support, available 24/7 by live chat and email
- Coverage by country: locations
Frequently asked questions
Once a minute. A prober dials each regional entry with an ordinary customer login, reads the exit address and repeats the test over HTTP and then SOCKS5.
A component is marked down only after three consecutive failed checks, so one lost packet does not become an outage. A day shows green at 99.5% and above.
Nefo reports 99.9% gateway uptime. The live status page shows 90-day and 30-day uptime for every component.
The probes run from one host, so a problem on the route between you and us can be real without showing. Try another gateway, then contact support and we will check from where you are.
The website and dashboard, the API, the Europe, United States and Asia entry gateways, and the residential network, mobile network and IP Vault.