North America routing coverage

United States Proxies

3,203,665+ published proxy IPs in the United States. Residential, residential flex, datacenter, and mobile capability is reported by the compatibility endpoint; targeting, protocol, and session controls depend on the selected source.

Catalogue updated June 2026; verify current route availability and plan terms before ordering.

3,203,665+
Published IPs in the United States
4
Reported network types
734
Autonomous systems
#1
Pool rank in North America
3,203,665+ published IPs in the United States99.9% uptime targetTargeting depends on the selected sourceVerify protocol and session controlsDatabay Trust Center
Reported coverage

US residential, residential flex, datacenter, and mobile proxy coverage

The compatibility response reports network categories for the United States; it does not prove live inventory or source-specific targeting controls.

  • ISP-origin IPs for authorized regional sampling and workflows that require a consumer-network route.

    Global pool
    34M+ IPs
    Network origin
    ISP-classified
  • Residential Flex capability reported for this country; current availability and controls depend on the selected source.

    Global pool
    Flex network
    Network origin
    ISP-classified
  • Hosting-network IPs for authorized bulk and latency-sensitive workloads.

    Global pool
    80K+ IPs
    Network origin
    Hosting network
  • Mobile Proxies

    Configured

    4G and 5G carrier-network IPs for authorized app testing and mobile-network checks.

    Global pool
    800K+ IPs
    Network origin
    Mobile carrier

A network shows as Configured when it is present in the current compatibility response for the United States; this is not proof of live inventory. Global pool sizes are catalogue-wide. browse the current community proxy list for the United States as a separate public-endpoint dataset.

Geo-targeting

Review source-dependent targeting for the United States

The compatibility response lists network categories only. Confirm the selected source capability, current credential syntax, and observed exit before using a targeting control.

  • Country targeting capability

    A source capability flag can report country targeting for the United States; obtain the current credential syntax from the dashboard or documentation and verify the observed exit.

  • Source-advertised geo controls

    Use continent, country, city, ZIP, coordinate, or other geo flags only when the selected source advertises that capability.

  • Source-advertised ASN controls

    An ASN in the coverage response does not imply ASN targeting. Use an ASN flag only when the selected source advertises it.

  • Source-advertised sessions

    Rotation and sticky-session behavior depend on the selected source and current route availability; verify both before relying on continuity.

  • Use only targeting flags advertised by the selected source
  • Verify the observed country or ASN before use
  • Confirm rotation and sticky-session behavior in current documentation
  • Confirm protocol and authentication compatibility for the client

Sample of 734 autonomous systems covered in the United States

  • AS174 COGENT-174 - Cogent Communications, LLC
  • AS209 CENTURYLINK-US-LEGACY-QWEST - CenturyLink Communications, LLC
  • AS701 UUNET - Verizon Business
  • AS702 UUNET - Verizon Business
  • AS1088 FASTBRIDGE-FIBER-RDNG-PA-01 - FastBridge Fiber
  • AS1239 COGENT-1239 - Cogent Communications, LLC
  • AS1448 UNITED-BROADBAND - United Cooperative Services
  • AS1819 DCM-CABLE - DCM Cable Inc.
  • AS1820 WNET - WNET TELECOM USA Corp.
  • AS2711 SPIRITTEL-AS - Spirit Communications
  • AS2731 HORIZONTELCOM - Infinity Fiber LLC
  • AS2914 NTT-DATA-2914 - NTT America, Inc.

These ASNs are coverage evidence, not proof that ASN targeting is enabled. Check the selected source capability and verify the observed exit.

Credential examples are withheld

Configured country and network coverage does not prove the credential grammar, session flags, or source selection used by the production gateway. Review the current documentation and dashboard-issued credentials, then verify the observed exit.

Network performance

Network-wide operating targets for US routes

These catalogue-wide figures describe the service target, not a country-specific guarantee. Measure the exact route and workload before relying on it.

Uptime target
99.9%
Network-wide availability
Residential latency
~1.1s
Median response time
Datacenter latency
~780ms
Median response time
Session controls
Source-specific
Verify current source capability

Latency and uptime are network-wide medians and targets. See how Databay benchmarks its network.

Field guide

Need an ISP-origin network? Review residential proxies in the United States and confirm that the selected source advertises the controls you need. Testing public endpoints first? You can browse the current community proxy list for the United States as a separate, freshness-bounded dataset.

United States planning artifact

Plan the required precision, then preserve a route record

Use this control sheet before an authorized comparison. It separates the requested network-origin hypothesis from the other signals that can change a search, ad, store, or checkout result.

United States precision planning matrix
Test hypothesisRequested route inputHold constantAcceptance evidence
National experienceCountry-level input, if supported for the route under reviewURL, language, device, cookies, account, and timestamp windowObserved exit country plus the direct and routed page outcomes
State or metro experienceOne region-level input, recorded exactly as requestedStore, delivery fixture, campaign preview, account, and browser stateObserved region, lookup source, and any mismatch or fallback
ZIP or precise-origin hypothesisOne postal, coordinate, or network-owner input—not a combined selectorAddress, tax fixture, currency, inventory time, and personalizationThe requested input, observed result, failure class, and UTC time

