Data as of Nov 6, 2026
5.11.62.0/23
1 residential-proxy exit · 30 daysM2 Connect LLC
Residential-proxy exits
Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
2
selling exits here
Oct 7, 2026 – Nov 5, 2026
Exits seen per day
79 observations
Proxy providers listing exits
- IPFly
- PuraRoute
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.
| Range | Addresses | Netname | Holder | Type | Created | Abuse contact |
|---|---|---|---|---|---|---|
| 5.11.60.0/22 | 1,024 | RU-T2TELECOM-20190227 | M2 Connect LLC (ORG-TTL45-RIPE) · RU | ALLOCATED PA | Dec 20, 2024 | ak@ |
| └ 5.11.62.0/23 | 512 | RU-T2TELECOM-20251102 | unknown | ASSIGNED PA | Feb 28, 2019 | ak@ via RU-T2TELECOM-20190227 |
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
Registry
Holder
- Organization
- M2 Connect LLC
- Handle
- ORG-TTL45-RIPE
- Range
- 5.
11. 60. 0/ 22 - Registration type
- ALLOCATED PA
- Record created
- Dec 20, 2024
Routing timeline
Who has announced this prefix
Summary
Routing history
- Pattern
- Stable
- First seen
- Feb 2025
- Current origin since
- Feb 2025 · 1.7 yr
- Origin networks
- 1
Whois
Registration for this announcement
- Range
- 5.
11. 62. 0/ 23 - Netname
- RU-T2TELECOM-20251102
- Registrant country
- RU
- Organization
- Not stated by the registry
- Type
- ASSIGNED PA
- Created
- Feb 28, 2019
- Updated
- Feb 11, 2025
- Maintainer
- mnt-ru-alcom-1
- RIR
- RIPE NCC
- Country
- RU
- Delegated
- Feb 27, 2019
- Status
- assigned
Report abuse
Abuse contact
- ak@
dtc. su - Name
- Abuse-C Role
- Handle
- AR62576-RIPE