Data as of Nov 14, 2026

5.179.72.0/21

1 residential-proxy exit · 30 days

4COM Technologies Limited

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

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

Exits seen per day

9 observations

Proxy providers listing exits

  • NovaProxy

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
5.179.72.0/212,048UK-4COMPLC-201208074COM Technologies Limited (ORG-PA516-RIPE) · GBALLOCATED PAAug 7, 20124com-noc@zananet.com
└ 5.179.72.0/2816FOURCOMrouter loopbacksASSIGNED PAFeb 5, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.16/2816FOURCOMrouter coreASSIGNED PAFeb 5, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.32/298FOURCOMroutes BTASSIGNED PAFeb 16, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.40/298FOURCOMrouter core 2ASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.48/298FOURCOMrouter core 3ASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.56/298FOURCOMrouter core 4ASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.64/2664FOURCOMDNS Radius MonitorASSIGNED PAFeb 5, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.128 - 5.179.72.15124FOURCOMMail HTTP VPNASSIGNED PAFeb 16, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.152/304FOURCOMHTTP serverASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.160/2816FOURCOM6to4 NATASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.72.192/2664FOURCOMVOIP systemsASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.73.0/24256FOURCOMCustomer DSLASSIGNED PAFeb 16, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.74.0/24256FOURCOMCustomer DSLASSIGNED PAFeb 16, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.75.0/24256FOURCOMCustomer DSL /32 assignmentsASSIGNED PAFeb 16, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.76.0/24256FOURCOMCustomer DSL /32 assignmentsASSIGNED PAOct 16, 20134com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.77.0/24256FOURCOMCustomer DSL /32 assignmentsASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.78.0/24256FOURCOMCustomer DSLASSIGNED PAJun 18, 20144com-noc@zananet.com
via UK-4COMPLC-20120807
└ 5.179.79.0/24256FOURCOMInfrastructureASSIGNED PASep 30, 20214com-noc@zananet.com
via UK-4COMPLC-20120807

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
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1