91.231.241.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
PLAllocated 7th October 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS213907seen on 80 paths from 80 vantage points
- Peer of AS5617seen on 7,603 paths from 140 vantage points
- Peer of AS5511seen on 126,941 paths from 48 vantage points
- Peer of AS2914seen on 60,369 paths from 3 vantage points
- Peer of AS8966seen on 133,632 paths from 2 vantage points
FR
US
AE
SGOne 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
- Amsterdam2139075617551134549213151This path
- London, UK2139075617551112998529This path
- Sao Paulo213907561755113356266213This path
- Oregon, US21390756175511693920130This path
- Singapore2139075617551129148966132337Shown above
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
- Poland
- Allocated
- 7th October 2011
- Allocation block
- 91.231.241.0/24
- Status
- assigned
- 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.
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.231.240.0/24 | 256 | AS198124FOP Zashkolny Aleksandr Ivanovich | 80/80 |
History
- AS21390712th 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.231.241.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.