subnet.im

41.222.244.0/23

At a glance

Addresses

512

/23 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

AFRINICRW

Allocated 13th March 2008

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 41.222.244.0/23 as seen from Oregon, US, read outward from the origin: AS37010 → AS37654 → AS36944 → AS3257 → AS23352 → AS20130. Each hop is listed with its network name beneath the graph.AS37010National Universi…OriginAS37654Rwanda Ministry o…AS36944Ubuntunet Allianc…AS3257GTT Communication…AS23352DEFT.COMAS20130Depaul University

Seen from Oregon, US

  1. Peer of AS37010seen on 79 paths from 79 vantage points
  2. Peer of AS37654seen on 691 paths from 80 vantage points
  3. Peer of AS36944seen on 8,081 paths from 140 vantage points
  4. Peer of AS3257seen on 59,210 paths from 1 vantage point
  5. Peer of AS23352seen on 103,654 paths from 1 vantage point
  6. 6AS20130Depaul UniversityUSVantage 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. London, UK37010376543694467628529This path
  2. Singapore3701037654376193376537100132337This path
  3. Oregon, US37010376543694432572335220130Shown above
  4. Amsterdam3701037654372283761914593166376939213151This path
  5. Sao Paulo3701037654372283761914593166376939266213This 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
Rwanda
Allocated
13th March 2008
Allocation block
41.222.244.0/22
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 41.222.244.0/23
PrefixAddressesOriginVisibility
41.222.246.0/23512AS37010National University of Rwanda79/80

History

  1. AS3701012th 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.222.244.0/23 in the calculator/23 reference

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