bgpreport

Network · data from 2026-11-12

AS10674 GRUCom

Registry name: GRUCOM - Gainesville Regional Utilities, US · PeeringDB

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

Announced routes

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

64.238.161.0/24 Invalid: maxLength Nonecovered by 64.238.160.0/19 27 4%low visibility 20
64.238.164.0/22 Invalid: maxLength Nonecovered by 64.238.160.0/19 27 4%low visibility 20
192.225.128.0/20 No ROA Other IRR onlyALTDB 668 99% 67
192.225.144.0/21 No ROA Other IRR onlyALTDB 668 99% 67
192.42.92.0/24 No ROA Other IRR onlyALTDB 666 99% 67
192.225.152.0/24 No ROA Other IRR onlyALTDB 666 99% 67
209.54.90.0/24 No ROA Other IRR onlyALTDB 666 99% 67
64.238.160.0/19 Valid RIR databaseARIN, RADB 668 99% 67
66.231.128.0/19 Valid RIR databaseARIN, RADB 668 99% 67
209.251.128.0/19 Valid RIR databaseARIN 668 99% 67
2607:4e00::/32 Valid RIR databaseARIN 631 99% 69

AS-SET

PeeringDB's irr_as_set for AS10674: ARIN::AS-GRU. 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 (AS10674 isn't in the set, or no route object for AS10674 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 objectsAS10674 in itNot covered
ARIN::AS-GRU ARIN 192165 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 30 are in fix.csv.

  • ROA: maxLength2
  • ROA: none5
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: maxLength64.238.161.0/24ROA 64.238.160.0/19 AS10674 has maxLength 19; the route is a /24. Raise the maxLength, or add a ROA for 64.238.161.0/24.27 of 673
Route object: none64.238.161.0/24No route object for it. A route object for 64.238.160.0/19 with origin AS10674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10674 in the RIR database for the space.27 of 673
ROA: maxLength64.238.164.0/22ROA 64.238.160.0/19 AS10674 has maxLength 19; the route is a /22. Raise the maxLength, or add a ROA for 64.238.164.0/22.27 of 673
Route object: none64.238.164.0/22No route object for it. A route object for 64.238.160.0/19 with origin AS10674 covers it (filters allowing more-specifics accept it). Add a route object with origin AS10674 in the RIR database for the space.27 of 673
ROA: none192.225.128.0/20No ROA covers it. Add a ROA for AS10674, maxLength 20.668 of 673
Route object: RIR192.225.128.0/20Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none192.225.144.0/21No ROA covers it. Add a ROA for AS10674, maxLength 21.668 of 673
Route object: RIR192.225.144.0/21Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none192.42.92.0/24No ROA covers it. Add a ROA for AS10674, maxLength 24.666 of 673
Route object: RIR192.42.92.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none192.225.152.0/24No ROA covers it. Add a ROA for AS10674, maxLength 24.666 of 673
Route object: RIR192.225.152.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673
ROA: none209.54.90.0/24No ROA covers it. Add a ROA for AS10674, maxLength 24.666 of 673
Route object: RIR209.54.90.0/24Route object only in ALTDB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

8.26.108.0/23RADBNo ROA
8.34.14.0/23RADBNo ROA
150.104.0.0/16ARIN, RADBNo ROA
162.212.248.0/22RADBNo ROA
192.81.80.0/22RADBNo ROA
198.184.170.0/24RADBNo ROA
198.205.104.0/21RADBNo ROA
198.212.141.0/24ALTDBNo ROA
198.212.142.0/24RADBNo ROA
204.10.176.0/21RADBNo ROA
204.124.16.0/23RADBNo ROA
204.124.18.0/24RADBNo ROA
204.147.204.0/22RADBNo ROA
208.49.78.0/24RADBNo ROA
216.194.144.0/20RADBNo ROA
216.225.240.0/20RADBNo 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.