SUBNET.IM

41.187.0.0/17

The Noor GroupAS20928

At a glance

Addresses

32,768

/17 block

Visibility

99%

79 of 80 vantage points

RPKI

No ROA

Registry

AFRINICEG

Allocated 21st November 2008

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.187.0.0/17, fanning out from AS20928 toward the vantage points that see it. Each path is written out in full beneath the graph.AS20928The Noor GroupOriginAS3257GTT Communication…AS34549meerfarbig GmbH &…AS213151Christian ElsenAS1299Arelion (fka. Tel…AS8529Zain Omantel Inte…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…AS132337AxclusiveAS23352DEFT.COMAS20130Depaul University
  1. Amsterdam20928325734549213151This path
  2. London, UK20928325712998529This path
  3. Sao Paulo2092832573356266213This path
  4. Singapore2092832571299132337This path
  5. Oregon, US2092832572335220130This 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
Egypt
Allocated
21st November 2008
Allocation block
41.187.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.

CoveringMore specific
Prefix hierarchy for 41.187.0.0/17: 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.187.0.0/16AS2092841.187.0.0/17AS20928This prefix41.187.128.0/17AS2092841.187.91.0/24AS2092841.187.97.0/24AS2092841.187.98.0/24AS2092841.187.120.0/24AS20928

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.187.0.0/17
PrefixAddressesOriginVisibility
41.187.0.0/1665.5kAS20928The Noor Group79/80

More specific announcements

Announcements contained within 41.187.0.0/17
PrefixAddressesOriginVisibility
41.187.91.0/24256AS20928The Noor Group79/80
41.187.97.0/24256AS20928The Noor Group79/80
41.187.98.0/24256AS20928The Noor Group79/80
41.187.120.0/24256AS20928The Noor Group79/80

Sibling prefixes

Prefixes of the same length sharing a parent block with 41.187.0.0/17
PrefixAddressesOriginVisibility
41.187.128.0/1732.8kAS20928The Noor Group79/80

History

  1. AS2092812th 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.187.0.0/17 in the calculator/17 reference

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