103.243.76.0/22
At a glance
Addresses
/22 block
Visibility
79 of 80 vantage points
RPKI
Registry
BDAllocated 8th October 2013
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 AS59315seen on 79 paths from 79 vantage points
- Peer of AS140889seen on 852 paths from 142 vantage points
- Peer of AS38008seen on 2,245 paths from 106 vantage points
- Peer of AS3356seen on 148,979 paths from 2 vantage points
HK
US
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
- Singapore5931514088938008132337This path
- London, UK593151408893800833568529Shown above
- Sao Paulo59315140889380083356266213This path
- Oregon, US5931514088938008693920130This path
- Amsterdam59315140889380083491291434549213151This 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
- Bangladesh
- Allocated
- 8th October 2013
- Allocation block
- 103.243.76.0/22
- 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.243.76.0/22 | AS59315 | /22 |
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
- AS5931512th 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.243.76.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.