Data as of Nov 10, 2026

178.67.200.0/23

No anonymizer space · no proxy exits in 30 days

PJSC Rostelecom

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.67.192.0/19
since Apr 2017
AS12389Residential1,770
26 always on
PJSC Rostelecom
178.67.192.0/18
since Sep 2018
AS12389Residential2,756
65 always on
PJSC Rostelecom
178.67.0.0/16
since Sep 2018
AS12389Residential9,537
318 always on
PJSC Rostelecom
178.64.0.0/13
since Oct 2018
AS12389Residential68,006
3,842 always on
PJSC Rostelecom

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.64.0.0/13524,288RU-RTK-20100105PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAJan 5, 2010abuse@rt.ru
└ 178.67.192.0/204,096RU-AVANGARD-DSLPJSC "Rostelecom" North-West RegionSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-RTK-20100105
└ 178.67.201.0/24256Rostelecom_netunknownSUB-ALLOCATED PAAug 26, 2025abuse@rt.ru
via RU-AVANGARD-DSL

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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2019
Current origin since
May 2024 · 2.5 yr
Origin networks
1