Data as of Nov 4, 2026
203.78.208.0/20
3 residential-proxy exits · 30 daysVerizon Business · space held by Verizon Communications India Private Limited
Residential-proxy exits
Proxy exits
3
0.07% of its addresses · 30 days
Spread
3 of 16
/24s with at least one exit
Providers
8
selling exits here
Oct 5, 2026 – Nov 3, 2026
Exits seen per day
122 observations
/24s with the most always-on exits
| /24 | Always-on exits | Proxy exits | |
|---|---|---|---|
| 203.78.211.0/24 | 0 | 1 | |
| 203.78.217.0/24 | 0 | 1 | |
| 203.78.218.0/24 | 0 | 1 |
Proxy providers listing exits
- ByteProxies
- Byteful
- DataImpulse
- GonzoProxy
- InfiniteProxies
- NodeProxy
- ProxyGeo
- PuraRoute
Registrations in this block
The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 203.78.208.0/20 | 4,096 | VzB-IN-NETBLOCK | Verizon Communications India Private Limited (ORG-VCIP1-AP) · IN | ALLOCATED PORTABLE | — | abuse. |
| └ 203.78.208.0/28 | 16 | MIRAE-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.208.16/28 | 16 | ASPEN-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.209.0/25 | 128 | TCS-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.209.144/28 | 16 | PARAMOUNT-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.209.160/27 | 32 | CITRIX-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.209.192/26 | 64 | MAN-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.212.0/27 | 32 | PRECISION-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.212.32/27 | 32 | PYXIS-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.212.64/28 | 16 | CMS-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.212.96/28 | 16 | BAKER-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.212.128/25 | 128 | TECH-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.213.0/24 | 256 | IMG-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.214.0/25 | 128 | SAPIENT-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.214.128/28 | 16 | CAMP-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.214.160/27 | 32 | NDS-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.214.192/26 | 64 | MAINSTAY-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.215.0/24 | 256 | OCWEN-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.218.0/24 | 256 | TATA-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.219.0/24 | 256 | LIONBRIDGE-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.221.64/29 | 8 | UU-203-78-221-64 | SAP Kolkata | ALLOCATED NON-PORTABLE | — | abuse. |
| └ 203.78.221.128/25 | 128 | JET-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
| └ 203.78.222.0/24 | 256 | OCWEN-IN | UUNET Non-Portable Customer Assignment | ASSIGNED NON-PORTABLE | — | abuse. via VzB-IN-NETBLOCK |
A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.
Composition
The types across the prefix's announced space, by addresses.
Announced space
Address share
Announced space
Types across the prefix
4,096 addresses
| Type | Addresses | Share | Ranges | |
|---|---|---|---|---|
| Internet provider | 3,224 | 79% | 10 | |
| Business | 872 | 21% | 17 |
Network & registry
Origin network
AS703
US
- Name
- Verizon Business
- Type
- Internet provider
- Registered
- Aug 3, 1990
- Domain
- verizonbusiness.com
- Website
- www.verizon.com/business/
- Industry
- Internet Service Provider (ISP)
- Spamhaus ASN-DROP
- not listed
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2006
- Current origin since
- Sep 2016 · 10 yr
- Origin networks
- 1
IRR
Route objects on the exact prefix
| Origin | Registry | Description | Maintainer | Modified |
|---|---|---|---|---|
| AS703 | RADB | UUNET-VSNL Route Object | MAINT-VSNL-IN | Nov 13, 2023 |
Whois
Registration for this announcement
- Range
- 203.
78. 208. 0/ 20 - Netname
- VzB-IN-NETBLOCK
- Registrant
- Verizon Communications India Private Limited
- Registrant country
- IN
- Organization
- Not stated by the registry
- Type
- ALLOCATED PORTABLE
- Created
- Not stated by the registry
- Updated
- Oct 20, 2020
- Maintainer
- APNIC-HM
- RIR
- APNIC
- Country
- IN
- Delegated
- Dec 20, 2005
- Status
- assigned
Report abuse
Abuse contact
- abuse.
apac@ verizon. com - Name
- ABUSE VERIZONAU
- Handle
- AV293-AP