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

62.78.32.0/19

479 residential-proxy exits · 30 days

Limited Liability Company WELLCOM-L

Announcement
this exact prefix
RPKI valid
Announced by
AS50289
Type
Residential

Residential-proxy exits

Proxy exits
479
5.8% of its addresses · 30 days
Spread
27 of 32
/24s with at least one exit
Providers
66
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

14K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
62.78.41.0/24027
62.78.57.0/24025
62.78.43.0/24024
62.78.56.0/24022
62.78.47.0/24022
62.78.63.0/24021
62.78.44.0/24021
62.78.46.0/24020
62.78.39.0/24020
62.78.45.0/24020
62.78.52.0/24020
62.78.60.0/24019
62.78.61.0/24018
62.78.53.0/24018
62.78.50.0/24018
62.78.37.0/24017
62.78.62.0/24017
62.78.40.0/24016
62.78.55.0/24016
62.78.42.0/24016
62.78.59.0/24016
62.78.38.0/24016
62.78.51.0/24015
62.78.54.0/24013

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BestProxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • Geonode
  • GhostConnect
  • GloryCloud
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LudaxProxy
  • MoMoProxy
  • NextProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYON
  • PROXYSCRAPE
  • PacketStream
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • PuraRoute
  • Q2IP
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • Smartproxy
  • StrikeProxy
  • SwiftProxy
  • TrueProxies
  • VantageProxies
  • ZENPROXY_LITE
  • ZENPROXY_PREMIUM

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
62.78.32.0/24
since Oct 2019
AS50289ResidentialLimited Liability Company WELLCOM-L
62.78.34.0/24
since Feb 2019
AS50289Residential1Limited Liability Company WELLCOM-L
62.78.35.0/24
since Sep 2019
AS50289Residential7Limited Liability Company WELLCOM-L
62.78.36.0/22
since Aug 2016
AS50289Residential66Limited Liability Company WELLCOM-L
62.78.40.0/21
since Oct 2019
AS50289Residential166Limited Liability Company WELLCOM-L
62.78.50.0/24
since Oct 2019
AS50289Residential18Limited Liability Company WELLCOM-L
62.78.51.0/24
since Oct 2019
AS50289Residential15Limited Liability Company WELLCOM-L
62.78.52.0/22
since Aug 2016
AS50289Residential67Limited Liability Company WELLCOM-L
62.78.56.0/21
since Oct 2019
AS50289Residential138Limited Liability Company WELLCOM-L

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
62.78.32.0/198,192RU-WELLCOMM-20091215Limited Liability Company WELLCOM-L (ORG-LLCW2-RIPE) · RUALLOCATED PADec 15, 2009abuse@well-comm.ru
└ 62.78.32.0/24256RU-WELLCOMM-IPV4-B1WELLCOM-L Broadband users 1ASSIGNED PAJun 10, 2020abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.33.0/24256WELLCOM-NETMetro Ethernet Internet Service ProviderASSIGNED PADec 15, 2009abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.34.0/24256WELLCOM-NETMetro Ethernet Internet Service ProviderASSIGNED PADec 15, 2009abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.35.0/24256WELLCOM-NETMetro Ethernet Internet Service ProviderASSIGNED PADec 15, 2009abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.36.0/221,024WELLCOM-NETWellcom Broadband UsersASSIGNED PAJul 7, 2010abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.40.0/212,048RU-WELLCOMM-IPV4-B2WELLCOM-L Broadband users 2ASSIGNED PAJun 10, 2020abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.48.0/24256WELLCOM-NETWellcom Broadband UsersASSIGNED PAJul 13, 2016abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.49.0/24256WELLCOM-NETWellcom Broadband UsersASSIGNED PAJul 13, 2016abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.50.0/24256RU-WELLCOMM-IPV4-B3WELLCOM-L Broadband users 3ASSIGNED PAJun 10, 2020abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.51.0/24256RU-WELLCOMM-IPV4-B4WELLCOM-L Broadband users 4ASSIGNED PAJun 10, 2020abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.52.0/221,024WELLCOM-NETWellcom Broadband UsersASSIGNED PAJul 13, 2016abuse@well-comm.ru
via RU-WELLCOMM-20091215
└ 62.78.56.0/212,048RU-WELLCOMM-IPV4-B5WELLCOM-L Broadband users 5ASSIGNED PAJun 10, 2020abuse@well-comm.ru
via RU-WELLCOMM-20091215

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
May 2005
Current origin since
Aug 2016 · 10 yr
Origin networks
3
Last change of origin
Dec 2009
Recorded history

History

Handoffs
2