2803:9800:b881::/48
At a glance
Subnets
/48 block
Visibility
63 of 65 vantage points
RPKI
Registry
ARAllocated 12th March 2012
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.
Route visibility
97%
Seen by 63 of 65 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
- LACNIC — Latin America and the Caribbean
- Country
- Argentina
- Allocated
- 12th March 2012
- Allocation block
- 2803:9800::/32
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 2803:9800::/32 | 4.3B × /64 | AS11664Techtel LMDS Comunicaciones Interactivas S.A. | 64/65 |
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
We have no history for this prefix yet. History is built forward from the first snapshot that contained it.
Routing data derived from RouteViews MRT archives and public registry data.