Proxy Bastion does not sell IPs. It sits in front of proxies you already pay for and gives each person a revocable, metered link instead of your credentials. What they receive is a relay link and nothing else: no upstream host, no upstream password.
This release accepts http and https upstreams only. It does not support socks5 upstreams, which matters here because PacketStream documents a socks5 port alongside its http and https ports. Use the http or https port, not the socks5 one.
We are not affiliated with PacketStream and we do not resell their traffic. Everything below comes from their public documentation, with the source and the date we read it listed at the bottom of this page.
What is supported
Upstream protocols: http, https
socks5 upstreams: not supported in this release
Gateway details we could confirm
Gateway host
proxy.packetstream.io
Port
HTTPS 31111, HTTP 31112 (a socks5 port 31113 is also documented but is not usable here)
Credential format
Username and password, either supplied separately with --proxy-user or embedded as USERNAME:PASSWORD in the proxy URL
Setup
1. Take the gateway credentials from your PacketStream dashboard
You need four values: the host, the port, your username and your password. The host and port are documented publicly; the username and password are yours, and they are the two values you should stop sending to other people.
2. Verify the upstream works before registering it
Run this against the http or https port. A 200 confirms the credentials, the port and the protocol are all correct, and that the failure is not upstream if anything goes wrong later. If you accidentally point this at the documented socks5 port, curl will fail in a way that looks like a dead proxy.
3. Register the upstream in Proxy Bastion and put it in a pool
A pool with one member works. Add more members if you want failover, keeping in mind that a pool whose members exit in different countries will make the recipient browser timezone disagree with the exit IP. We warn about that; we do not rewrite their fingerprint.
4. Issue one link per recipient
Set an expiry and a traffic ceiling per link. The recipient gets a relay link and never sees proxy.packetstream.io or your password. Revoking one link leaves every other link and your PacketStream credentials untouched. Two limits to know before you rely on either control: expect a revoked link to keep working for up to about 60 more seconds while the edge cache expires, and expect the traffic ceiling to be enforced from usage reported back in batches, so a link can overshoot it by up to about five minutes of traffic.
Sources
PacketStream documents the gateway host proxy.packetstream.io with HTTPS on port 31111, HTTP on port 31112 and socks5 on port 31113, and shows credentials either supplied separately or embedded as USERNAME:PASSWORD in the proxy URL. https://packetstream.io/docs/endpoints-authentication/(checked 2026-08-14)