Announced routes
Every prefix a peer of the route collectors sees with origin AS400768, 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.
| 2602:f2a4::/48 | Valid | Nonecovered by 2602:f2a4::/36 | 1 0%low visibility |
| 2602:f2a4:1::/48 | Valid | Nonecovered by 2602:f2a4::/36 | 1 0%low visibility |
| 2602:f2a4:2::/48 | Valid | Nonecovered by 2602:f2a4::/36 | 1 0%low visibility |
| 2602:f2a4:3::/48 | Valid | Nonecovered by 2602:f2a4::/36 | 1 0%low visibility |
| 198.179.184.0/23 | Valid | RIR databaseARIN | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS400768: ARIN::AS-CONCORD. 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 (AS400768 isn't in the set, or no route object for AS400768 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 | AS400768 in it | Not covered |
|---|---|---|---|---|---|
| ARIN::AS-CONCORD | ARIN | 0 | 1 | No | 5 |
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.
- Route object: none4
- AS-SET: own ASN1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2602:f2a4::/48 | No route object for it. A route object for 2602:f2a4::/36 with origin AS400768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400768 in the RIR database for the space. |
| Route object: none | 2602:f2a4:1::/48 | No route object for it. A route object for 2602:f2a4::/36 with origin AS400768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400768 in the RIR database for the space. |
| Route object: none | 2602:f2a4:2::/48 | No route object for it. A route object for 2602:f2a4::/36 with origin AS400768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400768 in the RIR database for the space. |
| Route object: none | 2602:f2a4:3::/48 | No route object for it. A route object for 2602:f2a4::/36 with origin AS400768 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400768 in the RIR database for the space. |
| AS-SET: own ASN | ARIN::AS-CONCORD | AS400768 isn't in AS-CONCORD (ARIN) once expanded. Add AS400768 to it. |
Route objects not announced
Route objects with origin AS400768 whose prefix no peer sees AS400768 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:f2a4::/36 | 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.