bgpreport

Network · data from 2026-11-12

AS26960 MICHELIN-NORTH-AMERICA-I1 - MICHELIN NORTH AMERICA

Registry name: MICHELIN-NORTH-AMERICA-I1 - MICHELIN NORTH AMERICA, US · not in PeeringDB

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

Announced routes

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

156.65.0.0/19 No ROA None 671 100% 67
156.65.8.0/24 No ROA None 671 100% 67
156.65.9.0/24 No ROA None 671 100% 67
156.65.10.0/24 No ROA None 671 100% 67
156.65.11.0/24 No ROA None 671 100% 67
156.65.12.0/24 No ROA None 671 100% 67
156.65.13.0/24 No ROA None 671 100% 67
156.65.14.0/24 No ROA None 671 100% 67
156.65.15.0/24 No ROA None 671 100% 67
156.65.46.0/24 No ROA Other origin only 671 100% 67
156.65.47.0/24 No ROA Other origin only 671 100% 67
156.65.248.0/24 No ROA None 671 100% 67
156.65.249.0/24 No ROA None 671 100% 67
156.65.250.0/24 No ROA None 671 100% 67
156.65.251.0/24 No ROA None 671 100% 67

AS-SET

AS26960 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 30 are in fix.csv.

  • ROA: none15
  • Route object: none15
ChangePrefix or setDetailFull-table peers
ROA: none156.65.0.0/19No ROA covers it. Add a ROA for AS26960, maxLength 19.671 of 673
Route object: none156.65.0.0/19No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.8.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.8.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.9.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.9.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.10.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.10.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.11.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.11.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.12.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.12.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.13.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.13.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.14.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.14.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.15.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.15.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.46.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.46.0/24Route objects for it name AS141167. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.47.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.47.0/24Route objects for it name AS141167. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.248.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.248.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.249.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.249.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.250.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.250.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673
ROA: none156.65.251.0/24No ROA covers it. Add a ROA for AS26960, maxLength 24.671 of 673
Route object: none156.65.251.0/24No route object for it. Add a route object with origin AS26960 in the RIR database for the space.671 of 673

Route objects not announced

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