Data as of Nov 17, 2026

31.204.136.0/23

27 residential-proxy exits · 30 days

i3D.net B.V

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
27
5.3% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
1
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

29 observations

Proxy providers listing exits

  • BlurPath

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
31.204.128.0/19
since May 2011
AS49544Hosting26i3D.net B.V

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
31.204.128.0/198,192NL-I3DNET-20110429i3D.net B.V (ORG-IA772-RIPE) · NLALLOCATED PAApr 29, 2011abuse@i3d.net
└ 31.204.136.0/23512i3Dnet-frmtl1unknownSUB-ALLOCATED PAMay 3, 2023abuse@i3d.net
via NL-I3DNET-20110429
└ 31.204.136.0/2816i3Dnet-frmtl1-k135850-infraunknownASSIGNED PAJul 19, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.16/2816i3Dnet-frstd1-k135850-infraunknownASSIGNED PAJul 19, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.32/2816i3Dnet-frmtl1-k783233unknownASSIGNED PAOct 21, 2023abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.48/2816i3Dnet-frmtl1-k783233unknownASSIGNED PAOct 21, 2023abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.64/2732i3Dnet-frmtl1-K786305unknownASSIGNED PAApr 18, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.96/2732i3Dnet-frmtl1-k812769unknownASSIGNED PANov 17, 2023abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.128/2664i3Dnet-frmtl1-k812773unknownASSIGNED PAOct 21, 2023abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.136.192/2664i3Dnet-frmtl1-K805877unknownASSIGNED PAJun 18, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.0/2664i3Dnet-frmtl1-K795150unknownASSIGNED PAJul 2, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.64/2816i3Dnet-frmtl1-k135850-infraunknownASSIGNED PAJul 8, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.80/2816i3Dnet-frmtl1-K812425unknownASSIGNED PAAug 19, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.96/2816i3Dnet-frmtl1-K812425unknownASSIGNED PAAug 20, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.112/2816i3Dnet-frmtl1-K787685unknownASSIGNED PANov 4, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.128/2732i3Dnet-frmtl1-K805877unknownASSIGNED PAJun 18, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.160/2732i3Dnet-frmtl1-K800129unknownASSIGNED PAOct 7, 2025abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.192/2816i3Dnet-frmtl1-k804777unknownASSIGNED PASep 16, 2024abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.208/2816i3Dnet-frmtl1-k173665unknownASSIGNED PAOct 21, 2023abuse@i3d.net
via i3Dnet-frmtl1
└ 31.204.137.224/2732i3Dnet-frmtl1-K786305unknownASSIGNED PAApr 18, 2024abuse@i3d.net
via i3Dnet-frmtl1

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2023
Current origin since
Mar 2023 · 3.6 yr
Origin networks
1