103.155.118.0/24
At a glance
Addresses
/24 block
Visibility
21 of 76 vantage points
RPKI
Registry
BDAllocated 7th September 2020
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS63969seen on 11,480 paths from 139 vantage points
- Peer of AS58715seen on 12,769 paths from 139 vantage points
- Peer of AS9498seen on 852 paths from 3 vantage points
- Peer of AS3356seen on 421,631 paths from 2 vantage points
IN
US
KHOne 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
- Singapore63969587159498335623673Shown above
- London, UK1353411374531501781749494988529This path
- Oregon, US135341137453150178174949498855142013This 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
28%
Seen by 21 of 76 full-feed vantage points
Seen by few vantage pointsObserved at 1 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
- Bangladesh
- Allocated
- 7th September 2020
- Allocation block
- 103.155.118.0/23
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 103.155.118.0/24 | AS150774 | /24 |
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.155.119.0/24 | 256 | AS141155Our Online | 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 103.155.118.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.