bgpreport

Network · data from 2026-11-12

AS32611 AS32611 - MERCEDES-BENZ USA, LLC

Registry name: AS32611 - MERCEDES-BENZ USA, LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS32611, 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.
141.113.158.0/23 Valid Nonecovered by 141.113.152.0/21 673 100% 66
141.113.168.0/23 Valid Nonecovered by 141.113.168.0/21 673 100% 66
141.113.171.0/24 Valid Nonecovered by 141.113.168.0/21 673 100% 66
2a03:9e41:e300::/48 Valid Nonecovered by 2a03:9e41::/32 636 100% 67
141.113.176.0/21 Valid RIR databaseRIPE 673 100% 66
141.113.184.0/21 Valid RIR databaseRIPE 673 100% 66
2a03:9e41::/32 Valid RIR databaseRADB, RIPE 633 100% 67
141.113.144.0/21 Valid RIR databaseRADB, RIPE 3 0%low visibility 3
141.113.152.0/21 Valid RIR databaseRADB, RIPE 3 0%low visibility 3
141.113.160.0/21 Valid RIR databaseRIPE 3 0%low visibility 3
141.113.168.0/21 Valid RIR databaseRIPE 3 0%low visibility 3

AS-SET

AS32611 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.

  • Route object: none4
ChangePrefix or setDetailFull-table peers
Route object: none141.113.158.0/23No route object for it. A route object for 141.113.152.0/21 with origin AS32611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32611 in the RIR database for the space.673 of 673
Route object: none141.113.168.0/23No route object for it. A route object for 141.113.168.0/21 with origin AS32611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32611 in the RIR database for the space.673 of 673
Route object: none141.113.171.0/24No route object for it. A route object for 141.113.168.0/21 with origin AS32611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32611 in the RIR database for the space.673 of 673
Route object: none2a03:9e41:e300::/48No route object for it. A route object for 2a03:9e41::/32 with origin AS32611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32611 in the RIR database for the space.636 of 636

Route objects not announced

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