103.153.154.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
BDAllocated 22nd July 2020
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS140930seen on 79 paths from 79 vantage points
- Peer of AS58688seen on 809 paths from 80 vantage points
- Peer of AS17494seen on 21 paths from 1 vantage point
- Peer of AS34549seen on 716,762 paths from 2 vantage points
DEOne 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
- Singapore1409305868817494132337This path
- Amsterdam140930586881749434549213151Shown above
- London, UK140930586881749464538529This path
- Oregon, US1409305868817494693920130This path
- Sao Paulo140930586881749429143356266213This 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 80 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
- Bangladesh
- Allocated
- 22nd July 2020
- Allocation block
- 103.153.154.0/23
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 103.153.154.0/23 | AS140930 | /24 |
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 103.153.154.0/23 | 512 | AS140930Pabna Cable Vision Dot Net | 80/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 103.153.155.0/24 | 256 | AS140930Pabna Cable Vision Dot Net | 80/80 |
History
- AS14093012th 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.153.154.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.