Announced routes
Every prefix a peer of the route collectors sees with origin AS394999, 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.
| 44.31.219.23/32 | No ROA | Nonecovered by 44.31.219.0/24 | 7 1%low visibility |
| 44.31.219.0/24 | No ROA | Other IRR onlyALTDB, RADB | 670 100% |
| 2602:814:e001::/48 | Valid | Other IRR onlyALTDB | 635 100% |
| 2602:814:e000::/44 | Valid | Other IRR onlyALTDB, RADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS394999: AS-K0MWB. 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 (AS394999 isn't in the set, or no route object for AS394999 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 | AS394999 in it | Not covered |
|---|---|---|---|---|---|
| AS-K0MWB | ALTDB | 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 6 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 44.31.219.23/32 | No ROA covers it. Add a ROA for AS394999, maxLength 32. |
| Route object: none | 44.31.219.23/32 | No route object for it. A route object for 44.31.219.0/24 with origin AS394999 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS394999 in the RIR database for the space. |
| ROA: none | 44.31.219.0/24 | No ROA covers it. Add a ROA for AS394999, maxLength 24. |
| Route object: RIR | 44.31.219.0/24 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:814:e001::/48 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2602:814:e000::/44 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS394999 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.