2a0c:ac0::/29
At a glance
Subnets
/29 block
Visibility
61 of 62 vantage points
RPKI
Registry
RUAllocated 1st April 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS204491seen on 915 paths from 61 vantage points
- Peer of AS51722seen on 5,586 paths from 142 vantage points
- Peer of AS208972seen on 2,798 paths from 141 vantage points
- Peer of AS9121seen on 24,769 paths from 123 vantage points
- Peer of AS3257seen on 12,757 paths from 19 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
US
TR
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
- Amsterdam20449151722208972912132576939213151This path
- London, UK20449151722208972912182201557651907This path
- Sao Paulo20449151722208972912132571295632590This path
- Singapore20449151722208972912132576939132337Shown 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
98%
Seen by 61 of 62 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
- Russia
- Allocated
- 1st April 2019
- Allocation block
- 2a0c:ac0::/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 |
|---|---|---|
| 2a0c:ac0::/29 | AS204491 | /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
- AS20449112th 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.
Routing data derived from RouteViews MRT archives and public registry data.