2a04:bac0:1000::/36
Not announced at this prefix length
We do not see 2a04:bac0:1000::/36 announced as its own route. The most specific announcement covering it is 2a04:bac0::/34, originated by AS198610 (Beget LLC). Traffic to addresses in this block follows that route.
At a glance
Subnets
/36 block
Visibility
RPKI
Registry
RUAllocated 6th March 2014
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
- Russia
- Allocated
- 6th March 2014
- Allocation block
- 2a04:bac0::/29
- Status
- allocated
- Origin validation
- Unknown
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 |
|---|---|---|---|
| 2a04:bac0::/34 | 1.1B × /64 | AS198610Beget LLC | 62/63 |
| 2a04:bac0::/29 | 34.4B × /64 | AS198610Beget LLC | 61/63 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a04:bac0::/36 | 268M × /64 | AS198610Beget LLC | 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.