Bounded route record

Request
Route input and test URL
Observation
Country or region and lookup source
Connection
New-connection identifier and sequence
Controls
Account, locale, address, store, and cookies
Failures
Timeout, mismatch, refusal, or content difference
Time
Start and finish in UTC

An observed U.S. exit is one input, not proof of a resident identity, tax outcome, or guaranteed search or ad result.

Buy US proxies by the precision the authorized test requires

A buyer searching to buy US proxies should begin with the smallest geographic question that can answer the authorized workflow: country, state, city, ZIP, coordinate, or ASN. Only if fresh, complete coverage confirms Premium Residential may its narrower controls be evaluated. A targeted request uses exactly one eligible geographic selector at a time; those country, state, city, ZIP, coordinate, and ASN controls cannot be combined. Requested precision must be checked against the independently observed exit. The allocation remains shared and does not reproduce a household or resident. Account creation purchases general-pool access rather than a separately orderable United States product, reserved location, or country-specific stock. Mark the product inappropriate if its confirmed controls cannot meet the written requirement.

Use a US storefront sheet that holds non-network controls fixed

For an owned or otherwise authorized US storefront, create one direct-control row and one routed row with the URL, selected store, delivery address, account, cookies, browser language, currency, basket, and timestamp held constant. Record the landing page, displayed price, promotion, pickup or delivery availability, tax estimate, final total, response class, and a safe content digest. A United States route can contribute a network-origin signal, but it does not select a store, set the delivery address, determine tax, or guarantee the same result for another visitor. Keep stale, personalized, challenged, partial, and missing outcomes. If inventory time or another fixture changes, start a new labelled comparison rather than attributing the difference automatically to geography.

Build a US route card before accepting local precision

A US route card should retain the exact product, coverage observation time and freshness, one requested selector, redacted session fingerprint, successful proxy handshake, hashed exit, observed country and region, named geolocation source, managed protocol, new-connection behavior, requested continuity, response class, latency and failure methodology, bytes, UTC time, and evidence hash. Keep requested state, city, ZIP, coordinate, or ASN separate from what the independent lookup actually reports. Conflicting sources make the United States observation unresolved; they do not justify choosing the preferred value. One successful connection proves only that bounded observation. It does not promise future routing, destination acceptance, session continuity, or the same local result at another time.

Test US search and owned-campaign presentation without overclaiming location

For US local-search or owned-campaign QA, use the service's preview or diagnostic facility first, then add a routed observation only when the network path is part of the question. Fix the query or campaign, URL, language, device class, account, cookies, personalization, time, and acceptance rule. Record the requested and observed geography, result or creative identifier, landing page, disclosure state, response, and UTC time. A United States IP is one location signal among several and cannot guarantee a particular search result, advert, audience classification, or resident experience. Use only campaigns and pages the team is authorized to inspect, and stop at a challenge, denial, account warning, or other destination control rather than changing identities to continue.

Pass a US cost-per-accepted-result gate before scaling

Within the North America catalogue, the United States' 3,203,665 figure is a manually refreshed annual total of historical IPs seen so far, not exact-product coverage, current routing evidence, simultaneous capacity, or a success rate. Before scaling a US workload, define one harmless authorized destination, request ceiling, timeout, retry allowance, connection reuse, accepted outcome, failure classes, transferred-byte method, and maximum cost per accepted result. Retain valid, challenged, denied, rate-limited, timed-out, and inconclusive attempts in the denominator. A new proxy connection may select an available exit, while a reused connection or tunnel can retain one; neither behavior guarantees a new address. Buy additional volume only if the fresh recorded configuration passes its prewritten threshold and current destination terms.

United States proxies

Frequently asked questions

How many proxy IPs does Databay have in the United States?
The 3,203,665+ figure is Databay's all-network catalogue count for the United States, not a per-network or live-inventory claim. Current configured capability includes residential, residential flex, datacenter, and mobile; routing and targeting controls depend on the selected source, and the observed exit must be verified.
What types of proxies are available in the United States?
Databay currently reports configured residential, residential flex, datacenter, and mobile capability in the United States. Protocol and session controls must be confirmed for the selected source.
Which networks and ASNs are covered in the United States?
Configured coverage in the United States references 734 autonomous systems across 4 reported network types. This does not imply ASN targeting; use that control only when the selected source advertises it.
How do I authenticate with Databay proxies?
Authentication is by username and password over the documented gateway. Use only targeting and session flags advertised by the selected source capability.
Which protocols are supported?
The location-capability check does not attest protocol or session support. Confirm the current gateway protocols and controls for the selected source in the dashboard and documentation.
Is there an API?
Use the documented API and gateway interfaces shown for the selected product. Do not infer pool, geo, protocol, or session controls from a country catalogue count.
How do I get started?
Create an account, choose a plan, and the dashboard issues gateway credentials you can use immediately.
Where can I verify current reseller or volume options?
Use the live product pricing pages for current self-serve terms and contact sales for requirements not listed there. Do not assume an older quantity, price, or reseller option remains available.

Review current United States proxy options

Review the reported US network category, then verify the selected source, observed route, and current plan terms.

Pricing, order minimums, and traffic validity vary by product.