Data as of Nov 15, 2026

185.207.60.0/22

18 residential-proxy exits · 30 days

Mainzer Breitband GmbH

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

Residential-proxy exits

Proxy exits
18
1.8% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

566 observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Extract
  • AnyIP
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FloppyData
  • GSocks
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

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
185.207.60.0/221,024DE-MAINZER-BREITBAND-20170607Mainzer Breitband GmbH (ORG-MBG11-RIPE) · DEALLOCATED PAJun 7, 2017ripe@mainzer-breitband.de
└ 185.207.60.0/24256Infra-MB-v4Infrastructure IPV4 by Mainzer BreitbandASSIGNED PAJun 13, 2017ripe@mainzer-breitband.de
via DE-MAINZER-BREITBAND-20170607
└ 185.207.62.0/24256Infra-MB-Cust-IntAccess-v4Infrastructure Customer Internet Access by Mainzer BreitbandASSIGNED PAJun 13, 2017ripe@mainzer-breitband.de
via DE-MAINZER-BREITBAND-20170607

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
Jul 2017
Current origin since
Jul 2017 · 9.3 yr
Origin networks
1