subnet.im

41.75.214.0/23

AS37440 is not currently observed originating this prefix. The origins we do see are listed above.

At a glance

Addresses

512

/23 block

Visibility

99%

76 of 77 vantage points

RPKI

No ROA

Registry

AFRINICTZ

Allocated 31st August 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.

  1. Amsterdam37133327708376628298This path
  2. London, UK37133327708376628529This path
  3. Sao Paulo371333744032770837100645335280This path
  4. Singapore3713332770837662174349123673This path
  5. Oregon, US37133327708376625511693920130This 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 76 of 77 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
31st August 2009
Allocation block
41.75.208.0/20
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.75.214.0/23: 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.75.208.0/20AS3713341.75.214.0/23AS37133This prefix41.75.212.0/23AS3713341.75.214.0/24AS37133

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.75.214.0/23
PrefixAddressesOriginVisibility
41.75.208.0/204.1kAS37133Airtel Tanzania77/77

More specific announcements

Announcements contained within 41.75.214.0/23
PrefixAddressesOriginVisibility
41.75.214.0/24256AS37133Airtel Tanzania76/77

Sibling prefixes

Prefixes of the same length sharing a parent block with 41.75.214.0/23
PrefixAddressesOriginVisibility
41.75.212.0/23512AS37133Airtel Tanzania76/77

History

  1. AS3713312th October 2026 — present
  2. AS3744024th September 2026 — 12th October 2026
  3. AS32770830th September 2026 — 12th October 2026
  4. AS3713312th August 2026 — 6th October 2026
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.75.214.0/23 in the calculator/23 reference

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