SUBNET.IM

41.78.53.0/24

IPSYSTEM S.AAS37163

At a glance

Addresses

256

/24 block

Visibility

99%

79 of 80 vantage points

RPKI

Valid

Registry

AFRINICBF

Allocated 16th September 2011

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.78.53.0/24, fanning out from AS37163 toward the vantage points that see it. Each path is written out in full beneath the graph.AS37163IPSYSTEM S.AOriginAS56987ABACLOUDA SASAS213151Christian ElsenAS8529Zain Omantel Inte…AS132337AxclusiveAS6939Hurricane Electri…AS20130Depaul UniversityAS1299Arelion (fka. Tel…AS3356Lumen (Level 3)AS266213PLANETCLICK TELEC…
  1. Amsterdam3716356987213151This path
  2. London, UK37163569878529This path
  3. Singapore3716356987132337This path
  4. Oregon, US3716356987693920130This path
  5. Sao Paulo371635698712993356266213This 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
Burkina Faso
Allocated
16th September 2011
Allocation block
41.78.52.0/22
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.78.53.0/24
ROA prefixAuthorised originMax length
41.78.52.0/22AS37163/24

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 41.78.53.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.78.52.0/22AS3716341.78.53.0/24AS37163This prefix41.78.52.0/24AS37163

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.78.53.0/24
PrefixAddressesOriginVisibility
41.78.52.0/221kAS37163IPSYSTEM S.A79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 41.78.53.0/24
PrefixAddressesOriginVisibility
41.78.52.0/24256AS37163IPSYSTEM S.A79/80

History

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

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