2a00:4802:4c10::/44
Not announced at this prefix length
We do not see 2a00:4802:4c10::/44 announced as its own route. The most specific announcement covering it is 2a00:4800::/29, originated by AS8717 (A1 Bulgaria EAD). Traffic to addresses in this block follows that route.
At a glance
Subnets
/44 block
Visibility
RPKI
Registry
BGAllocated 8th December 2010
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
- Bulgaria
- Allocated
- 8th December 2010
- Allocation block
- 2a00:4800::/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 |
|---|---|---|---|
| 2a00:4800::/29 | 34.4B × /64 | AS8717A1 Bulgaria EAD | 63/63 |
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.