LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

192.174.4.0/22

5 residential-proxy exits · 30 days

Bell Canada

Announcement
this exact prefix
No RPKI
Announced by
AS54182
Type
Business

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
38
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FloppyData
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPMUSK
  • Infatica
  • KindProxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
192.174.5.0/24
since Jun 2021
AS54182BusinessBell Canada

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
192.174.4.0/221,024AXIA-ACL-NET-4Bell Canada (LINX) · CADirect AllocationAug 30, 2012abuse@bellnexxia.net
└ 192.174.4.0/2732ACL-NET-4unknown———
└ 192.174.4.32/2816ACL-NET-4unknown———
└ 192.174.4.48/298ACL-NET-4unknown———
└ 192.174.4.56/298ACL-NET-4unknown———
└ 192.174.4.64/2732ACL-NET-4unknown———
└ 192.174.4.96/304ACL-NET-4unknown———
└ 192.174.4.100/304ACL-NET-4unknown———
└ 192.174.4.104/298ACL-NET-4unknown———
└ 192.174.4.112/304ACL-NET-4unknown———
└ 192.174.4.116/304ACL-NET-4unknown———
└ 192.174.4.120/298ACL-NET-4unknown———
└ 192.174.4.128/2816ACL-NET-4unknown———
└ 192.174.4.144/2816ACL-NET-4unknown———
└ 192.174.4.160/298ACL-NET-4unknown———
└ 192.174.4.168/298ACL-NET-4unknown———
└ 192.174.4.176/304ACL-NET-4unknown———
└ 192.174.4.180/304ACL-NET-4unknown———
└ 192.174.4.184/304ACL-NET-4unknown———
└ 192.174.4.188/304ACL-NET-4unknown———
└ 192.174.4.192/2732ACL-NET-4unknown———
└ 192.174.4.224/298ACL-NET-4unknown———
└ 192.174.4.232/298ACL-NET-4unknown———
└ 192.174.4.240/298ACL-NET-4unknown———
└ 192.174.4.248/304ACL-NET-4unknown———
└ 192.174.4.252/304ACL-NET-4unknown———
└ 192.174.5.0/24256ACL-NET-4unknownReassignedJul 25, 2014abuse@bellnexxia.net
via AXIA-ACL-NET-4
└ 192.174.6.0/25128ACL-NET-4unknown———
└ 192.174.6.128/312ACL-NET-4unknown———
└ 192.174.6.130/312ACL-NET-4unknown———
└ 192.174.6.132/312ACL-NET-4unknown———
└ 192.174.6.134/312ACL-NET-4unknown———
└ 192.174.6.136/312ACL-NET-4unknown———
└ 192.174.6.138/312ACL-NET-4unknown———
└ 192.174.6.140/312ACL-NET-4unknown———
└ 192.174.6.142/312ACL-NET-4unknown———
└ 192.174.6.144/312ACL-NET-4unknown———
└ 192.174.6.146/312ACL-NET-4unknown———
└ 192.174.6.148/312ACL-NET-4unknown———
└ 192.174.6.150/312ACL-NET-4unknown———
└ 192.174.6.152/304ACL-NET-4unknown———
└ 192.174.6.156/304ACL-NET-4unknown———
└ 192.174.6.160/2732ACL-NET-4unknown———
└ 192.174.6.192/2816ACL-NET-4unknown———
└ 192.174.6.208/298ACL-NET-4unknown———
└ 192.174.6.224/2816ACL-NET-4unknown———
└ 192.174.6.240/2816ACL-NET-4unknown———
└ 192.174.7.0/25128ACL-NET-4unknown———
└ 192.174.7.128/298ACL-NET-4unknown———
└ 192.174.7.136/298ACL-NET-4unknown———
└ 192.174.7.144/304ACL-NET-4unknown———
└ 192.174.7.148/304ACL-NET-4unknown———
└ 192.174.7.152/298ACL-NET-4unknown———

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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