91.102.232.0/24
At a glance
Addresses
/24 block
Visibility
79 of 80 vantage points
RPKI
Registry
Allocated 9th November 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS196659seen on 107 paths from 80 vantage points
- Peer of AS42781seen on 6,308 paths from 80 vantage points
- Peer of AS6412seen on 14,364 paths from 80 vantage points
- Peer of AS42961seen on 35,166 paths from 142 vantage points
- Peer of AS8529seen on 1,200 paths from 2 vantage points
One 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, UK196659427816412429618529This path
- Amsterdam196659427816412429618529213151Shown above
- Sao Paulo196659915547589393863356266213This path
- Singapore196659427816412429618529132337This path
- Oregon, US19665991554758939386693920130This 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 propagatedObserved 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
Kuwait
- Allocated
- 9th November 2006
- Allocation block
- 91.102.232.0/21
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 91.102.233.0/24 | 256 | AS19905Arbor Cloud | 79/80 |
History
- AS19665912th 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 91.102.232.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.