Network · data from 2026-11-12
AS37314 inq.
Registry name: Inq Digital South Africa (Pty) Ltd - Inq Digital South Africa (Pty) Ltd, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS37314, 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.
| 102.69.236.179/32 | No ROA | Nonecovered by 102.69.236.0/23 | 0 0%low visibility |
| 102.69.236.0/23 | No ROA | RIR databaseAFRINIC | 672 100% |
| 102.69.237.0/24 | No ROA | RIR databaseAFRINIC | 672 100% |
| 102.219.224.0/23 | No ROA | RIR databaseAFRINIC | 672 100% |
| 168.155.16.0/24 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 192.70.200.0/24 | No ROA | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 41.79.20.0/22 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 41.79.20.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 41.79.21.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 41.79.22.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 154.119.64.0/20 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 154.119.64.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 154.119.66.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 154.119.76.0/24 | Valid | RIR databaseAFRINIC | 672 100% |
| 154.119.78.0/24 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 165.16.128.0/19 | Valid | RIR databaseAFRINIC, RIPE-NONAUTH | 672 100% |
| 165.16.128.0/24 | Valid | RIR databaseAFRINIC | 672 100% |
| 2c0f:f1a0::/32 | Valid | RIR databaseAFRINIC | 634 100% |
| 2c0f:f1a0::/44 | Valid | RIR databaseAFRINIC | 634 100% |
| 2c0f:f1a0:8100::/40 | Valid | RIR databaseAFRINIC | 634 100% |
| 2c0f:f1a0:8300::/40 | Valid | RIR databaseAFRINIC | 634 100% |
| 2c0f:f1a0:8400::/40 | Valid | RIR databaseAFRINIC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS37314: AS-SYREX. 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 (AS37314 isn't in the set, or no route object for AS37314 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 | AS37314 in it | Not covered |
|---|---|---|---|---|---|
| AS-SYREX | AFRINIC | 9 | 3 | Yes | 1 |
| RIPE (also)2 member sets in no database: AS37314:AS-CUSTOMERS, AS37314:AS-CUSTOMERS:AS328074 | 1 | 1 | Yes | 1 |
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 7 are in fix.csv.
- ROA: none6
- Route object: none1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 102.69.236.179/32 | No ROA covers it. Add a ROA for AS37314, maxLength 32. |
| Route object: none | 102.69.236.179/32 | No route object for it. A route object for 102.69.236.0/23 with origin AS37314 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS37314 in the RIR database for the space. |
| ROA: none | 102.69.236.0/23 | No ROA covers it. Add a ROA for AS37314, maxLength 23. |
| ROA: none | 102.69.237.0/24 | No ROA covers it. Add a ROA for AS37314, maxLength 24. |
| ROA: none | 102.219.224.0/23 | No ROA covers it. Add a ROA for AS37314, maxLength 23. |
| ROA: none | 168.155.16.0/24 | No ROA covers it. Add a ROA for AS37314, maxLength 24. |
| ROA: none | 192.70.200.0/24 | No ROA covers it. Add a ROA for AS37314, maxLength 24. |
Route objects not announced
Every route object with origin AS37314 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.