Data as of Nov 11, 2026

31.187.80.0/22

23 residential-proxy exits · 30 days

KOMRO Gesellschaft fuer Telekommunikation mit beschraenkter Haftung

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

Residential-proxy exits

Proxy exits
23
2.2% of its addresses · 30 days
Always-on exits
2
8.7% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
61
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

3.1K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
31.187.82.0/24111
31.187.83.0/2413
31.187.81.0/2407
31.187.80.0/2402

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • Shifter
  • StrikeProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

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
31.187.80.0/221,024DE-KOMRO-20110325KOMRO Gesellschaft fuer Telekommunikation mit beschraenkter Haftung (ORG-KG3-RIPE) · DEALLOCATED PAFeb 29, 2016abuse@komro.net
└ 31.187.80.0/24256komroDynamic Address CMTSASSIGNED PAMar 1, 2016abuse@komro.net
via DE-KOMRO-20110325

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
Jan 2015
Current origin since
Mar 2016 · 11 yr
Origin networks
3
Last change of origin
Mar 2016
Recorded history

History

Handoffs
2