Network · data from 2026-11-12
AS149024 ABIS-AS-AP - Afghan Bawar ICT Services
Registry name: ABIS-AS-AP - Afghan Bawar ICT Services, AF · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS149024, 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.
| 163.223.180.0/23 | No ROA | None | 4 1%low visibility |
| 163.223.181.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS149024 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 6 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 163.223.180.0/23 | No ROA covers it. Add a ROA for AS149024, maxLength 23. |
| Route object: none | 163.223.180.0/23 | No route object for it. Add a route object with origin AS149024 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS149024 whose prefix no peer sees AS149024 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.195.135.0/24 | AFRINIC | Invalid: origin |
| 103.176.224.0/24 | NTTCOM, RADB | No ROA |
| 103.176.225.0/24 | NTTCOM, RADB | No ROA |
| 163.223.180.0/24 | 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.