SUBNET.IM

95.213.44.0/24

LLC VKAS47541

LLC VKAS47542

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

96%

77 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCRU

Allocated 12th August 2009

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 95.213.44.0/24, fanning out from AS47541 toward the vantage points that see it. Each path is written out in full beneath the graph.AS47541LLC VKOriginAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6762Telecom Italia Sp…AS174Cogent Communicat…AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK4754112998529This path
  2. Singapore475416939132337This path
  3. Oregon, US47541693920130This path
  4. Sao Paulo4754112993356266213This path
  5. Amsterdam47541676217434549213151This 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

96%

Seen by 77 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Russia
Allocated
12th August 2009
Allocation block
95.213.0.0/17
Status
allocated
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 95.213.44.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.95.213.0.0/18AS4754195.213.0.0/17AS4754195.213.45.0/24AS4754195.213.44.0/24AS47541This prefix95.213.45.0/24AS47542

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

Announcements that contain 95.213.44.0/24
PrefixAddressesOriginVisibility
95.213.0.0/1816.4kAS47541LLC VK80/80
95.213.0.0/1732.8kAS47541LLC VK80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 95.213.44.0/24
PrefixAddressesOriginVisibility
95.213.45.0/24256AS47541LLC VK77/80
95.213.45.0/24256AS47542LLC VK3/80

History

  1. AS4754212th August 2026 — present
  2. AS4754112th 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 95.213.44.0/24 in the calculator/24 reference

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