163.223.169.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
INAllocated 20th March 2025
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS133645seen on 77 paths from 76 vantage points
- Peer of AS151845seen on 505 paths from 138 vantage points
- Peer of AS55836seen on 518,155 paths from 138 vantage points
- Peer of AS64049seen on 9,680 paths from 2 vantage points
SG
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
- Amsterdam13364515184555836640498298Shown above
- London, UK13364515184555836640498529This path
- Sao Paulo133645151845558366404935280This path
- Singapore133645151845558366404923673This path
- Oregon, US1336451518455583664049855142013This 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
- APNIC — Asia-Pacific
- Country
- India
- Allocated
- 20th March 2025
- Allocation block
- 163.223.168.0/23
- Status
- assigned
- 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
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 163.223.169.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.