Network · data from 2026-11-12
AS215287 SecureDigitalApp Secure Digital Apps CO WLL
Registry name: SecureDigitalApp Secure Digital Apps CO WLL, BH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215287, 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.
| 96.62.152.0/24 | Invalid: origin | Other origin only | 24 4%low visibility |
| 143.223.179.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 79.175.122.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
AS-SET
AS215287 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 3 are in fix.csv.
- ROA: origin1
- ROA: none1
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 96.62.152.0/24 | ROAs covering it name AS18186, AS63902, AS140224, not AS215287. If AS215287 should announce it, add a ROA for AS215287. |
| Route object: none | 96.62.152.0/24 | Route objects for it name AS18186, AS63902, AS140224. Add a route object with origin AS215287 in the RIR database for the space. |
| ROA: none | 143.223.179.0/24 | No ROA covers it. Add a ROA for AS215287, maxLength 24. |
Route objects not announced
Every route object with origin AS215287 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.