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

199.167.24.0/22

6 residential-proxy exits · 30 days

Bell Canada

Announcement
this exact prefix
No RPKI
Announced by
AS54182
Type
Business

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Always-on exits
2
33% of its exits
Spread
1 of 4
/24s with at least one exit
Providers
41
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

6.1K observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • Infatica
  • Kookey
  • LemonBright
  • LudaxProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Thordata
  • ThunderProxy
  • TrueProxies
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

More specific

Announcements inside

PrefixOriginTypeHolderRPKI
199.167.24.0/24
since Nov 2017
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
199.167.24.0/221,024AXIA-ACL-NET-3Bell Canada (LINX) · CADirect AllocationMar 22, 2012abuse@bellnexxia.net
└ 199.167.24.0/24256ACL-NET-3-COMTECHunknownReassignedOct 6, 2014abuse@bellnexxia.net
via AXIA-ACL-NET-3
└ 199.167.25.0/2732ACL-NET-3-COMTECHunknown———
└ 199.167.25.32/2816ACL-NET-3-COLDLAKEunknown———
└ 199.167.25.48/2816ACL-NET-3-COMM-COLDLAKEunknown———
└ 199.167.25.64/2732ACL-NET-3-COMM-COLDLAKEunknown———
└ 199.167.25.96/298ACL-NET-3-COMM-COLDLAKEunknown———
└ 199.167.25.104/298ACL-NET-3-BANFFCENTREunknown———
└ 199.167.25.112/298ACL-NET-3unknown———
└ 199.167.25.128/25128ACL-NET-3unknown———
└ 199.167.26.0/2816ACL-NET-3unknown———
└ 199.167.26.16/2816ACL-NET-3unknown———
└ 199.167.26.32/2732ACL-NET-3unknown———
└ 199.167.26.64/298ACL-NET-3unknown———
└ 199.167.26.72/298ACL-NET-3unknown———
└ 199.167.26.80/2816ACL-NET-3unknown———
└ 199.167.26.96/304ACL-NET-3unknown———
└ 199.167.26.100/304ACL-NET-3unknown———
└ 199.167.26.104/304ACL-NET-3unknown———
└ 199.167.26.108/312ACL-NET-3unknown———
└ 199.167.26.110/312ACL-NET-3unknown———
└ 199.167.26.112/2816ACL-NET-3unknown———
└ 199.167.26.128/2816ACL-NET-3unknown———
└ 199.167.26.144/298ACL-NET-3unknown———
└ 199.167.26.152/298ACL-NET-3unknown———
└ 199.167.26.160/2732ACL-NET-3unknown———
└ 199.167.26.192/2816ACL-NET-3unknown———
└ 199.167.26.208/298ACL-NET-3unknown———
└ 199.167.26.216/312ACL-NET-3unknown———
└ 199.167.26.218/312ACL-NET-3unknown———
└ 199.167.26.220/304ACL-NET-3unknown———
└ 199.167.26.224/298ACL-NET-3unknown———
└ 199.167.26.232/298ACL-NET-3unknown———
└ 199.167.26.240/298ACL-NET-3unknown———
└ 199.167.26.248/298ACL-NET-3unknown———
└ 199.167.27.0/24256ACL-NET-3unknown———

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