subnet.im

45.221.197.0/24

Habari Node Public LimitedAS36909

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

AFRINICTZ

Allocated 9th November 2016

AS paths to this prefix

All paths

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

OriginVantage point · Singapore
One AS path to 45.221.197.0/24 as seen from Singapore, read outward from the origin: AS36909 → AS36908 → AS36994 → AS132337. Each hop is listed with its network name beneath the graph.AS36909Habari Node Publi…OriginAS36908Vodacom Tanzania …AS36994VodacomAS132337Axclusive

Seen from Singapore

  1. 1AS36909Habari Node Public LimitedTZOrigin
    Peer of AS36909seen on 1,895 paths from 80 vantage points
  2. 2AS36908Vodacom Tanzania LtdTZ
    Peer of AS36908seen on 3,750 paths from 80 vantage points
  3. 3AS36994VodacomZA
    Peer of AS36994seen on 717 paths from 2 vantage points
  4. 4AS132337AxclusiveSGVantage 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. Amsterdam369093690837100213151This path
  2. London, UK3690936908371008529This path
  3. Singapore369093690836994132337Shown above
  4. Oregon, US3690937035693920130This path
  5. Sao Paulo3690936908369943356266213This 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
AFRINIC — Africa
Country
Tanzania
Allocated
9th November 2016
Allocation block
45.221.192.0/21
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 45.221.197.0/24
PrefixAddressesOriginVisibility
45.221.196.0/24256AS36909Habari Node Public Limited79/80

History

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

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