subnet.im

130.137.133.0/24

Amazon.com, Inc.AS16509

At a glance

Addresses

256

/24 block

Visibility

72%

56 of 78 vantage points

RPKI

No ROA

Registry

ARINUS

Allocated 14th February 2018

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: 4 observed paths to 130.137.133.0/24, fanning out from AS16509 toward the vantage points that see it. Each path is written out in full beneath the graph.AS16509Amazon.com, Inc.OriginAS8529Zain Omantel Inte…AS206375NETSPEED INTERNET…AS7768Nuh Ahmet Firat t…AS6453TATA Communicatio…AS35280F5 Networks SARLAS8551Bezeq Internation…AS42013Together Communic…
  1. London, UK165098529This path
  2. Amsterdam165092063757768This path
  3. Sao Paulo16509645335280This path
  4. Oregon, US16509855142013This 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

72%

Seen by 56 of 78 full-feed vantage points

Partially propagated

Observed at 4 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
14th February 2018
Allocation block
130.137.0.0/16
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

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

History

  1. AS1650913th November 2026 — present
  2. AS1650912th November 2026 — 12th November 2026
  3. AS1650910th November 2026 — 10th November 2026
  4. AS165099th November 2026 — 9th November 2026
  5. AS165097th November 2026 — 8th November 2026
  6. AS165095th November 2026 — 5th November 2026
  7. AS165092nd November 2026 — 2nd November 2026
  8. AS165091st November 2026 — 1st November 2026
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 130.137.133.0/24 in the calculator/24 reference

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