subnet.im

167.150.100.0/24

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

APNICCA

Allocated 2nd August 1993

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to Sao Paulo.

OriginVantage point · Sao Paulo
One AS path to 167.150.100.0/24 as seen from Sao Paulo, read outward from the origin: AS136258 → AS396356 → AS6453 → AS3356 → AS266213. Each hop is listed with its network name beneath the graph.AS136258BrainStorm Networ…OriginAS396356Latitude.shAS6453TATA Communicatio…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…

Seen from Sao Paulo

  1. Peer of AS136258seen on 2,672 paths from 142 vantage points
  2. Peer of AS396356seen on 696 paths from 65 vantage points
  3. Peer of AS6453seen on 254,737 paths from 71 vantage points
  4. Peer of AS3356seen on 997,311 paths from 2 vantage points

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. London, UK13625839635664538529This path
  2. Oregon, US136258396356693920130This path
  3. Sao Paulo13625839635664533356266213Shown above
  4. Singapore13625839635674731299132337This path
  5. Amsterdam1362583963567473646134549213151This 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
APNIC — Asia-Pacific
Country
Canada
Allocated
2nd August 1993
Allocation block
167.150.100.0/23
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 167.150.100.0/24
ROA prefixAuthorised originMax length
167.150.100.0/24AS136258/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 167.150.100.0/24
PrefixAddressesOriginVisibility
167.150.101.0/24256AS136258BrainStorm Network, Inc80/80

History

  1. AS13625812th 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 167.150.100.0/24 in the calculator/24 reference

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