Checked from your browser.
Not a stored badge. Your browser asks each component directly when this page loads, so what you see is what you would get.
What each check tests
- API. Your browser calls the API's health endpoint, which answers only when the application and its database both respond. Checkout, provisioning and credentials all run through it.
- Dashboard. Your browser requests the dashboard and times the answer. If it loads here, it loads for you.
- Website. You are reading it, so it reached you.
Each row shows the response time your browser measured, so a slow row is worth a look even when it is green.
Check your proxy from your side
When the rows above are green and requests still fail, the fastest answer is one request through your own proxy. Take the host, port and credentials from your dashboard and run:
curl -sS -x "http://USER:PASS@HOST:PORT" https://httpbingo.org/ipThe response is the exit IP the target sees. What the result means:
- An IP comes back. The proxy works; the problem sits with the target or the client settings.
- 407 Proxy Authentication Required. The credentials were not accepted. Percent-encode special characters in the password (
@becomes%40). - Connection refused or timed out. Check the host and port, and that your network allows outbound connections to that port.
- SOCKS5. Use
socks5h://so DNS resolves on the proxy side, not on your machine.
Step-by-step setup for every system, browser and language is in how to use a proxy, and what our gateway forwards is measured in proxymint Lab #1.
Common questions
Is proxymint down right now?
Open proxymint.com/status/. Your own browser checks the API and the dashboard when the page loads and shows the result with the response time, so a green row means the service answered you, not a badge someone set by hand.
Why does the status page say operational while my proxy requests fail?
The page checks the API, the dashboard and the website. A request through a proxy can also fail on your side or on the target: wrong credentials (407), a password with special characters that is not percent-encoded, a target that blocks the network type, or a local firewall. Run the curl check on this page against your own proxy to see which one it is.
How do I test my proxymint proxy from the command line?
Run curl -x "http://USER:PASS@HOST:PORT" https://httpbingo.org/ip with the host, port and credentials from your dashboard, percent-encoding any special characters in the password. The response shows the exit IP the target sees. For SOCKS5, use socks5h:// so DNS resolves on the proxy side.
What does a 407 error from a proxy mean?
HTTP 407 Proxy Authentication Required means the proxy did not accept the credentials it received. Check the username and password in your dashboard, percent-encode special characters, and make sure the client sends credentials to the proxy rather than to the target.
Report a problem
Something broken that this page says is fine? That is the useful report -[email protected].