2a0e:b082::/32
At a glance
Subnets
/32 block
Visibility
64 of 64 vantage points
RPKI
Registry
IRAllocated 3rd June 2019
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 AS60631seen on 2,702 paths from 145 vantage points
- Peer of AS204203seen on 1,292 paths from 145 vantage points
- Peer of AS42337seen on 154,164 paths from 145 vantage points
- Peer of AS12880seen on 193,018 paths from 145 vantage points
- Peer of AS49666seen on 35,149 paths from 145 vantage points
- Peer of AS5511seen on 295,827 paths from 65 vantage points
- Peer of AS1299seen on 514,221 paths from 6 vantage points
FR
SEOne 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
- Amsterdam60631204203423371288049666676232590This path
- London, UK606312042034233712880496665511129935280Shown above
- Sao Paulo606312042034233712880496665511645335280This path
- Singapore6063120420342337128804966667626939132337This 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 64 of 64 full-feed vantage points
Globally 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Iran
- Allocated
- 3rd June 2019
- Allocation block
- 2a0e:b080::/29
- 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 |
|---|---|---|---|
| 2a0e:b083::/32 | 4.3B × /64 | AS60631Vandad Vira Hooman LLC | 64/64 |
History
- AS6063122nd September 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.