Network · data from 2026-11-12
AS37387 Platformity
Registry name: Platformity CC - Platformity CC, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37387, 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.
| 41.79.160.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 41.79.161.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 41.79.162.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 41.79.163.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 41.223.8.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 41.223.9.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 41.223.10.0/24 | No ROA | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 2c0f:fa78::/32 | No ROA | Other IRR onlyRIPE-NONAUTH | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS37387: AFRINIC::AS-PLATFORM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS37387 isn't in the set, or no route object for AS37387 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS37387 in it | Not covered |
|---|---|---|---|---|---|
| AFRINIC::AS-PLATFORM | AFRINIC | 1 | 1 | Yes | 0 |
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 18 are in fix.csv.
- ROA: none8
- Route object: RIR8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 41.79.160.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.79.160.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.79.161.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.79.161.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.79.162.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.79.162.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.79.163.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.79.163.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.223.8.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.223.8.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.223.9.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.223.9.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 41.223.10.0/24 | No ROA covers it. Add a ROA for AS37387, maxLength 24. |
| Route object: RIR | 41.223.10.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| ROA: none | 2c0f:fa78::/32 | No ROA covers it. Add a ROA for AS37387, maxLength 32. |
| Route object: RIR | 2c0f:fa78::/32 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS37387 whose prefix no peer sees AS37387 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.79.160.0/22 | RIPE-NONAUTH | No ROA |
| 41.223.8.0/22 | RIPE-NONAUTH | 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.