SUBNET.IM

2001:4320::/32

SOCIETE BENINOISE D'INFRASTRUCTURES NUMERIQUESAS28683

At a glance

Subnets

4,294,967,296 × /64

/32 block

Visibility

97%

60 of 62 vantage points

RPKI

Valid

Registry

AFRINICBJ

Allocated 23rd October 2007

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: 4 observed paths to 2001:4320::/32, fanning out from AS28683 toward the vantage points that see it. Each path is written out in full beneath the graph.AS28683SOCIETE BENINOISE…OriginAS5511Orange S.A.AS6939Hurricane Electri…AS213151Christian ElsenAS174Cogent Communicat…AS15576NTS workspace AGAS51907Kanton ZugAS12956Telxius (Telefoni…AS32590Valve CorporationAS132337Axclusive
  1. Amsterdam2868355116939213151This path
  2. London, UK286831741557651907This path
  3. Sao Paulo286831741295632590This path
  4. Singapore2868355116939132337This 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

97%

Seen by 60 of 62 full-feed vantage points

Globally propagated

Observed at 4 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
Benin
Allocated
23rd October 2007
Allocation block
2001:4320::/32
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 2001:4320::/32
ROA prefixAuthorised originMax length
2001:4320::/32AS28683/54
2001:4320::/32AS28683/32
2001:4320::/32AS28683/48
2001:4320::/32AS28683/128
2001:4320::/32AS28683/112
2001:4320::/32AS28683/56
2001:4320::/32AS28683/64
2001:4320::/32AS28683/40
2001:4320::/32AS328228/64
2001:4320::/32AS328228/128
2001:4320::/32AS328228/58
2001:4320::/32AS328228/40
2001:4320::/32AS328228/56
2001:4320::/32AS328228/36
2001:4320::/32AS328228/112
2001:4320::/32AS328228/48
2001:4320::/32AS328228/100
2001:4320::/32AS328228/32
2001:4320::/32AS328228/54

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 2001:4320::/32: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.2001:4320::/32AS28683This prefix2001:4320:20::/44AS3282282001:4320:50::/44AS3282282001:4320:9::/48AS28683

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

No less specific announcement covers this prefix.

More specific announcements

Announcements contained within 2001:4320::/32
PrefixAddressesOriginVisibility
2001:4320:20::/441M × /64AS328228SOCIETE BENINOISE D'INFRASTRUCTURES NUMERIQUES60/62
2001:4320:50::/441M × /64AS328228SOCIETE BENINOISE D'INFRASTRUCTURES NUMERIQUES60/62
2001:4320:9::/4865.5k × /64AS28683SOCIETE BENINOISE D'INFRASTRUCTURES NUMERIQUES60/62

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS2868312th 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.

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