SUBNET.IM

216.150.56.0/22

Merkle Inc.AS10440

At a glance

Addresses

1,024

/22 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 11th December 2003

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 216.150.56.0/22, fanning out from AS10440 toward the vantage points that see it. Each path is written out in full beneath the graph.AS10440Merkle Inc.OriginAS3356Lumen (Level 3)AS8529Zain Omantel Inte…AS266213PLANETCLICK TELEC…AS1299Arelion (fka. Tel…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS2914NTT America, Inc.AS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. London, UK1044033568529This path
  2. Sao Paulo104403356266213This path
  3. Singapore1044033561299132337This path
  4. Oregon, US104403356693920130This path
  5. Amsterdam104403356291434549213151This 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
ARIN — North America
Country
United States
Allocated
11th December 2003
Allocation block
216.150.48.0/20
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 216.150.56.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.216.150.56.0/22AS10440This prefix216.150.58.0/23AS10440

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 216.150.56.0/22
PrefixAddressesOriginVisibility
216.150.58.0/23512AS10440Merkle Inc.79/80

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

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

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