2a13:c8c4:fc0c::/46
At a glance
Subnets
/46 block
Visibility
41 of 63 vantage points
RPKI
Registry
ALAllocated 10th April 2026
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 AS218995seen on 50 paths from 41 vantage points
- Peer of AS219451seen on 58 paths from 47 vantage points
- Peer of AS198590seen on 901 paths from 139 vantage points
- Peer of AS207252seen on 2,656 paths from 112 vantage points
- Peer of AS57575seen on 1,575 paths from 108 vantage points
- Peer of AS5405seen on 3,088 paths from 3 vantage points
RO
DE
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
- Amsterdam218995219451198590207252506298298This path
- London, UK21899521945119859020725257575540535280Shown above
- Sao Paulo21899521945119859020725250629291435280This 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
65%
Seen by 41 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
- Albania
- Allocated
- 10th April 2026
- Allocation block
- 2a13:c8c0::/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.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a13:c8c4:fc00::/39 | 33.6M × /64 | AS218995Bobeica Mihaita David | 63/63 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a13:c8c4:fc08::/46 | 262k × /64 | AS218995Bobeica Mihaita David | 62/63 |
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.