Data as of Nov 13, 2026

203.95.8.0/21

1 residential-proxy exit · 30 days

Pacific Data Systems

Announcement
this exact prefix
RPKI valid
Announced by
Type
Internet provider
>99% of it

Residential-proxy exits

Proxy exits
1
0.05% of its addresses · 30 days
Spread
1 of 8
/24s with at least one exit
Providers
2
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • NovaProxy
  • ProxyEmpire

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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
203.95.8.0/212,048PDSGUAMPacific Data Systems (ORG-PDS1-AP) · GUALLOCATED PORTABLE—abuse@pdsguam.com
└ 203.95.8.1/321PDS-CORE-HIPDSHawaii Core BGP SpeakerASSIGNED NON-PORTABLE—abuse@pdsguam.com
via PDSGUAM
└ 203.95.8.2/321PDS-CORE-GUPDSGuam Core BGP SpeakerASSIGNED NON-PORTABLE—abuse@pdsguam.com
via PDSGUAM
└ 203.95.8.3/321PDS-CORE-SPNPDSSaipan Core BGP SpeakerASSIGNED NON-PORTABLE—abuse@pdsguam.com
via PDSGUAM
└ 203.95.8.20/321PDS-CORE-LAPDSLA Core BGP SpeakerASSIGNED NON-PORTABLE—abuse@pdsguam.com
via PDSGUAM
└ 203.95.12.128/298PDS-CUST-PSS_HOGROAST-PROXYPDS Non-Portable Customer AssignmentASSIGNED NON-PORTABLE—abuse@pdsguam.com
via PDSGUAM

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

2,048 addresses
TypeAddressesShareRanges
Internet provider2,036>99%4
Business120.59%5

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2005
Current origin since
Dec 2005 · 21 yr
Origin networks
1