subnet.im

153.72.209.0/24

Palo Alto Networks, IncAS2763

Oracle CloudAS31898

Announced by more than one origin AS (MOAS).

At a glance

Addresses

256

/24 block

Visibility

72%

55 of 76 vantage points

RPKI

Valid

Registry

ARINUS

Allocated 4th December 2025

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 153.72.209.0/24 as seen from Oregon, US, read outward from the origin: AS2763 → AS31898 → AS1299 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS2763Palo Alto Network…OriginAS31898Oracle CloudAS1299Arelion (fka. Tel…AS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS2763seen on 1,043 paths from 76 vantage points
  2. Peer of AS31898seen on 62,945 paths from 133 vantage points
  3. Peer of AS1299seen on 321,664 paths from 1 vantage point
  4. Peer of AS8551seen on 1,077,002 paths from 1 vantage 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. Singapore31898291423673This path
  2. London, UK27633189812998529This path
  3. Sao Paulo276331898291435280This path
  4. Amsterdam2763318981299250918298This path
  5. Oregon, US2763318981299855142013Shown above

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 55 of 76 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
4th December 2025
Allocation block
153.72.0.0/16
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 153.72.209.0/24
ROA prefixAuthorised originMax length
153.72.192.0/19AS2763/24
153.72.192.0/19AS31898/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 153.72.209.0/24
PrefixAddressesOriginVisibility
153.72.208.0/24256AS31898Oracle Cloud76/76

History

  1. AS27639th November 2026 — present
  2. AS3189812th 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 153.72.209.0/24 in the calculator/24 reference

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