Data as of Nov 12, 2026

45.83.164.0/22

3 residential-proxy exits · 30 days

MyComms Ltd

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

Residential-proxy exits

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

Exits seen per day

5 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
45.83.164.0/2402
45.83.166.0/2401

Proxy providers listing exits

  • AnyIP
  • Byteful
  • FloppyData
  • NovaProxy
  • RainProxy
  • Shifter

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
45.83.164.0/221,024UK-MYCOMMS-20190528MyComms Ltd (ORG-ML593-RIPE) · GBALLOCATED PAMay 28, 2019abuse@mycomms.org
└ 45.83.164.0/24256mycommsblock1unknownASSIGNED PAJul 1, 2024abuse@mycomms.org
via UK-MYCOMMS-20190528
└ 45.83.165.0/24256mycommsblock2unknownASSIGNED PAJul 1, 2024abuse@mycomms.org
via UK-MYCOMMS-20190528
└ 45.83.166.0/24256mucommsblock3unknownASSIGNED PAJul 1, 2024abuse@mycomms.org
via UK-MYCOMMS-20190528
└ 45.83.167.0/24256mycommsblock4unknownASSIGNED PAJul 1, 2024abuse@mycomms.org
via UK-MYCOMMS-20190528

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