bgpreport

Network · data from 2026-11-12

AS11901 COSWAN - County of Sacramento

Registry name: COSWAN - County of Sacramento, US · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
8Route objects not announced registered with origin AS11901, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS11901, 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.
208.79.244.0/23 No ROA RIR databaseARIN 672 100% 67
208.79.246.0/23 No ROA RIR databaseARIN 672 100% 67

AS-SET

AS11901 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 10 are in fix.csv.

  • ROA: none2
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none208.79.244.0/23No ROA covers it. Add a ROA for AS11901, maxLength 23.672 of 673
ROA: none208.79.246.0/23No ROA covers it. Add a ROA for AS11901, maxLength 23.672 of 673

Route objects not announced

Route objects with origin AS11901 whose prefix no peer sees AS11901 announce. Many are kept on purpose (backup routes, space announced only in some places).

4.15.78.192/28ARINNo ROA
208.79.244.0/22ARINNo ROA
208.87.80.0/22ARINNo ROA
208.87.80.0/24ARINNo ROA
208.87.81.0/24ARINNo ROA
208.87.82.0/24ARINNo ROA
208.87.83.0/24ARINNo ROA
2620:1c:c000::/48ARINNo 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.