SUBNET.IM

45.94.120.0/22

At a glance

Addresses

1,024

/22 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCRU

Allocated 5th July 2019

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 45.94.120.0/22, fanning out from AS49505 toward the vantage points that see it. Each path is written out in full beneath the graph.AS49505JSC SelectelOriginAS9002RETN LimitedAS8529Zain Omantel Inte…AS12389Rostelecom PJSCAS6939Hurricane Electri…AS213151Christian ElsenAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS4766Korea TelecomAS132337AxclusiveAS20130Depaul University
  1. London, UK4950590028529This path
  2. Amsterdam49505123896939213151This path
  3. Sao Paulo4950590023356266213This path
  4. Singapore49505123894766132337This path
  5. Oregon, US4950512389693920130This 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
RIPE NCC — Europe, Middle East, Central Asia
Country
Russia
Allocated
5th July 2019
Allocation block
45.94.120.0/22
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 45.94.120.0/22
ROA prefixAuthorised originMax length
45.94.120.0/22AS49505/22

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 45.94.120.0/22: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.45.94.120.0/22AS49505This prefix45.94.120.0/23AS4950545.94.122.0/23AS49505

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.

More specific announcements

Announcements contained within 45.94.120.0/22
PrefixAddressesOriginVisibility
45.94.120.0/23512AS49505JSC Selectel80/80
45.94.122.0/23512AS49505JSC Selectel80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 45.94.120.0/22
PrefixAddressesOriginVisibility
45.94.124.0/221kAS29075IELO-LIAZO SERVICES SAS79/80

History

  1. AS4950512th 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 45.94.120.0/22 in the calculator/22 reference

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