Network · data from 2026-11-12
AS140613 SAIMUNENTERPRISE-AS-AP - Saimun Enterprise
Registry name: SAIMUNENTERPRISE-AS-AP - Saimun Enterprise, BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140613, 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.
| 223.165.2.0/24 | Invalid: maxLength | Other origin onlycovered by 223.165.2.0/23 | 0 0%low visibility |
AS-SET
AS140613 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 4 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 223.165.2.0/24 | ROA 223.165.2.0/23 AS140613 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 223.165.2.0/24. |
| Route object: none | 223.165.2.0/24 | Route objects for it name AS138501. A route object for 223.165.2.0/23 with origin AS140613 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140613 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140613 whose prefix no peer sees AS140613 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 223.165.2.0/23 | APNIC | Valid |
| 2001:df6:26c0::/48 | APNIC | Valid |
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.