Data as of Nov 19, 2026

81.95.130.0/24

1 residential-proxy exit · 30 days

JSC 'ER-Telecom Holding'

Announcement
this exact prefix
No RPKI
Announced by
Type
Business

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Providers
3
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

12 observations

Proxy providers listing exits

  • RainProxy
  • Shifter
  • ZENPROXY_PREMIUM

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
81.95.130.0 - 81.95.140.2552,816RU-RAID-20020905JSC "ER-Telecom Holding" (ORG-RA21-RIPE) · RUALLOCATED PAOct 2, 2026abuse@domru.ru
└ 81.95.130.0/25128MATRIXTELECOM-NETMatrix telecom, MoscowASSIGNED PAApr 4, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.128/2816MOSTCOMLeased Line ClientsASSIGNED PAApr 4, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.144/2816MOSTCOMLeased Line ClientsASSIGNED PAApr 4, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.160/2816MOSTCOMLeased Line ClientsASSIGNED PAApr 4, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.176/304TPRCredit Pilot mail serverASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.180/304KrialMoscow, Ogorodnij pr-d 15ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.184/304SportingMoscow, F.Engelsa 58ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.188/304ArsenalMoscow, F.Engelsa 58ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.192/304TTS-PartnersMoscow, Leontevskij per 15ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.196/304CFTMoscow, Leningradskaya st. 38ASSIGNED PAApr 9, 2013abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.200/304DonayMoscow, MKAD 84 kmASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.204/304LavantMoscow, F.Engelsa 58ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.208/298TWO-GISMoscow, Marksistskaya 3ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.216/298ItercorpMoscow, Litovskij b-r 31ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.224/298RidgenalMO, Riga LandASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.232/298V-MediaMoscow, BC Paveletskij, Kozevnicheskaya 6ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.240/304MSYMoscow, B.Pochtovaya 55ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.244/304Bank_Rysskij_StandartMoscow, Zemlianoj Val 27ASSIGNED PAApr 28, 2012abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.248/304ENEKSMoscow, B.Dmitrovka 32-1ASSIGNED PAApr 9, 2013abuse@domru.ru
via RU-RAID-20020905
└ 81.95.130.252/304InveststrojMoscow, Rysakovskaya 13ASSIGNED PAApr 9, 2013abuse@domru.ru
via RU-RAID-20020905

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 2008
Current origin since
Nov 2017 · 9.0 yr
Origin networks
1