Network · data from 2026-11-12
AS209988
Not in the RIR AS name list · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209988, 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.
| 2a14:7581:f2f0::/44 | Valid | Nonecovered by 2a14:7581:f000::/36 | 1 0%low visibility |
| 2a14:7581:f900::/40 | Valid | Nonecovered by 2a14:7581:f000::/36 | 1 0%low visibility |
| 2a14:7581:fb70::/44 | Valid | Nonecovered by 2a14:7581:f000::/36 | 1 0%low visibility |
| 2a14:7581:fbf0::/44 | Valid | Nonecovered by 2a14:7581:f000::/36 | 1 0%low visibility |
| 2a14:7581:fe00::/40 | Valid | Nonecovered by 2a14:7581:f000::/36 | 1 0%low visibility |
AS-SET
AS209988 isn't in PeeringDB, where networks name their AS-SET.
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 8 are in fix.csv.
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a14:7581:f2f0::/44 | No route object for it. A route object for 2a14:7581:f000::/36 with origin AS209988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209988 in the RIR database for the space. |
| Route object: none | 2a14:7581:f900::/40 | No route object for it. A route object for 2a14:7581:f000::/36 with origin AS209988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209988 in the RIR database for the space. |
| Route object: none | 2a14:7581:fb70::/44 | No route object for it. A route object for 2a14:7581:f000::/36 with origin AS209988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209988 in the RIR database for the space. |
| Route object: none | 2a14:7581:fbf0::/44 | No route object for it. A route object for 2a14:7581:f000::/36 with origin AS209988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209988 in the RIR database for the space. |
| Route object: none | 2a14:7581:fe00::/40 | No route object for it. A route object for 2a14:7581:f000::/36 with origin AS209988 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209988 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS209988 whose prefix no peer sees AS209988 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.49.61.0/24 | APNIC | Valid |
| 2a12:3fc2:1200::/44 | RADB | No ROA |
| 2a14:7581:f000::/36 | RADB | 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.