41.231.236.0/24
At a glance
Addresses
/24 block
Visibility
55 of 76 vantage points
RPKI
Registry
TNAllocated 12th December 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS328880seen on 3,457 paths from 76 vantage points
- Peer of AS5438seen on 18,931 paths from 138 vantage points
- Peer of AS2609seen on 12,264 paths from 115 vantage points
- Peer of AS3257seen on 182,632 paths from 39 vantage points
- Peer of AS6453seen on 654,008 paths from 6 vantage points
US
FROne 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
- London, UK3288805438260967628529This path
- Amsterdam328880543826096762250918298This path
- Sao Paulo328880543826093257645335280Shown above
- Oregon, US3288805438260967621299855142013This 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
72%
Seen by 55 of 76 full-feed vantage points
Partially propagatedObserved 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
- Tunisia
- Allocated
- 12th December 2006
- Allocation block
- 41.224.0.0/13
- 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.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 41.231.236.0/22 | 1k | AS328880STE INTERNET SMART SOLUTIONS | 76/76 |
| 41.231.0.0/16 | 65.5k | AS2609Tunisia BackBone AS | 76/76 |
| 41.224.0.0/13 | 524k | AS2609Tunisia BackBone AS | 75/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 41.231.237.0/24 | 256 | AS328880STE INTERNET SMART SOLUTIONS | 76/76 |
History
- AS3288809th November 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.231.236.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.