bgpreport

Network · data from 2026-11-12

AS62759 Reedsburg Utility Commission (LightSpeed)

Registry name: RUCLS1 - Reedsburg Utility Commission, US · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS62759, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS62759, 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.
140.174.192.0/20 Valid Other IRR onlyNTTCOM 673 100% 67
74.119.124.0/22 Valid RIR databaseARIN 673 100% 67
162.245.176.0/21 Valid RIR databaseARIN, RADB 673 100% 67
163.123.240.0/22 Valid RIR databaseARIN 673 100% 67
199.255.20.0/22 Valid RIR databaseARIN 673 100% 67
2604:46c0::/32 Valid RIR databaseARIN 634 100% 67

AS-SET

AS62759's PeeringDB record names no 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 1 are in fix.csv.

  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: RIR140.174.192.0/20Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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