Network · data from 2026-11-12
AS140627 OneQode
Registry name: ONEQODEASSETS-AS-AP - OneQode, AU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140627, 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.
| 157.10.104.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 202.43.5.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 103.112.0.0/24 | Valid | Other IRR onlyRADB | 664 99% |
| 103.151.64.0/23 | Valid | RIR databaseAPNIC, RADB | 667 99% |
| 163.5.184.0/24 | Valid | RIR databaseRADB, RIPE | 667 99% |
| 2406:1540::/32 | Valid | RIR databaseAPNIC, RADB | 635 100% |
| 45.113.82.0/24 | Valid | RIR databaseAPNIC, RADB | 610 91% |
| 103.151.64.0/24 | Valid | RIR databaseAPNIC, RADB | 287 43% |
| 103.151.65.0/24 | Valid | RIR databaseAPNIC, RADB | 287 43% |
AS-SET
PeeringDB's irr_as_set for AS140627: AS140627:AS-OQ. 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 (AS140627 isn't in the set, or no route object for AS140627 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 | AS140627 in it | Not covered |
|---|---|---|---|---|---|
| AS140627:AS-OQ | RADB | 140 | 41 | Yes | 0 |
| APNIC (also)3 member sets in no database: AS-63916, AS-IDCCUBE, AS-PARSUN | 28 | 13 | 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 10 are in fix.csv.
- Route object: RIR3
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 157.10.104.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 202.43.5.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.112.0.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140627 whose prefix no peer sees AS140627 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.243.229.0/24 | RADB | No ROA |
| 88.218.236.0/23 | RADB | No ROA |
| 88.218.238.0/24 | RADB | No ROA |
| 91.108.224.0/19 | RADB | No ROA |
| 155.117.239.0/24 | RADB, RIPE | Valid |
| 163.47.18.0/24 | RADB | No ROA |
| 202.7.56.0/23 | RADB | 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.