LAYER3 INTEL
Get started
Sign in
Data as of Nov 13, 2026

77.41.188.0/23

1 residential-proxy exit · 30 days

DataFort LLC · space held by PJSC "Vimpelcom"

Announcement
this exact prefix
No RPKI
Announced by
AS20919
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
0.20% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
1
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1 observation

Proxy providers listing exits

  • Shifter

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.41.160.0/19
since Apr 2014
AS3216Residential73
14 always on
PJSC "Vimpelcom"
via PJSC "Vimpelcom"

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
77.41.128.0/1732,768RU-SOVINTEL-20061201PJSC "Vimpelcom" (ORG-ES15-RIPE) · RUALLOCATED PADec 1, 2006abuse-b2b@beeline.ru
└ 77.41.160.0/198,192RU-VimpelCom-former-IzSvyazInvest-IPv4-POOLPJSC "Vimpelcom" (ORG-ES15-RIPE) · RULIR-PARTITIONED PAApr 11, 2014abuse-b2b@beeline.ru
└ 77.41.188.0/23512RU-Vimpelcom-MSK-BeeCLOUD-Pool-NET111250 Russia Vimpelcom et SOVINTEL/EDNASSIGNED PAJul 18, 2019abuse-b2b@beeline.ru
via RU-VimpelCom-former-IzSvyazInvest-IPv4-POOL

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Reactivated
First seen
Jul 2019
Current origin since
Jun 2025 · 1.4 yr
Origin networks
2
Last change of origin
Jun 2025
Recorded history

History

Handoffs
1