Data as of Nov 16, 2026

37.228.94.0/24

2 residential-proxy exits · 30 days

JSC Mediasoft ekspert

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Providers
3
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

13 observations

Proxy providers listing exits

  • Ake.net
  • 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.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
37.228.88.0/212,048RU-MTW-20120410JSC Mediasoft ekspert (ORG-JME1-RIPE) · RUALLOCATED PAApr 10, 2012abuse@mtw.ru
└ 37.228.94.0/24256MTW-NET-KOROLEVJSC Mediasoft ekspert (ORG-JME1-RIPE) · RUSUB-ALLOCATED PAOct 31, 2013abuse@mtw.ru
└ 37.228.94.0/304MTW-CLIENT-FLYHOSTFlyHost LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.4/304IBGP-GW6-VOSTOKiBGP peering/MTW LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.12/304BGP-PEER-CITYLINKCityLink LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.16/304MTW-CLIENT-MEDIA-TELECOMMedia Telecom Ltd.ASSIGNED PADec 23, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.20/304MTW-CLIENT-VRNVRNASSIGNED PANov 25, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.24/298MTW-CLIENT-STROY-BETONStroyBeton LLC, static routeASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.32/304MTW-PEER-CENTROSET-EBGPBGP customer/CentroSet Ltd.ASSIGNED PAFeb 6, 2014abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.40/298MTW-CLIENT-STROY-BETONStroyBeton LLC, static routeASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.48/304IBGP-GW2-VOSTOKMTW LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.52/304MTW-CLIENT-STROY-BETONStroyBeton LLC, static routeASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.56/304BGP-PEER-VERMONTVermont LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.64/298BGP-PEER-INTEK-MIntek-M LLCASSIGNED PAJul 16, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.72/304MTW-CLIENT-INTEK-MIntek-M LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.76/304MCAST-PEER-INCOMSVmBGP peering/Incom Svyaz LLCASSIGNED PASep 5, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.80/304MCAST-PEER-LITE-TELECOMmBGP peering/CentroSetASSIGNED PASep 5, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.84/304BGP-PEER-YANDEXBGP peering/Yandex enterprise networkASSIGNED PASep 5, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.88/304BGP-PEER-F1F2MTW LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.92/304IBGP-GW2-GW6iBGP peering/MTW LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.96/304PEER-IT-NOVATIONLLC "IT Novation", DEPASSIGNED PAOct 29, 2014abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.100/304BGP-PEER-LIGHT-TELECOMLight Telecom LLCASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.104/304BGP-PEER-CITILINKLLC "City-Link"ASSIGNED PAOct 29, 2014abuse@mtw.ru
via MTW-NET-KOROLEV
└ 37.228.94.128/25128MTW-CLIENT-ELITESELiTES-StudioASSIGNED PAOct 31, 2013abuse@mtw.ru
via MTW-NET-KOROLEV

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
Apr 2012
Current origin since
Apr 2012 · 15 yr
Origin networks
1