bgpreport

Network · data from 2026-11-12

AS270547 KERKHOFEN & MORREIRA

Registry name: AS270547 - KERKHOFEN & MORREIRA LTDA ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270547, 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.
190.111.180.0/23 No ROA Nonecovered by 190.111.180.0/22 665 99% 67
190.111.182.0/23 No ROA Nonecovered by 190.111.180.0/22 665 99% 67
2804:6da8::/33 No ROA Nonecovered by 2804:6da8::/32 635 100% 67
2804:6da8:8000::/33 No ROA Nonecovered by 2804:6da8::/32 635 100% 67
190.111.180.0/22 No ROA Other IRR onlyRADB, TC 668 99% 66

AS-SET

AS270547'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 11 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none190.111.180.0/23No ROA covers it. Add a ROA for AS270547, maxLength 23.665 of 673
Route object: none190.111.180.0/23No route object for it. A route object for 190.111.180.0/22 with origin AS270547 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270547 in the RIR database for the space.665 of 673
ROA: none190.111.182.0/23No ROA covers it. Add a ROA for AS270547, maxLength 23.665 of 673
Route object: none190.111.182.0/23No route object for it. A route object for 190.111.180.0/22 with origin AS270547 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270547 in the RIR database for the space.665 of 673
ROA: none2804:6da8::/33No ROA covers it. Add a ROA for AS270547, maxLength 33.635 of 636
Route object: none2804:6da8::/33No route object for it. A route object for 2804:6da8::/32 with origin AS270547 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270547 in the RIR database for the space.635 of 636
ROA: none2804:6da8:8000::/33No ROA covers it. Add a ROA for AS270547, maxLength 33.635 of 636
Route object: none2804:6da8:8000::/33No route object for it. A route object for 2804:6da8::/32 with origin AS270547 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270547 in the RIR database for the space.635 of 636
ROA: none190.111.180.0/22No ROA covers it. Add a ROA for AS270547, maxLength 22.668 of 673
Route object: RIR190.111.180.0/22Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

2804:6da8::/32TCNo 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.