bgpreport

Network · data from 2026-11-12

AS40659 BMW-GDCA-AS - BMW of North America, LLC (Group Data Centers America)

Registry name: BMW-GDCA-AS - BMW of North America, LLC (Group Data Centers America), US · not in PeeringDB

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

Announced routes

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

170.34.244.0/24 No ROA RIR databaseARIN 671 100% 67
170.34.242.0/24 No ROA RIR databaseARIN 668 99% 67
2605:3c80:e001::/48 No ROA RIR databaseARIN 636 100% 67
2605:3c80:a4e0::/48 No ROA RIR databaseARIN 635 100% 67

AS-SET

AS40659 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 37 are in fix.csv.

  • ROA: none4
  • Route object: not announced33
ChangePrefix or setDetailFull-table peers
ROA: none170.34.244.0/24No ROA covers it. Add a ROA for AS40659, maxLength 24.671 of 673
ROA: none170.34.242.0/24No ROA covers it. Add a ROA for AS40659, maxLength 24.668 of 673
ROA: none2605:3c80:e001::/48No ROA covers it. Add a ROA for AS40659, maxLength 48.636 of 636
ROA: none2605:3c80:a4e0::/48No ROA covers it. Add a ROA for AS40659, maxLength 48.635 of 636

Route objects not announced

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

170.34.34.0/24ARINNo ROA
170.34.41.0/24ARINNo ROA
170.34.48.0/24ARINNo ROA
170.34.59.0/24ARINNo ROA
170.34.63.0/24ARINNo ROA
170.34.80.0/24ARINNo ROA
170.34.100.0/24ARINNo ROA
170.34.104.0/24ARINNo ROA
170.34.105.0/24ARINNo ROA
170.34.113.0/24ARINNo ROA
170.34.117.0/24ARINNo ROA
170.34.118.0/24ARINNo ROA
170.34.121.0/24ARINNo ROA
170.34.127.0/24ARINNo ROA
192.109.61.0/24RIPENo ROA
192.109.67.0/24RIPENo ROA
192.109.68.0/24RIPENo ROA
192.109.69.0/24RIPENo ROA
192.109.184.0/24RIPENo ROA
192.109.185.0/24RIPENo ROA
192.109.186.0/24RIPENo ROA
192.109.187.0/24RIPENo ROA
192.109.188.0/24RIPENo ROA
205.167.100.0/23RADBNo ROA
205.167.100.0/24RADBNo ROA
205.167.101.0/24ARIN, RADBNo ROA
2605:3c80:f8::/48ARINNo ROA
2605:3c80:f9::/48ARINNo ROA
2605:3c80:fb::/48ARINNo ROA
2605:3c80:fc::/48ARINNo ROA
2605:3c80:fd::/48ARINNo ROA
2605:3c80:fe::/48ARINNo ROA
2605:3c80:ff::/48ARINNo 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.