45.232.136.0/23
At a glance
Addresses
/23 block
Visibility
18 of 80 vantage points
RPKI
Registry
BRAllocated 26th March 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS267321seen on 86 paths from 21 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
US
SGOne 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 Paulo267321266213This path
- London, UK2673211374098529This path
- Singapore2673216939132337Shown above
- Oregon, US267321693920130This path
- Amsterdam26732169395829941051213151This 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
23%
Seen by 18 of 80 full-feed vantage points
Seen by few vantage pointsObserved 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
- 26th March 2018
- Allocation block
- 45.232.136.0/22
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 45.232.136.0/22 | 1k | AS267321NTISP TELECOM | 79/80 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 45.232.136.0/24 | 256 | AS267321NTISP TELECOM | 14/80 |
| 45.232.137.0/24 | 256 | AS267321NTISP TELECOM | 14/80 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 45.232.138.0/23 | 512 | AS267321NTISP TELECOM | 18/80 |
History
- AS26732112th 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 45.232.136.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.