Announced routes
Every prefix a peer of the route collectors sees with origin AS219240, 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.
| 2001:67c:644::/48 | Valid | RIR databaseRIPE | 3 0%low visibility |
| 2a06:9801:1100::/40 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS219240: AS219240:AS-UPSTREAMS. 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 (AS219240 isn't in the set, or no route object for AS219240 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 | AS219240 in it | Not covered |
|---|---|---|---|---|---|
| AS219240:AS-UPSTREAMS | RIPE | 1 | 1 | No | 2 |
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 1 are in fix.csv.
- AS-SET: own ASN1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: own ASN | AS219240:AS-UPSTREAMS | AS219240 isn't in AS219240:AS-UPSTREAMS (RIPE) once expanded. Add AS219240 to it. |
Route objects not announced
Every route object with origin AS219240 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.