Network · data from 2026-11-12
AS13660 BCBSND-AS - Blue Cross Blue Shield of North Dakota
Registry name: BCBSND-AS - Blue Cross Blue Shield of North Dakota, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS13660, 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.
| 199.253.128.0/24 | Invalid: maxLength | Nonecovered by 199.253.128.0/21 | 2 0%low visibility |
| 199.253.128.0/21 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS13660 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 4 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: RIR1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 199.253.128.0/24 | ROA 199.253.128.0/21 AS13660 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 199.253.128.0/24. |
| Route object: none | 199.253.128.0/24 | No route object for it. A route object for 199.253.128.0/21 with origin AS13660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13660 in the RIR database for the space. |
| Route object: RIR | 199.253.128.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS13660 whose prefix no peer sees AS13660 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2620:42:4000::/48 | RADB | No ROA |
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.