bgpreport

Network · data from 2026-11-12

AS268172 Golden Fibra

Registry name: AS268172 - Golden Fibra Provedor de Internet, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268172, 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:5928::/33 No ROA Nonecovered by 2804:5928::/32 635 100% 67
2804:5928::/34 No ROA Nonecovered by 2804:5928::/32 635 100% 67
45.170.202.0/24 No ROA Other IRR onlyRADB 672 100% 66
45.170.203.0/24 No ROA Other IRR onlyRADB 671 100% 66
2804:5928::/32 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS268172'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 13 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none2804:5928::/33No ROA covers it. Add a ROA for AS268172, maxLength 33.635 of 636
Route object: none2804:5928::/33No route object for it. A route object for 2804:5928::/32 with origin AS268172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268172 in the RIR database for the space.635 of 636
ROA: none2804:5928::/34No ROA covers it. Add a ROA for AS268172, maxLength 34.635 of 636
Route object: none2804:5928::/34No route object for it. A route object for 2804:5928::/32 with origin AS268172 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268172 in the RIR database for the space.635 of 636
ROA: none45.170.202.0/24No ROA covers it. Add a ROA for AS268172, maxLength 24.672 of 673
Route object: RIR45.170.202.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none45.170.203.0/24No ROA covers it. Add a ROA for AS268172, maxLength 24.671 of 673
Route object: RIR45.170.203.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:5928::/32No ROA covers it. Add a ROA for AS268172, maxLength 32.635 of 636
Route object: RIR2804:5928::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.170.200.0/22RADB, TCNo ROA
45.170.200.0/24RADBNo ROA
45.170.201.0/24RADBNo 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.