177.85.13.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
BRAllocated 20th August 2020
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS271251seen on 80 paths from 80 vantage points
- Peer of AS272487seen on 76 paths from 76 vantage points
- Peer of AS267618seen on 105 paths from 87 vantage points
- Peer of AS264598seen on 3,748 paths from 136 vantage points
- Peer of AS23106seen on 20,288 paths from 68 vantage points
- Peer of AS52320seen on 213,520 paths from 71 vantage points
- Peer of AS6939seen on 309,709 paths from 2 vantage points
CO
US
DEOne 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, UK271251272487215748529This path
- Sao Paulo27125127248721574266213This path
- Singapore27125127248721574263444132337This path
- Oregon, US27125127248721574719532572335220130This path
- Amsterdam27125127248726761826459823106523206939213151Shown 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
100%
Seen by 80 of 80 full-feed vantage points
Globally propagatedObserved at 5 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
- 20th August 2020
- Allocation block
- 177.85.12.0/22
- 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 |
|---|---|---|---|
| 177.85.12.0/22 | 1k | AS271251LAR NET TELECOMUNICAÇÕES LTDA | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 177.85.12.0/24 | 256 | AS271251LAR NET TELECOMUNICAÇÕES LTDA | 80/80 |
History
- AS27125112th 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.
Open 177.85.13.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.