2804:1674:2e::/48
GRUPOHOST COMUNICACAO MULTIMIDIA LTDAAS53231
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
59 of 65 vantage points
RPKI
Registry
BRAllocated 22nd April 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS53231seen on 2,646 paths from 141 vantage points
- Peer of AS28666seen on 3,060 paths from 133 vantage points
- Peer of AS262287seen on 5,769 paths from 147 vantage points
- Peer of AS22356seen on 5,313 paths from 51 vantage points
- Peer of AS57463seen on 18,230 paths from 5 vantage points
BG
USOne 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
- Sao Paulo532312866635280This path
- London, UK5323128666262287335635280This path
- Singapore532312866626228722356132337This path
- Amsterdam5323128666262287223565746332590Shown 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
91%
Seen by 59 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
- Brazil
- Allocated
- 22nd April 2014
- Allocation block
- 2804:1674::/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 |
|---|---|---|---|
| 2804:1674::/32 | 4.3B × /64 | AS53231GRUPOHOST COMUNICACAO MULTIMIDIA LTDA | 63/65 |
| 2804:1674::/32 | 4.3B × /64 | AS28666HostLocation Ltda | 1/65 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:1674:2f::/48 | 65.5k × /64 | AS28666HostLocation Ltda | 5/65 |
| 2804:1674:2f::/48 | 65.5k × /64 | AS53231GRUPOHOST COMUNICACAO MULTIMIDIA LTDA | 59/65 |
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.