Data as of Nov 20, 2026

146.234.0.0/16

4 residential-proxy exits · 30 days

Fraport AG Frankfurt Airport Services Worldwide

Announcement
this exact prefix
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
4
<0.01% of its addresses · 30 days
Spread
4 of 256
/24s with at least one exit
Providers
6
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

48 observations

/24s with the most always-on exits

Proxy providers listing exits

  • AnyIP
  • EnigmaProxy
  • FloppyData
  • NovaProxy
  • ProxyEmpire
  • VantageProxies

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
146.234.0.0/19
since Sep 2022
AS43857Business1Fraport AG Frankfurt Airport Services Worldwide
146.234.32.0/19
since Sep 2022
AS43857BusinessFraport AG Frankfurt Airport Services Worldwide
146.234.64.0/19
since Sep 2022
AS43857Business3Fraport AG Frankfurt Airport Services Worldwide
146.234.96.0/19
since Sep 2022
AS43857BusinessFraport AG Frankfurt Airport Services Worldwide
146.234.128.0/19
since Sep 2022
AS43857BusinessFraport AG Frankfurt Airport Services Worldwide
146.234.160.0/19
since Sep 2022
AS43857BusinessFraport AG Frankfurt Airport Services Worldwide
146.234.192.0/19
since Sep 2022
AS43857BusinessFraport AG Frankfurt Airport Services Worldwide
146.234.255.0/24
since Aug 2022
AS43857BusinessFraport AG Frankfurt Airport Services Worldwide

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
146.234.0.0/1665,536FAIRNETFraport AG Frankfurt Airport Services Worldwide (ORG-FRA5-RIPE) · DELEGACY—abuse@fraport.de
└ 146.234.203.0/24256FAIRNETFraport AGLEGACYOct 10, 2007abuse@fraport.de
via FAIRNET

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Dec 2007 · 19 yr
Origin networks
2
Last change of origin
Dec 2007
Recorded history

History

Handoffs
1