SUBNET.IM

217.168.160.0/21

At a glance

Addresses

2,048

/21 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

RIPE NCCMT

Allocated 21st March 2001

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 217.168.160.0/21, fanning out from AS20521 toward the vantage points that see it. Each path is written out in full beneath the graph.AS20521Bellnet LimitedOriginAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS6939Hurricane Electri…AS132337AxclusiveAS20130Depaul UniversityAS2914NTT America, Inc.AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK2052133568529This path
  2. Sao Paulo205213356266213This path
  3. Singapore2052133566939132337This path
  4. Oregon, US205213356693920130This path
  5. Amsterdam205213356291434549213151This 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
Malta
Allocated
21st March 2001
Allocation block
217.168.160.0/20
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 217.168.160.0/21
ROA prefixAuthorised originMax length
217.168.160.0/20AS202/32
217.168.160.0/20AS203/32
217.168.160.0/20AS20521/32
217.168.160.0/20AS3356/32

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 217.168.160.0/21: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.217.168.160.0/20AS20521217.168.160.0/21AS20521This prefix217.168.168.0/21AS20521

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 217.168.160.0/21
PrefixAddressesOriginVisibility
217.168.160.0/204.1kAS20521Bellnet Limited80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 217.168.160.0/21
PrefixAddressesOriginVisibility
217.168.168.0/212kAS20521Bellnet Limited80/80

History

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

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