Network · data from 2026-11-12
AS138556 ARMOUR-AS-AP - Armour Technologies Ltd.
Registry name: ARMOUR-AS-AP - Armour Technologies Ltd., BD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS138556, 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.132.224.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.132.225.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 103.132.226.0/24 | Valid | RIR databaseAPNIC | 672 100% |
| 2404:4140::/32 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:1000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:2000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:3000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:4000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:5000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:6000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:7000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:8000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:9000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:a000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:b000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:c000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:d000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:e000::/36 | Valid | RIR databaseAPNIC | 635 100% |
| 2404:4140:f000::/36 | Valid | RIR databaseAPNIC | 635 100% |
AS-SET
AS138556 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS138556 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.