Bright Data ISP proxies: how do I buy a small block of static IPs and keep the same session?

Most teams looking at Bright Data ISP proxies want two things at once: a small, predictable block of IPs they can keep, and the ability to hold a stable session so sites behave like they’re talking to a real, consistent user. You can do both with Bright Data’s ISP proxy product by combining dedicated static IP allocation with sticky sessions in your connection settings or Proxy Manager.

Quick Answer: Buy a small pool of dedicated ISP proxies in your required country/region, then configure sticky sessions (via session IDs) so each connection keeps using the same IP for as long as you need. With Bright Data, you can retain those static ISP IPs, target specific locations, and control session duration through simple connection parameters or the built-in Proxy Manager.

Why This Matters

If you’re running login-based workflows, price monitoring dashboards, or AI agents that need to “stay logged in,” rotating IPs every request can break everything. Static ISP proxies plus sticky sessions give you a stable identity on target sites while still benefiting from ISP-grade reliability and geo targeting.

This combination reduces bans, keeps cookies and sessions valid, and removes the need to constantly re-authenticate or re-warm browsers.

Key Benefits:

Stable identity for sensitive workflows: Keep the same ISP IP for days or weeks, so logins, carts, and dashboards stay intact.
Session control without reinventing your stack: Use simple session parameters or Proxy Manager rules instead of custom “IP pinning” logic.
Reliable access under pressure: Combine static ISP IPs with Bright Data’s unblocking stack for high success rates on public, dynamic sites.

Core Concepts & Key Points

Concept	Definition	Why it's important
ISP proxies	Residential-grade IPs provided by ISPs rather than end-user devices; Bright Data offers 1,300,000+ fast, stable ISP IPs.	Behave like real consumer connections, reducing blocks and improving trust on target sites.
Static IP block	A dedicated set of IP addresses you exclusively control and can keep for as long as you need.	Enables consistent identity, whitelist-based access, and predictable behavior across sessions.
Sticky sessions	A connection strategy where the same IP is reused over time by using a session ID, instead of rotating every request.	Preserves logins, cookies, and app state, which is critical for dashboards, carts, and multi-step flows.

How It Works (Step-by-Step)

At a high level, you do two things: purchase a small dedicated ISP pool, then configure your connections for sticky sessions.

1. Choose and purchase a small ISP proxy block

You’ll start in the Bright Data dashboard:

Create a new proxy zone and select ISP as the network type.
Choose your country and city targeting (Bright Data supports 195+ countries and major cities worldwide for dedicated proxies).
Select dedicated IPs and specify how many you want in your small block (e.g., 5–50 IPs depending on your use case).
Confirm pricing and provisioning; ISP IPs are residential-grade, fast, and stable, making them ideal for session-heavy workflows.

Outcome: you now have a dedicated ISP zone with a small private pool of static IPs you can retain as long as you keep the subscription.

2. Configure access with static behavior

Once your ISP zone is ready, you can connect in two main ways:

Directly from code/tooling using Bright Data’s proxy endpoint (host + port + credentials).
Through Bright Data Proxy Manager, which adds more advanced controls (rules, IP pinning, custom headers, retries).

Key configuration points for “small block + static behavior”:

Use the ISP zone credentials assigned to your account.
Set country and city targeting (either in the zone or via parameters) to match your chosen block.
Use the dedicated IP mode (no sharing with other customers) so your block isn’t rotated with external traffic.

3. Enable and manage sticky sessions

Static IPs give you a stable pool; sticky sessions keep a specific IP attached to a workflow.

There are two common patterns:

Option A: Sticky sessions via session ID

For most HTTP(s) clients, you’ll pass a session parameter in the username or as a query parameter, for example:

curl -x "http://user-session-123:password@brd.superproxy.io:22225" https://target-site.com

Reuse "session-123" across multiple requests to keep the same IP.
Change the session ID (e.g., session-124) when you want a different IP from your block.
Configure session TTL (time-to-live) in the zone/Proxy Manager so sessions last minutes, hours, or longer, depending on your needs.

Option B: Sticky sessions via Proxy Manager

If you’re using Bright Data’s Proxy Manager:

Add your ISP zone as a new proxy port in Proxy Manager.
Under IP control / session settings, enable sticky sessions and define:
- Session duration (e.g., 10 minutes, 1 hour, custom).
- Whether stickiness is keyed by requester IP, header, or custom session ID.
Point your scraper, app, or AI agent at the Proxy Manager port (e.g., localhost:24000).

Proxy Manager then:

Pins session IDs to specific ISP IPs within your dedicated block.
Handles retries, failover, and IP re-assignment if one IP becomes unstable.
Lets you add rules for headers, cookies, JS rendering, and more, without changing your scraping code.

Common Mistakes to Avoid

Assuming ISP automatically means static:
ISP is a network type, not a guarantee of stickiness. You still need dedicated allocation + sticky session configuration to behave like a static IP block.
Not controlling session TTL for your workflow:
If your session TTL is too short, your “static” identity will unexpectedly change mid-workflow. Align TTL with your typical session length (e.g., 30–60 minutes for a shopping flow, several hours for monitoring dashboards).
Mixing rotating and static behaviors in the same zone:
If some code paths use session IDs and others don’t, you’ll see unpredictable IP behavior. Standardize on always passing a session ID for workflows that must keep the same IP.

Real-World Example

A pricing team runs a browser-based monitoring tool that logs into multiple retailer portals, pulls price tables, and exports them to Snowflake in CSV/JSON. Using generic rotating proxies, they kept getting:

Logouts mid-session when IPs changed.
Extra 2FA prompts and CAPTCHAs.
Blocked dashboards after too many suspicious logins.

They switched to a small block of 20 dedicated ISP IPs in key markets and accessed them through Bright Data Proxy Manager:

Each retailer integration uses a dedicated session ID, mapped to one ISP IP.
Sessions are configured to stay sticky for 90 minutes, aligning with their data pull windows.
Structured outputs are collected and pushed to S3 and Snowflake on schedule, with far fewer login failures.

Result: fewer firefights, stable dashboards, and a predictable cost model driven by successful data delivery instead of raw bandwidth.

Pro Tip: Treat each long-lived workflow (per account, per store, or per bot/agent) as its own session ID. That way, if one IP is ever rate-limited or challenged, you can switch that session to a new IP from your small ISP block without touching the other flows.

Summary

To buy a small block of static Bright Data ISP proxies and keep the same session:

Set up a dedicated ISP proxy zone with the number of IPs and locations you need.
Connect via the zone endpoint or Proxy Manager, making sure you’re in dedicated mode.
Implement sticky sessions using session IDs and sensible TTLs so each workflow keeps the same IP from your block.

You end up with residential-grade ISP IPs that look like real users, stay stable over time, and can be controlled programmatically—ideal for login-based scraping, AI agents, and sensitive dashboards.

Next Step

Get Started