bgpreport

Network · data from 2026-11-12

AS31758 Griggs County Telephone Co.

Registry name: MLGC-AS - Griggs County Telephone Co., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS31758, 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.

206.62.128.0/21 No ROA Other IRR onlyALTDB, RADB 671 100% 68
104.128.0.0/20 Valid RIR databaseALTDB, ARIN 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS31758: AS31758:AS-ALL. 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 (AS31758 isn't in the set, or no route object for AS31758 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 objectsAS31758 in itNot covered
AS31758:AS-ALL ALTDB 115 Yes 0
ARIN (also)1 member set in no database: AS37158:AS-CUSTOMERS 115 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 5 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none206.62.128.0/21No ROA covers it. Add a ROA for AS31758, maxLength 21.671 of 673
Route object: RIR206.62.128.0/21Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

69.22.180.0/24ALTDBNo ROA
209.237.245.0/24NTTCOMNo ROA
2607:7500::/32ALTDB, ARINValid

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.