2a0e:a780::/29
Not announced at this prefix length
No announcement covering 2a0e:a780::/29 was visible from any of our collectors at the last snapshot. That can mean the space is unrouted, or that it is announced only within a network we have no vantage point inside.
At a glance
Subnets
/29 block
Visibility
RPKI
Registry
LTAllocated 9th April 2024
AS paths to this prefix
No AS paths are stored for this prefix. We keep the full path from one reference peer per collector rather than from every peer, so a prefix only has paths here once it has been seen by one of those peers.
Registry and RPKI
- RIR
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Lithuania
- Allocated
- 9th April 2024
- Allocation block
- 2a0e:a780::/29
- Status
- allocated
- Origin validation
- Unknown
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2a0e:a780::/29 | AS18978 | /29 |
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
No prefix of the same length in the same parent block is announced.
History
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.