103.235.204.0/23
At a glance
Addresses
/23 block
Visibility
79 of 80 vantage points
RPKI
Registry
AUAllocated 9th July 2014
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 AS9507seen on 8,171 paths from 134 vantage points
- Peer of AS1221seen on 162,718 paths from 138 vantage points
- Peer of AS4637seen on 16,519 paths from 2 vantage points
HK
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
- Singapore95079002132337This path
- London, UK9507122146378529Shown above
- Sao Paulo9507747432573356266213This path
- Oregon, US950774747473693920130This path
- Amsterdam950774747473646134549213151This 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
99%
Seen by 79 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
- APNIC — Asia-Pacific
- Country
- Australia
- Allocated
- 9th July 2014
- Allocation block
- 103.235.204.0/23
- Status
- assigned
- 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 |
|---|---|---|---|
| 103.235.206.0/23 | 512 | AS58678Intech Online Private Limited | 17/80 |
History
- AS950712th 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 103.235.204.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.