91.208.32.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
TRAllocated 17th April 2023
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS21245seen on 80 paths from 80 vantage points
- Peer of AS212330seen on 28,759 paths from 142 vantage points
- Peer of AS208293seen on 15,230 paths from 142 vantage points
- 4AS211513Al Lawn Al Akhdar International Company for Communications and Information Technology Ltd.
IQPeer of AS211513seen on 13,910 paths from 142 vantage points - Peer of AS210021seen on 9 paths from 1 vantage point
- Peer of AS137409seen on 91,764 paths from 6 vantage points
AU
AEOne 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
- Amsterdam2124521233020829321151321002112735213151This path
- London, UK212452123302082932115132100211374098529Shown above
- Singapore2124521233020829321151321002112735132337This path
- Oregon, US21245212330208293211513210021693920130This path
- Sao Paulo212452123302082932115132100211273590023356→ ⋯This 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
100%
Seen by 80 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
- Türkiye
- Allocated
- 17th April 2023
- Allocation block
- 91.208.32.0/24
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 91.208.32.0/24 | AS21245 | /24 |
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.208.33.0/24 | 256 | AS41975OOO RIVC "Simplex" | 80/80 |
History
- AS2124512th 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.208.32.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.