170.238.36.0/23
ROMÃO E CARVALHO COMUNICAÇÃO E MULTIMÍDIA LTDA MEAS265447
PLANETCLICK TELECOMUNICACOES LTDAAS266213
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/23 block
Visibility
78 of 80 vantage points
RPKI
Registry
BRAllocated 27th October 2016
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS265447seen on 236 paths from 79 vantage points
- Peer of AS266213seen on 505 paths from 89 vantage points
- Peer of AS262355seen on 249 paths from 2 vantage points
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
- Sao Paulo266213This path
- Amsterdam265447266213262355213151Shown above
- London, UK26544726621333568529This path
- Singapore265447266213262355132337This path
- Oregon, US265447266213693920130This path
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
98%
Seen by 78 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
- 27th October 2016
- Allocation block
- 170.238.36.0/22
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 170.238.36.0/22 | AS265447 | /32 |
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 |
|---|---|---|---|
| 170.238.36.0/22 | 1k | AS265447ROMÃO E CARVALHO COMUNICAÇÃO E MULTIMÍDIA LTDA ME | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 170.238.38.0/23 | 512 | AS265447ROMÃO E CARVALHO COMUNICAÇÃO E MULTIMÍDIA LTDA ME | 79/80 |
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.
Open 170.238.36.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.