132.255.46.0/23
At a glance
Addresses
/23 block
Visibility
76 of 77 vantage points
RPKI
Registry
BRAllocated 7th November 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS267388seen on 1,305 paths from 77 vantage points
- Peer of AS61832seen on 5,556 paths from 28 vantage points
- Peer of AS6939seen on 44,429 paths from 5 vantage points
- Peer of AS38623seen on 86,250 paths from 1 vantage point
US
KHOne 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 Paulo2673886183235280This path
- Amsterdam26738861832374688298This path
- London, UK2673886183269398529This path
- Oregon, US26738861832693920130This path
- Singapore2673886183269393862323673Shown 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
99%
Seen by 76 of 77 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
- 7th November 2014
- Allocation block
- 132.255.44.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 |
|---|---|---|
| 132.255.44.0/22 | AS267388 | /24 |
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 |
|---|---|---|---|
| 132.255.44.0/22 | 1k | AS267388Voafibra Comunicacao | 77/77 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 132.255.44.0/23 | 512 | AS267388Voafibra Comunicacao | 76/77 |
History
- AS2673886th October 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 132.255.46.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.