Announced routes
Every prefix a peer of the route collectors sees with origin AS207606, 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.
| 149.100.176.0/24 | No ROA | Nonecovered by 149.100.176.0/22 | 673 100% |
| 149.100.177.0/24 | No ROA | Nonecovered by 149.100.176.0/22 | 673 100% |
| 2a04:1a80::/29 | No ROA | None | 324 51% |
| 149.100.176.0/22 | No ROA | Other IRR onlyRADB | 671 100% |
| 91.206.231.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS207606: AS207606. 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 (AS207606 isn't in the set, or no route object for AS207606 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 | AS207606 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS207606 | A single AS number, not a set: AS207606 (this network), 2 route objects. | |||||
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.
- ROA: none5
- Route object: none3
- Route object: RIR1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 149.100.176.0/24 | No ROA covers it. Add a ROA for AS207606, maxLength 24. |
| Route object: none | 149.100.176.0/24 | No route object for it. A route object for 149.100.176.0/22 with origin AS207606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207606 in the RIR database for the space. |
| ROA: none | 149.100.177.0/24 | No ROA covers it. Add a ROA for AS207606, maxLength 24. |
| Route object: none | 149.100.177.0/24 | No route object for it. A route object for 149.100.176.0/22 with origin AS207606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS207606 in the RIR database for the space. |
| ROA: none | 2a04:1a80::/29 | No ROA covers it. Add a ROA for AS207606, maxLength 29. |
| Route object: none | 2a04:1a80::/29 | No route object for it. Add a route object with origin AS207606 in the RIR database for the space. |
| ROA: none | 149.100.176.0/22 | No ROA covers it. Add a ROA for AS207606, maxLength 22. |
| Route object: RIR | 149.100.176.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 91.206.231.0/24 | No ROA covers it. Add a ROA for AS207606, maxLength 24. |
Route objects not announced
Every route object with origin AS207606 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.