Data as of Nov 22, 2026

205.200.228.0/22

6 residential-proxy exits · 30 days

Bell Canada

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

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Always-on exits
1
17% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
30
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

2.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
205.200.230.0/2414
205.200.229.0/2401
205.200.231.0/2401

Proxy providers listing exits

  • BirdProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NSTPROXY_LITE
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy302
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
205.200.0.0/1665,536MTS-205-200-MB-CABell Canada (LINX) · CADirect AllocationMar 31, 1995abuse@bell.ca
└ 205.200.230.0/24256VCC-MB-CAunknown———

Network & registry

Routing timeline

Who has announced 205.200.0.0/16

205.200.0.0/16

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Sep 2015 · 11 yr
Origin networks
3
Last change of origin
Sep 2015
Recorded history

History

Handoffs
2