bgpreport

Network · data from 2026-11-12

AS43108 GARM-AS GARMTECH LP

Registry name: GARM-AS GARMTECH LP, GB · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43108, 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.
91.194.77.221/32 Invalid: maxLength Nonecovered by 91.194.76.0/23 2 0%low visibility 2
193.169.166.0/23 No ROA RIR databaseRIPE 673 100% 66
185.242.184.0/24 Valid Other origin only 673 100% 66
91.194.76.0/23 Valid RIR databaseRIPE 673 100% 66
91.228.4.0/22 Valid RIR databaseRIPE 673 100% 66
178.213.48.0/21 Valid RIR databaseRIPE 673 100% 66
195.28.26.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

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

  • ROA: maxLength1
  • ROA: none1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: maxLength91.194.77.221/32ROA 91.194.76.0/23 AS43108 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 91.194.77.221/32.2 of 673
Route object: none91.194.77.221/32No route object for it. A route object for 91.194.76.0/23 with origin AS43108 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43108 in the RIR database for the space.2 of 673
ROA: none193.169.166.0/23No ROA covers it. Add a ROA for AS43108, maxLength 23.673 of 673
Route object: none185.242.184.0/24Route objects for it name AS60320. Add a route object with origin AS43108 in the RIR database for the space.673 of 673

Route objects not announced

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