Data as of Nov 15, 2026

185.250.4.0/22

5 residential-proxy exits · 30 days

Monaco Telecom S.A.

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

Residential-proxy exits

Proxy exits
5
0.49% of its addresses · 30 days
Always-on exits
1
20% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
17
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.4K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.250.4.0/2413
185.250.6.0/2401
185.250.7.0/2401

Proxy providers listing exits

  • BottingTools
  • Byteful
  • Decodo
  • FastProxy
  • GSocks
  • IPFly
  • Infatica
  • KocerRoxy
  • LemonBright
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • PuraRoute
  • Thordata
  • ThunderProxy
  • 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.250.4.0/221,024MC-TELECOM-20180316Monaco Telecom S.A. (ORG-MT2-RIPE) · MCALLOCATED PAMar 16, 2018ipnetworks@monaco-telecom.mc
└ 185.250.4.0/24256Monaco-TelecomPROVIDERASSIGNED PAMar 19, 2018ipnetworks@monaco-telecom.mc
via MC-TELECOM-20180316
└ 185.250.5.0/24256Monaco-TelecomunknownASSIGNED PAMar 19, 2018ipnetworks@monaco-telecom.mc
via MC-TELECOM-20180316
└ 185.250.6.0/24256Monaco-TelecomunknownASSIGNED PAMar 19, 2018ipnetworks@monaco-telecom.mc
via MC-TELECOM-20180316
└ 185.250.7.0/24256Monaco-TelecomunknownASSIGNED PAMar 19, 2018ipnetworks@monaco-telecom.mc
via MC-TELECOM-20180316

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
Oct 2019
Current origin since
Jun 2025 · 1.4 yr
Origin networks
1