Network · data from 2026-11-12
AS138004 MIR INFO SYSTEMS
Registry name: MISL-AS-AP - MIR INFO SYSTEMS LTD., BD · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138004, 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.77.101.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.138.214.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.139.144.0/24 | Invalid: origin | Other origin only | 0 0%low visibility |
| 103.10.194.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.10.195.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.52.140.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.52.141.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.52.143.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.135.234.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.135.235.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.142.69.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.94.20.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 180.94.20.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 180.94.21.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.125.64.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.125.66.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.125.67.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.125.68.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 202.125.79.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 103.72.198.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 202.125.78.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2401:51e0::/32 | Valid | RIR databaseAPNIC | 636 100% |
AS-SET
AS138004's PeeringDB record names no 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 10 are in fix.csv.
- ROA: origin3
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 103.77.101.0/24 | ROAs covering it name AS149994, not AS138004. If AS138004 should announce it, add a ROA for AS138004. |
| Route object: none | 103.77.101.0/24 | Route objects for it name AS149994. Add a route object with origin AS138004 in the RIR database for the space. |
| ROA: origin | 103.138.214.0/24 | ROAs covering it name AS149994, not AS138004. If AS138004 should announce it, add a ROA for AS138004. |
| Route object: none | 103.138.214.0/24 | Route objects for it name AS149994. Add a route object with origin AS138004 in the RIR database for the space. |
| ROA: origin | 103.139.144.0/24 | ROAs covering it name AS149994, not AS138004. If AS138004 should announce it, add a ROA for AS138004. |
| Route object: none | 103.139.144.0/24 | Route objects for it name AS149994. Add a route object with origin AS138004 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS138004 whose prefix no peer sees AS138004 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.10.194.0/23 | APNIC | Valid |
| 103.117.84.0/22 | RADB | No ROA |
| 2001:df1:4dc0::/48 | APNIC | Valid |
| 2403:1640::/32 | RADB | No ROA |
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.