Data as of Nov 12, 2026

178.237.60.0/22

203 residential-proxy exits · 30 days

LLC Balttelecom

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

Residential-proxy exits

Proxy exits
203
20% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
76
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

8.9K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
178.237.60.0/24068
178.237.62.0/24050
178.237.63.0/24046
178.237.61.0/24038

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Datarama
  • Decodo
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GloryCloud
  • GonzoProxy
  • HPROXY
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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
178.237.60.0/221,024RU-BALTTELECOM-20180905LLC Balttelecom (ORG-FB13-RIPE) · RUALLOCATED PASep 5, 2018abuse.ripe@balttelecom.net
└ 178.237.60.0/24256ISP-BALTTELECOM-NETWORKWASP's pool 1ASSIGNED PASep 6, 2018abuse.ripe@balttelecom.net
via RU-BALTTELECOM-20180905
└ 178.237.61.0/24256ISP-BALTTELECOM-NETWORKWASP's pool 2ASSIGNED PASep 6, 2018abuse.ripe@balttelecom.net
via RU-BALTTELECOM-20180905
└ 178.237.62.0/24256ISP-BALTTELECOM-NETWORKWASP's pool 3ASSIGNED PASep 6, 2018abuse.ripe@balttelecom.net
via RU-BALTTELECOM-20180905
└ 178.237.63.0/24256ISP-BALTTELECOM-NETWORKWASP's pool 4ASSIGNED PASep 6, 2018abuse.ripe@balttelecom.net
via RU-BALTTELECOM-20180905

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