bgpreport

Network · data from 2026-11-12

AS397142 City of Fort Collins

Registry name: FORT-COLLINS-CONNEXION - City of Fort Collins, US · PeeringDB

13IPv4 routes 84.6% RPKI valid · 100.0% with a route object
10IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
0Route objects not announced registered with origin AS397142, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS397142, 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.
204.133.79.0/24 No ROA RIR databaseARIN 670 100% 68
204.133.83.0/24 No ROA RIR databaseARIN 670 100% 68
23.163.32.0/24 Valid RIR databaseARIN 670 100% 68
38.15.32.0/19 Valid RIR databaseARIN, RADB 670 100% 68
38.75.232.0/21 Valid RIR databaseARIN, RADB 670 100% 68
38.80.148.0/22 Valid RIR databaseARIN, RADB 670 100% 68
38.147.232.0/21 Valid RIR databaseARIN, RADB 670 100% 68
38.175.160.0/19 Valid RIR databaseARIN, RADB 670 100% 68
38.246.0.0/19 Valid RIR databaseARIN, RADB 670 100% 68
167.94.176.0/20 Valid RIR databaseARIN 670 100% 68
192.251.149.0/24 Valid RIR databaseARIN 670 100% 68
198.99.80.0/22 Valid RIR databaseARIN 670 100% 68
204.107.184.0/24 Valid RIR databaseARIN 670 100% 68
2605:b40::/32 Valid RIR databaseARIN 635 100% 69
2605:b40:1200::/40 Valid RIR databaseARIN 605 95% 67
2605:b40:1300::/40 Valid RIR databaseARIN 605 95% 67
2605:b40:2100::/40 Valid RIR databaseARIN 605 95% 67
2605:b40:2200::/40 Valid RIR databaseARIN 605 95% 67
2605:b40:2300::/40 Valid RIR databaseARIN 605 95% 67
2605:b40:2400::/40 Valid RIR databaseARIN 605 95% 67
2605:b40:f0c0::/48 Valid RIR databaseARIN 605 95% 67
2605:b40:1100::/40 Valid RIR databaseARIN 604 95% 67
2605:b40:1400::/40 Valid RIR databaseARIN 604 95% 67

AS-SET

PeeringDB's irr_as_set for AS397142: AS-FCC-EPTBB-LP-LNL. 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 (AS397142 isn't in the set, or no route object for AS397142 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.

NameDatabaseASNsSets Route objectsAS397142 in itNot covered
AS-FCC-EPTBB-LP-LNL ARIN 111200 Yes 0

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

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none204.133.79.0/24No ROA covers it. Add a ROA for AS397142, maxLength 24.670 of 673
ROA: none204.133.83.0/24No ROA covers it. Add a ROA for AS397142, maxLength 24.670 of 673

Route objects not announced

Every route object with origin AS397142 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.