Network · data from 2026-11-12
AS36943 1-grid.com
Registry name: 1 GRID (PTY) LTD - 1 GRID (PTY) LTD, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36943, 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.185.3.0/24 | Valid | Nonecovered by 41.185.0.0/18 | 667 99% |
| 41.61.0.0/16 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 41.185.0.0/16 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 41.185.56.0/24 | Valid | RIR databaseAFRINIC | 673 100% |
| 196.43.195.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 196.220.32.0/19 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 673 100% |
| 2c0f:fe90::/32 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS36943: AS-1-GRID. 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 (AS36943 isn't in the set, or no route object for AS36943 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 | AS36943 in it | Not covered |
|---|---|---|---|---|---|
| AS-1-GRID | AFRINIC | 2 | 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 11 are in fix.csv.
- Route object: none1
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 41.185.3.0/24 | No route object for it. A route object for 41.185.0.0/18 with origin AS36943 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36943 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36943 whose prefix no peer sees AS36943 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 41.61.0.0/17 | AFRINIC | Valid |
| 41.61.128.0/17 | AFRINIC | Valid |
| 41.185.0.0/18 | AFRINIC | Valid |
| 41.185.64.0/18 | AFRINIC | Valid |
| 41.185.128.0/17 | AFRINIC | Valid |
| 196.220.32.0/21 | AFRINIC | Valid |
| 196.220.32.0/24 | AFRINIC | Valid |
| 196.220.40.0/21 | AFRINIC, RADB | Valid |
| 196.220.48.0/21 | AFRINIC | Valid |
| 196.220.56.0/21 | AFRINIC | 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.