Network · data from 2026-11-12
AS204300 IIL-NET D2CLOUD NETWORK SERVICES (PTY) LTD
Registry name: IIL-NET D2CLOUD NETWORK SERVICES (PTY) LTD, ZA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204300, 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.
| 94.142.130.0/24 | No ROA | None | 673 100% |
| 185.155.74.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 193.24.212.0/22 | Valid | None | 673 100% |
| 185.21.128.0/24 | Valid | Other origin only | 147 22% |
| 91.242.75.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 95.164.196.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 164.163.124.0/24 | Valid | RIR databaseLACNIC | 671 100% |
| 193.107.40.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 194.35.52.0/22 | Valid | RIR databaseRIPE | 671 100% |
| 195.138.118.0/24 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
AS204300 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: none2
- Route object: none3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.142.130.0/24 | No ROA covers it. Add a ROA for AS204300, maxLength 24. |
| Route object: none | 94.142.130.0/24 | No route object for it. Add a route object with origin AS204300 in the RIR database for the space. |
| ROA: none | 185.155.74.0/24 | No ROA covers it. Add a ROA for AS204300, maxLength 24. |
| Route object: none | 193.24.212.0/22 | No route object for it. Add a route object with origin AS204300 in the RIR database for the space. |
| Route object: none | 185.21.128.0/24 | Route objects for it name AS7018. Add a route object with origin AS204300 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS204300 whose prefix no peer sees AS204300 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.4.204.0/23 | LACNIC | 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.