subnet.im

216.225.27.0/24

MyPoints.com, Inc.AS46301

FMC Central Engineering LaboratoriesAS100

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

56%

45 of 80 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 11th May 1999

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.225.27.0/24, fanning out from AS100, AS46301 toward the vantage points that see it. Each path is written out in full beneath the graph.AS46301MyPoints.com, Inc.OriginAS174Cogent Communicat…AS132337AxclusiveAS6453TATA Communicatio…AS8529Zain Omantel Inte…AS100FMC Central Engin…OriginAS46301MyPoints.com, Inc.AS46887Zayo BandwidthAS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS3257GTT Communication…AS23352DEFT.COMAS20130Depaul UniversityAS6461Zayo BandwidthAS34549meerfarbig GmbH &…AS213151Christian Elsen
  1. Singapore46301174132337This path
  2. London, UK4630117464538529This path
  3. Sao Paulo10046301468873356266213This path
  4. Oregon, US4630117432572335220130This path
  5. Amsterdam1004630146887646134549213151This 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

56%

Seen by 45 of 80 full-feed vantage points

Partially 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 May 1999
Allocation block
216.225.24.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.

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 216.225.27.0/24
PrefixAddressesOriginVisibility
216.225.26.0/24256AS53541Prodege LLC79/80

History

  1. AS4630112th August 2026 — present
  2. AS10012th 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.225.27.0/24 in the calculator/24 reference

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