bgpreport

Network · data from 2026-11-12

AS265354 Microchip Net

Registry name: AS265354 - Microchip.Net Fibra Optica, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265354, 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.
2804:2e98::/33 No ROA Nonecovered by 2804:2e98::/32 636 100% 67
168.205.68.0/23 No ROA Nonecovered by 168.205.68.0/22 126 19% 44
168.205.70.0/23 No ROA Nonecovered by 168.205.68.0/22 126 19% 44
168.205.70.0/24 No ROA Nonecovered by 168.205.68.0/22 126 19% 44
168.205.71.0/24 No ROA Nonecovered by 168.205.68.0/22 126 19% 44
2804:2e98::/34 No ROA Nonecovered by 2804:2e98::/32 111 17% 43
168.205.68.0/22 No ROA Other IRR onlyTC 669 99% 67
2804:2e98::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS265354's PeeringDB record names no 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2804:2e98::/33No ROA covers it. Add a ROA for AS265354, maxLength 33.636 of 636
Route object: none2804:2e98::/33No route object for it. A route object for 2804:2e98::/32 with origin AS265354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265354 in the RIR database for the space.636 of 636
ROA: none168.205.68.0/23No ROA covers it. Add a ROA for AS265354, maxLength 23.126 of 673
Route object: none168.205.68.0/23No route object for it. A route object for 168.205.68.0/22 with origin AS265354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265354 in the RIR database for the space.126 of 673
ROA: none168.205.70.0/23No ROA covers it. Add a ROA for AS265354, maxLength 23.126 of 673
Route object: none168.205.70.0/23No route object for it. A route object for 168.205.68.0/22 with origin AS265354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265354 in the RIR database for the space.126 of 673
ROA: none168.205.70.0/24No ROA covers it. Add a ROA for AS265354, maxLength 24.126 of 673
Route object: none168.205.70.0/24No route object for it. A route object for 168.205.68.0/22 with origin AS265354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265354 in the RIR database for the space.126 of 673
ROA: none168.205.71.0/24No ROA covers it. Add a ROA for AS265354, maxLength 24.126 of 673
Route object: none168.205.71.0/24No route object for it. A route object for 168.205.68.0/22 with origin AS265354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265354 in the RIR database for the space.126 of 673
ROA: none2804:2e98::/34No ROA covers it. Add a ROA for AS265354, maxLength 34.111 of 636
Route object: none2804:2e98::/34No route object for it. A route object for 2804:2e98::/32 with origin AS265354 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265354 in the RIR database for the space.111 of 636
ROA: none168.205.68.0/22No ROA covers it. Add a ROA for AS265354, maxLength 22.669 of 673
Route object: RIR168.205.68.0/22Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:2e98::/32No ROA covers it. Add a ROA for AS265354, maxLength 32.636 of 636
Route object: RIR2804:2e98::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

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