2804:20ec:4000::/34
At a glance
Subnets
/34 block
Visibility
13 of 62 vantage points
RPKI
Registry
BRAllocated 17th December 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS264521seen on 279 paths from 93 vantage points
- Peer of AS263650seen on 1,489 paths from 142 vantage points
- Peer of AS266337seen on 376 paths from 91 vantage points
- Peer of AS61945seen on 1,824 paths from 141 vantage points
- Peer of AS4230seen on 103,021 paths from 80 vantage points
- Peer of AS1299seen on 1,103 paths from 37 vantage points
- Peer of AS6461seen on 8,292 paths from 13 vantage points
- Peer of AS7473seen on 4,810 paths from 9 vantage points
- Peer of AS8966seen on 133,632 paths from 2 vantage points
SE
US
SG
AEOne 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
- London, UK264521263650266337619454230129964618218→ ⋯This path
- Singapore264521263650266337619454230129964617473→ ⋯Shown 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
21%
Seen by 13 of 62 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- 17th December 2014
- Allocation block
- 2804:20ec::/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:20ec::/32 | 4.3B × /64 | AS264521SLIM NET TELECOM LTDA | 13/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2804:20ec::/34 | 1.1B × /64 | AS264521SLIM NET TELECOM LTDA | 13/62 |
History
- AS26452112th August 2026 — present
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.