bgpreport

Network · data from 2026-11-12

AS14703 MAQSNET - MARQUETTE-ADAMS TELEPHONE COOPERATIVE, INC.

Registry name: MAQSNET - MARQUETTE-ADAMS TELEPHONE COOPERATIVE, INC., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS14703, 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.
2604:260::/32 No ROA None 636 100% 67
38.254.12.0/22 No ROA Other IRR onlyRADB 670 100% 67
154.59.60.0/22 No ROA Other IRR onlyRADB 670 100% 67
66.187.32.0/20 No ROA RIR databaseARIN, RADB 672 100% 67
66.187.40.0/21 No ROA RIR databaseARIN, RADB 672 100% 67
66.206.48.0/20 No ROA RIR databaseARIN, RADB 672 100% 67
66.206.48.0/21 No ROA RIR databaseARIN, RADB 672 100% 67
66.206.56.0/21 No ROA RIR databaseARIN, RADB 672 100% 67
66.187.32.0/22 No ROA RIR databaseARIN, RADB 670 100% 67
66.187.36.0/22 No ROA RIR databaseARIN, RADB 670 100% 67

AS-SET

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

  • ROA: none10
  • Route object: none1
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2604:260::/32No ROA covers it. Add a ROA for AS14703, maxLength 32.636 of 636
Route object: none2604:260::/32No route object for it. Add a route object with origin AS14703 in the RIR database for the space.636 of 636
ROA: none38.254.12.0/22No ROA covers it. Add a ROA for AS14703, maxLength 22.670 of 673
Route object: RIR38.254.12.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none154.59.60.0/22No ROA covers it. Add a ROA for AS14703, maxLength 22.670 of 673
Route object: RIR154.59.60.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none66.187.32.0/20No ROA covers it. Add a ROA for AS14703, maxLength 20.672 of 673
ROA: none66.187.40.0/21No ROA covers it. Add a ROA for AS14703, maxLength 21.672 of 673
ROA: none66.206.48.0/20No ROA covers it. Add a ROA for AS14703, maxLength 20.672 of 673
ROA: none66.206.48.0/21No ROA covers it. Add a ROA for AS14703, maxLength 21.672 of 673
ROA: none66.206.56.0/21No ROA covers it. Add a ROA for AS14703, maxLength 21.672 of 673
ROA: none66.187.32.0/22No ROA covers it. Add a ROA for AS14703, maxLength 22.670 of 673
ROA: none66.187.36.0/22No ROA covers it. Add a ROA for AS14703, maxLength 22.670 of 673

Route objects not announced

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