subnet.im

163.8.36.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

76 of 76 vantage points

RPKI

Valid

Registry

APNICAU

Allocated 29th June 1992

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 163.8.36.0/24 as seen from Oregon, US, read outward from the origin: AS214143 → AS20473 → AS1221 → AS4637 → AS8551 → AS42013. Each hop is listed with its network name beneath the graph.AS214143SKYDIGITAL TELECO…OriginAS20473The Constant Comp…AS1221Telstra LimitedAS4637Telstra Internati…AS8551Bezeq Internation…AS42013Together Communic…

Seen from Oregon, US

  1. Peer of AS214143seen on 402 paths from 76 vantage points
  2. Peer of AS20473seen on 3,268 paths from 85 vantage points
  3. Peer of AS1221seen on 163,238 paths from 135 vantage points
  4. Peer of AS4637seen on 20,235 paths from 1 vantage point
  5. Peer of AS8551seen on 1,076,496 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. Sao Paulo21414320473291435280This path
  2. Singapore21414320473349123673This path
  3. Amsterdam214143204732914250918298This path
  4. London, UK21414320473349164538529This path
  5. Oregon, US2141432047312214637855142013Shown 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

100%

Seen by 76 of 76 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
APNIC — Asia-Pacific
Country
Australia
Allocated
29th June 1992
Allocation block
163.8.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 163.8.36.0/24
ROA prefixAuthorised originMax length
163.8.36.0/24AS214143/24
163.8.36.0/24AS834/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 163.8.36.0/24
PrefixAddressesOriginVisibility
163.8.37.0/24256AS9507NextHop Pty Ltd55/76

History

  1. AS21414326th October 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 163.8.36.0/24 in the calculator/24 reference

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