201.218.151.0/24
M & B Soluciones Peru S.A.C. (FASTNET)AS269862
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
55 of 78 vantage points
RPKI
Registry
EEAllocated 20th June 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS269862seen on 55 paths from 55 vantage points
- Peer of AS270007seen on 2,669 paths from 142 vantage points
- Peer of AS7195seen on 5,530 paths from 2 vantage points
PE
CO
AEOne 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
- Amsterdam26986227000771958298This path
- London, UK26986227000771958529Shown above
- Sao Paulo269862270007719535280This path
- Singapore5243964146335623673This path
- Oregon, US2698622700077195855142013This 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
71%
Seen by 55 of 78 full-feed vantage points
Partially propagatedObserved at 4 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- Estonia
- Allocated
- 20th June 2012
- Allocation block
- 201.218.128.0/19
- 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.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 201.218.150.0/24 | 256 | AS269862M & B Soluciones Peru S.A.C. (FASTNET) | 78/78 |
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 201.218.151.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.