SUBNET.IM

195.161.0.0/16

JSC RTComm.RUAS8342

At a glance

Addresses

65,536

/16 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

Unknown

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 195.161.0.0/16, fanning out from AS8342 toward the vantage points that see it. Each path is written out in full beneath the graph.AS8342JSC RTComm.RUOriginAS12389Rostelecom PJSCAS8529Zain Omantel Inte…AS6939Hurricane Electri…AS213151Christian ElsenAS4766Korea TelecomAS132337AxclusiveAS20130Depaul UniversityAS3491PCCW Global (HK) …AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. London, UK8342123898529This path
  2. Amsterdam8342123896939213151This path
  3. Singapore8342123894766132337This path
  4. Oregon, US834212389693920130This path
  5. Sao Paulo83421238934913356266213This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

100%

Seen by 80 of 80 full-feed vantage points

Globally propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
Unknown
Country
Unknown
Allocated
Unknown
Allocation block
Unknown
Status
Unknown
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 195.161.0.0/16: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.195.161.0.0/16AS8342This prefix195.161.96.0/20AS8342195.161.56.0/22AS8342195.161.88.0/22AS8342195.161.120.0/22AS8342195.161.140.0/22AS8342+3 more

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

No less specific announcement covers this prefix.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS834212th August 2026 — present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 195.161.0.0/16 in the calculator/16 reference

Routing data derived from RouteViews MRT archives and public registry data.