Network · data from 2026-11-12
AS61092 123NET fibre
Registry name: SA123NET 123 NET CPT (PTY) LTD, ZA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61092, 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.205.172.0/22 | Valid | None | 141 21% |
| 164.160.116.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 164.160.119.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 169.255.36.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 169.255.37.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 169.255.38.0/23 | Valid | Other IRR onlyRIPE-NONAUTH | 673 100% |
| 164.160.117.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 672 100% |
| 164.160.118.0/24 | Valid | Other IRR onlyRIPE-NONAUTH | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS61092: AS-123NET. 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 (AS61092 isn't in the set, or no route object for AS61092 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 | AS61092 in it | Not covered |
|---|---|---|---|---|---|
| AS-123NET | RIPE | 2 | 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 9 are in fix.csv.
- Route object: none1
- Route object: RIR7
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 102.205.172.0/22 | No route object for it. Add a route object with origin AS61092 in the RIR database for the space. |
| Route object: RIR | 164.160.116.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 164.160.119.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 169.255.36.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 169.255.37.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 169.255.38.0/23 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 164.160.117.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
| Route object: RIR | 164.160.118.0/24 | Route object only in RIPE-NONAUTH. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61092 whose prefix no peer sees AS61092 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 169.255.36.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.