Announced routes
Every prefix a peer of the route collectors sees with origin AS4927, 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.
| 64.4.132.0/24 | No ROA | Nonecovered by 64.4.128.0/19 | 673 100% |
| 64.4.128.0/19 | No ROA | Other IRR onlyRADB | 671 100% |
| 208.47.64.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 64.29.224.0/20 | Valid | RIR databaseARIN, RADB | 671 100% |
| 64.68.128.0/21 | Valid | RIR databaseARIN | 671 100% |
| 199.201.128.0/24 | Valid | RIR databaseARIN, RADB | 671 100% |
| 205.254.224.0/19 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.71.192.0/18 | Valid | RIR databaseARIN, RADB | 671 100% |
| 207.154.64.0/18 | Valid | RIR databaseARIN, RADB | 671 100% |
| 64.68.136.0/21 | Valid | RIR databaseARIN | 670 100% |
| 2001:19f8::/32 | Valid | RIR databaseARIN | 635 100% |
| 2001:19f8:8000::/36 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS4927: LEVEL3::AS-IMPU. 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 (AS4927 isn't in the set, or no route object for AS4927 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 | AS4927 in it | Not covered | |
|---|---|---|---|---|---|---|
| LEVEL3::AS-IMPU | In no IRR database read today. | |||||
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 15 are in fix.csv.
- ROA: none3
- Route object: none1
- Route object: RIR2
- AS-SET: not found1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.4.132.0/24 | No ROA covers it. Add a ROA for AS4927, maxLength 24. |
| Route object: none | 64.4.132.0/24 | No route object for it. A route object for 64.4.128.0/19 with origin AS4927 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4927 in the RIR database for the space. |
| ROA: none | 64.4.128.0/19 | No ROA covers it. Add a ROA for AS4927, maxLength 19. |
| Route object: RIR | 64.4.128.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 208.47.64.0/22 | No ROA covers it. Add a ROA for AS4927, maxLength 22. |
| Route object: RIR | 208.47.64.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | LEVEL3::AS-IMPU | PeeringDB names LEVEL3::AS-IMPU; no IRR database read has it. |
Route objects not announced
Route objects with origin AS4927 whose prefix no peer sees AS4927 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 44.6.2.0/24 | ALTDB | No ROA |
| 64.68.128.0/20 | RADB | No ROA |
| 64.68.142.0/24 | ARIN | Invalid: maxLength |
| 199.120.157.0/24 | RADB | No ROA |
| 207.154.68.0/24 | ARIN | Invalid: maxLength |
| 209.136.164.0/24 | RADB | No ROA |
| 2001:470:2e5::/48 | ARIN | Valid |
| 2001:470:621::/48 | ARIN | 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.