201.150.44.0/23
At a glance
Addresses
/23 block
Visibility
80 of 80 vantage points
RPKI
Registry
MXAllocated 31st August 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS28546seen on 408 paths from 80 vantage points
- Peer of AS28458seen on 1,844 paths from 47 vantage points
- Peer of AS3356seen on 997,311 paths from 2 vantage points
US
BROne 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
- Amsterdam2854628458213151This path
- London, UK28546284588529This path
- Singapore2854628458132337This path
- Sao Paulo28546284583356266213Shown above
- Oregon, US2854628458693920130This 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
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
- Mexico
- Allocated
- 31st August 2011
- Allocation block
- 201.150.40.0/21
- 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 |
|---|---|---|---|
| 201.150.40.0/21 | 2k | AS28546Servnet Mexico, S.A. de C.V. | 79/80 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 201.150.44.0/24 | 256 | AS28546Servnet Mexico, S.A. de C.V. | 80/80 |
| 201.150.45.0/24 | 256 | AS28546Servnet Mexico, S.A. de C.V. | 80/80 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS2854612th 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 201.150.44.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.