bgpreport

Network · data from 2026-11-12

AS270713 GUILHERME PORTUGAL FREIXO ME

Registry name: AS270713 - GUILHERME PORTUGAL FREIXO ME, BR · PeeringDB

3IPv4 routes 0.0% RPKI valid · 100.0% with a route object
1IPv6 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
7Route objects not announced registered with origin AS270713, seen from no peer

Announced routes

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

189.127.176.0/22 No ROA Other IRR onlyRADB, TC 671 100% 66
189.127.176.0/23 No ROA Other IRR onlyRADB 671 100% 66
189.127.178.0/23 No ROA Other IRR onlyRADB 671 100% 66
2804:7038::/32 No ROA Other IRR onlyRADB, TC 631 99% 67

AS-SET

AS270713'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 15 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced7
ChangePrefix or setDetailFull-table peers
ROA: none189.127.176.0/22No ROA covers it. Add a ROA for AS270713, maxLength 22.671 of 673
Route object: RIR189.127.176.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none189.127.176.0/23No ROA covers it. Add a ROA for AS270713, maxLength 23.671 of 673
Route object: RIR189.127.176.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none189.127.178.0/23No ROA covers it. Add a ROA for AS270713, maxLength 23.671 of 673
Route object: RIR189.127.178.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:7038::/32No ROA covers it. Add a ROA for AS270713, maxLength 32.631 of 636
Route object: RIR2804:7038::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

179.124.12.0/24RADBNo ROA
189.127.176.0/24RADBNo ROA
189.127.177.0/24RADBNo ROA
189.127.178.0/24RADBNo ROA
189.127.179.0/24RADBNo ROA
2804:7038::/33RADBNo ROA
2804:7038:8000::/33RADBNo 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.