bgpreport

Network · data from 2026-11-12

AS203483 garmin-emea Garmin International, Inc.

Registry name: garmin-emea Garmin International, Inc., US · not in PeeringDB

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

Announced routes

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

2a0c:9680:2::/47 No ROA Other origin only 635 100% 67
185.11.92.0/24 No ROA RIR databaseRIPE 673 100% 70
185.132.76.0/23 No ROA RIR databaseRIPE 673 100% 67
185.132.76.0/24 No ROA RIR databaseRIPE 673 100% 70
185.207.93.0/24 No ROA RIR databaseRIPE 672 100% 66
185.11.94.0/24 Valid Nonecovered by 185.11.94.0/23 673 100% 66
185.11.94.0/23 Valid RIR databaseRIPE 673 100% 66

AS-SET

AS203483 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 10 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2a0c:9680:2::/47No ROA covers it. Add a ROA for AS203483, maxLength 47.635 of 636
Route object: none2a0c:9680:2::/47Route objects for it name AS15830. Add a route object with origin AS203483 in the RIR database for the space.635 of 636
ROA: none185.11.92.0/24No ROA covers it. Add a ROA for AS203483, maxLength 24.673 of 673
ROA: none185.132.76.0/23No ROA covers it. Add a ROA for AS203483, maxLength 23.673 of 673
ROA: none185.132.76.0/24No ROA covers it. Add a ROA for AS203483, maxLength 24.673 of 673
ROA: none185.207.93.0/24No ROA covers it. Add a ROA for AS203483, maxLength 24.672 of 673
Route object: none185.11.94.0/24No route object for it. A route object for 185.11.94.0/23 with origin AS203483 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203483 in the RIR database for the space.673 of 673

Route objects not announced

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

185.132.77.0/24RIPENo ROA
2a0c:9680:2::/48RIPEValid
2a0c:9680:3::/48RIPEValid

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.