subnet.im

81.7.80.0/21

At a glance

Addresses

2,048

/21 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCLT

Allocated 1st August 2002

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Oregon, US.

OriginVantage point · Oregon, US
One AS path to 81.7.80.0/21 as seen from Oregon, US, read outward from the origin: AS8764 → AS6939 → AS20130. Each hop is listed with its network name beneath the graph.AS8764Telia Lietuva, ABOriginAS6939Hurricane Electri…AS20130Depaul University

Seen from Oregon, US

  1. Peer of AS8764seen on 3,732 paths from 10 vantage points
  2. Peer of AS6939seen on 975,334 paths from 1 vantage point
  3. 3AS20130Depaul UniversityUSVantage point

One path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.

Every path we see

  1. Amsterdam8764213151This path
  2. Singapore8764132337This path
  3. London, UK876412998529This path
  4. Oregon, US8764693920130Shown above
  5. Sao Paulo876412993356266213This 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
Lithuania
Allocated
1st August 2002
Allocation block
81.7.64.0/18
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 81.7.80.0/21
ROA prefixAuthorised originMax length
81.7.64.0/18AS8764/24

Prefix hierarchy

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

Covering announcements

No less specific announcement covers this prefix.

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 81.7.80.0/21
PrefixAddressesOriginVisibility
81.7.88.0/212kAS8764Telia Lietuva, AB79/80

History

  1. AS876412th 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 81.7.80.0/21 in the calculator/21 reference

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