subnet.im

167.129.0.0/16

City of SaskatoonAS394366

At a glance

Addresses

65,536

/16 block

Visibility

100%

80 of 80 vantage points

RPKI

No ROA

Registry

ARINCA

Allocated 30th June 1993

AS paths to this prefix

All paths

One observed path, hop by hop, from the origin out to London, UK.

OriginVantage point · London, UK
One AS path to 167.129.0.0/16 as seen from London, UK, read outward from the origin: AS394366 → AS6327 → AS3356 → AS8529. Each hop is listed with its network name beneath the graph.AS394366City of SaskatoonOriginAS6327Shaw Communicatio…AS3356Lumen (Level 3)AS8529Zain Omantel Inte…

Seen from London, UK

  1. 1AS394366City of SaskatoonCAOrigin
    Peer of AS394366seen on 26 paths from 26 vantage points
  2. 2AS6327Shaw CommunicationsCA
    Peer of AS6327seen on 75,600 paths from 72 vantage points
  3. 3AS3356Lumen (Level 3)US
    Peer of AS3356seen on 148,979 paths from 2 vantage points
  4. 4AS8529Zain Omantel International FZ-LLCAEVantage 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. Amsterdam394366195236939213151This path
  2. London, UK394366632733568529Shown above
  3. Sao Paulo394366195236939266213This path
  4. Singapore394366195236939132337This path
  5. Oregon, US39436619523693920130This 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

100%

Seen by 80 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
ARIN — North America
Country
Canada
Allocated
30th June 1993
Allocation block
167.129.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

Prefixes of the same length sharing a parent block with 167.129.0.0/16
PrefixAddressesOriginVisibility
167.128.0.0/1665.5kAS16424Linn Benton Lincoln Education Service District80/80

History

  1. AS39436612th 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.129.0.0/16 in the calculator/16 reference

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