SUBNET.IM

41.90.2.0/24

At a glance

Addresses

256

/24 block

Visibility

100%

80 of 80 vantage points

RPKI

Valid

Registry

AFRINICKE

Allocated 16th November 2009

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

OriginVantage points
AS path graph: 5 observed paths to 41.90.2.0/24, fanning out from AS33771 toward the vantage points that see it. Each path is written out in full beneath the graph.AS33771Safaricom LimitedOriginAS37100SEACOM LimitedAS8529Zain Omantel Inte…AS8966Etisalat (E&)AS132337AxclusiveAS37662West Indian Ocean…AS6939Hurricane Electri…AS213151Christian ElsenAS266213PLANETCLICK TELEC…AS20130Depaul University
  1. London, UK33771371008529This path
  2. Singapore337718966132337This path
  3. Amsterdam33771376626939213151This path
  4. Sao Paulo33771376626939266213This path
  5. Oregon, US3377137662693920130This 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
AFRINIC — Africa
Country
Kenya
Allocated
16th November 2009
Allocation block
41.90.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 41.90.2.0/24
ROA prefixAuthorised originMax length
41.90.0.0/16AS198949/24
41.90.0.0/16AS19905/24
41.90.0.0/16AS33771/24
41.90.0.0/16AS37061/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 41.90.2.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.41.90.0.0/17AS3377141.90.0.0/16AS3377141.90.2.0/24AS33771This prefix41.90.3.0/24AS33771

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 41.90.2.0/24
PrefixAddressesOriginVisibility
41.90.0.0/1732.8kAS33771Safaricom Limited80/80
41.90.0.0/1665.5kAS33771Safaricom Limited80/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 41.90.2.0/24
PrefixAddressesOriginVisibility
41.90.3.0/24256AS33771Safaricom Limited80/80

History

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

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