163.5.191.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
Allocated 29th June 1992
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 AS154950seen on 169 paths from 66 vantage points
- Peer of AS11967seen on 1,818 paths from 118 vantage points
- Peer of AS215828seen on 1,082 paths from 121 vantage points
- Peer of AS62255seen on 286 paths from 2 vantage points
- Peer of AS4230seen on 56,132 paths from 6 vantage points
One 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
- Amsterdam154950119678298This path
- London, UK154950119672158288529This path
- Singapore15495055470558366404923673This path
- Sao Paulo1549501196721582862255423035280Shown above
- Oregon, US1549501196721582862255855142013This 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 76 of 76 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
France
- Allocated
- 29th June 1992
- Allocation block
- 163.5.0.0/16
- 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.
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 |
|---|---|---|---|
| 163.5.190.0/24 | 256 | AS216155MIRIDIA SASU | 76/76 |
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 163.5.191.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.