Network · data from 2026-11-12
AS140040 SHILMANDIONLINE-AS-AP - SHILMANDI ONLINE
Registry name: SHILMANDIONLINE-AS-AP - SHILMANDI ONLINE, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140040, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 103.147.191.0/24 | Invalid: maxLength | Other origin onlycovered by 103.147.190.0/23 | 1 0%low visibility |
| 103.147.190.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.147.190.0/23 | Valid | RIR databaseAPNIC | 2 0%low visibility |
AS-SET
AS140040 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.
- ROA: maxLength1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 103.147.191.0/24 | ROA 103.147.190.0/23 AS140040 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 103.147.191.0/24. |
| Route object: none | 103.147.191.0/24 | Route objects for it name AS131464. A route object for 103.147.190.0/23 with origin AS140040 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140040 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS140040 is announced.
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.