187.252.252.0/23
At a glance
Addresses
/23 block
Visibility
59 of 77 vantage points
RPKI
Registry
MXAllocated 14th September 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS28509seen on 18,702 paths from 141 vantage points
- Peer of AS18734seen on 11,059 paths from 65 vantage points
- Peer of AS3356seen on 119,316 paths from 3 vantage points
- Peer of AS57866seen on 6,307 paths from 2 vantage points
- Peer of AS8283seen on 62,467 paths from 2 vantage points
US
NL
CHOne 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, UK285091873433568529This path
- Sao Paulo2850918734335635280This path
- Singapore2850918734174349123673This path
- Oregon, US28509187343356693920130This path
- Amsterdam285091873433565786682838298Shown 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
77%
Seen by 59 of 77 full-feed vantage points
Partially 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
- 14th September 2012
- Allocation block
- 187.252.0.0/15
- 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 |
|---|---|---|---|
| 187.252.252.0/22 | 1k | AS16960Cablevision Red, S.A de C.V. | 77/77 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
No prefix of the same length in the same parent block is announced.
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 187.252.252.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.