DataImpulse with Proxy Bastion

Last checked 2026-08-14

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.

DataImpulse documents two authentication methods: a username and password pair, and IP-based allowlisting. Which one your plan uses decides whether this setup helps you at all. With credentials, we hold them and hand out links instead. With allowlisting, the thing that authorises traffic is the source IP, so what you would be sharing is reachability from our egress rather than a credential, and you should check that our egress IP is on your allowlist before assuming it works.

We have not published a DataImpulse gateway host or port here, because their documentation pages we could reach do not state them. Take those from your own dashboard and verify them with the command in step two. We are not affiliated with DataImpulse and we do not resell their traffic.

What is supported

  • Upstream protocols: http, https
  • socks5 upstreams: not supported in this release

Gateway details we could confirm

Credential format Either a username and password pair, or IP-based allowlisting; the documentation lists both as supported methods

Setup

1. Determine which authentication method your plan is on

This decides everything that follows. If the plan authenticates by source IP rather than by credentials, then a credential you paste anywhere is not what grants access, and the allowlist has to include the address traffic actually leaves from.

2. Verify the upstream before registering it

Substitute your own host, port and credentials. A 200 confirms host, port, protocol and credentials together. On a credential-based plan this is conclusive; on an allowlist plan a success here only proves your own machine is allowlisted, which is not the same thing.

curl -sS -o /dev/null -w 'http_code=%{http_code}\n' --max-time 15 --proxy 'http://USER:PASS@HOST:PORT' https://example.com

3. On an allowlist plan, find out what your own egress IP is

The empty proxy value is deliberate, not a typo: it overrides any http_proxy or https_proxy environment variable and forces a direct request, so you get your own address rather than whatever a configured proxy would report. Check that address against the allowlist in the dashboard.

curl -sS --max-time 15 --proxy '' https://api.ipify.org

4. Register the upstream, pool it, then issue one link per recipient

Each link carries its own expiry and traffic ceiling, and the recipient never sees the upstream host or password. Two limits to know before you rely on either control: a revoked link can stay usable for up to about 60 more seconds while the edge cache expires, and the traffic ceiling is enforced from usage reported back in batches, so a link can overshoot it by up to about five minutes of traffic.

Sources

  • DataImpulse documentation lists two supported authentication methods, username and password, and IP-based whitelisting. The authentication overview page states no gateway hostname, port or credential string format. https://docs.dataimpulse.com/authentication-methods (checked 2026-08-14)
  • The DataImpulse proxies documentation page lists the proxy product types and navigation, and does not state a gateway hostname, port, credential format or supported protocols. https://docs.dataimpulse.com/proxies (checked 2026-08-14)