SUBNET.IM

45.144.72.0/22

Logifuture Austria GmbHAS201239

At a glance

Addresses

1,024

/22 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

RIPE NCCAT

Allocated 22nd August 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.144.72.0/22, fanning out from AS201239 toward the vantage points that see it. Each path is written out in full beneath the graph.AS201239Logifuture Austri…OriginAS15830Equinix, Inc.AS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS20130Depaul University
  1. Amsterdam20123915830213151This path
  2. London, UK201239158308529This path
  3. Singapore20123915830132337This path
  4. Sao Paulo201239158303356266213This path
  5. Oregon, US20123915830693920130This 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

99%

Seen by 79 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
Austria
Allocated
22nd August 2019
Allocation block
45.144.72.0/22
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 45.144.72.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.144.72.0/22AS201239This prefix45.144.72.0/24AS20123945.144.73.0/24AS20123945.144.74.0/24AS20123945.144.75.0/24AS201239

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.144.72.0/22
PrefixAddressesOriginVisibility
45.144.72.0/24256AS201239Logifuture Austria GmbH80/80
45.144.73.0/24256AS201239Logifuture Austria GmbH80/80
45.144.74.0/24256AS201239Logifuture Austria GmbH80/80
45.144.75.0/24256AS201239Logifuture Austria GmbH80/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 45.144.72.0/22
PrefixAddressesOriginVisibility
45.144.76.0/221kAS210150Voss Fiber AS80/80

History

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

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