2a10:ed40:a::/48
At a glance
Subnets
/48 block
Visibility
40 of 63 vantage points
RPKI
Registry
IRAllocated 7th February 2024
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Adjacentseen on 190 paths from 95 vantage points
- Peer of AS49581seen on 40,519 paths from 126 vantage points
- Peer of AS44592seen on 7,793 paths from 89 vantage points
- Peer of AS6424seen on 31,634 paths from 115 vantage points
- Peer of AS174seen on 635,742 paths from 48 vantage points
- Peer of AS6453seen on 653,191 paths from 6 vantage points
DE
NL
PT
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
- Amsterdam204104495818298This path
- London, UK2041044958144592642435280This path
- Sao Paulo20410449581445926424174645335280Shown 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
63%
Seen by 40 of 63 full-feed vantage points
Partially propagatedObserved at 3 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
- 7th February 2024
- Allocation block
- 2a10:ed40::/29
- 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 |
|---|---|---|
| 2a10:ed40:a::/48 | AS204104 | /48 |
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 |
|---|---|---|---|
| 2a10:ed40:b::/48 | 65.5k × /64 | AS204104Giti Secure Cloud LLC | 40/63 |
History
- AS20410410th 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.
Routing data derived from RouteViews MRT archives and public registry data.