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

178.57.72.0/21

1 residential-proxy exit · 30 days

Data Storage Center JSC

Announcement
this exact prefix
RPKI valid
Announced by
AS49063
Type
Hosting

Residential-proxy exits

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

Exits seen per day

3 observations

Proxy providers listing exits

  • Shifter

Announcements

Nesting

More-specifics by size

Sized by addresses, colored by each announcement's type. Click a tile with children to zoom in, a leaf to open it.
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
178.57.72.0/24
since Oct 2016
AS49063HostingData Storage Center JSC
178.57.73.0/24
since Nov 2016
AS49063HostingData Storage Center JSC
178.57.74.0/24
since Jan 2017
AS49063HostingData Storage Center JSC
178.57.75.0/24
since Dec 2016
AS49063HostingData Storage Center JSC
178.57.76.0/24
since Dec 2016
AS49063HostingData Storage Center JSC
178.57.77.0/24
since Jan 2017
AS49063HostingData Storage Center JSC
178.57.78.0/24
since Nov 2016
AS49063Hosting1Data Storage Center JSC
178.57.79.0/24
since Nov 2016
AS49063HostingData Storage Center JSC

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
178.57.72.0/212,048RU-DATALINE-2010202Data Storage Center JSC (ORG-DL76-RIPE) · RUALLOCATED PAOct 24, 2016abuse@dtln.ru
└ 178.57.72.0/24256DTLN-CustomersunknownLIR-PARTITIONED PAOct 18, 2021abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.72.32/2732DTLN-CUSTOMERS-CARDIFunknownASSIGNED PAAug 21, 2018abuse@dtln.ru
via DTLN-Customers
└ 178.57.72.64/2664DTLN-CUSTOMERS-ITCom-DirMindbox (ORG-MA1887-RIPE)ASSIGNED PAOct 18, 2021abuse@mindbox.ru
└ 178.57.73.80/2816Dtln-CustomerunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.73.128/2732DTLN-Customer-BAKunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.74.0/24256DTLN-CLOUDunknownASSIGNED PAJan 12, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.75.64/2732DTLN-Customer-BAKunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.75.160/2816DTLN-Customer-RNPKunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.75.176/2816DTLN-Customer-RNPKunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.75.208/2816DTLN-CustomerunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.75.224/2732DTLN-Customer-BTI_CloudunknownASSIGNED PAJan 17, 2018abuse@dtln.ru
via RU-DATALINE-2010202
└ 178.57.76.0/24256DTLN-Customer-SimaOptunknownASSIGNED PAJan 12, 2018abuse@dtln.ru
via RU-DATALINE-2010202

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2013
Current origin since
Oct 2016 · 10 yr
Origin networks
2
Last change of origin
Oct 2016
Recorded history

History

Handoffs
1