bgpreport

Network · data from 2026-11-12

AS269600 Fourfibras Serviços de Telecom

Registry name: AS269600 - Fourfibras Servicos de Telecom LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269600, 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:670c::/33 No ROA Nonecovered by 2804:670c::/32 636 100% 67
45.187.80.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
45.187.80.0/23 No ROA Other IRR onlyRADB 671 100% 67
45.187.82.0/23 No ROA Other IRR onlyRADB 671 100% 67
45.187.82.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.187.83.0/24 No ROA Other IRR onlyRADB 671 100% 67
45.187.80.0/24 No ROA Other IRR onlyRADB 670 100% 67
45.187.81.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:670c::/32 No ROA Other IRR onlyRADB, TC 636 100% 67

AS-SET

AS269600'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 18 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none2804:670c::/33No ROA covers it. Add a ROA for AS269600, maxLength 33.636 of 636
Route object: none2804:670c::/33No route object for it. A route object for 2804:670c::/32 with origin AS269600 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269600 in the RIR database for the space.636 of 636
ROA: none45.187.80.0/22No ROA covers it. Add a ROA for AS269600, maxLength 22.671 of 673
Route object: RIR45.187.80.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none45.187.80.0/23No ROA covers it. Add a ROA for AS269600, maxLength 23.671 of 673
Route object: RIR45.187.80.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.187.82.0/23No ROA covers it. Add a ROA for AS269600, maxLength 23.671 of 673
Route object: RIR45.187.82.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.187.82.0/24No ROA covers it. Add a ROA for AS269600, maxLength 24.671 of 673
Route object: RIR45.187.82.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.187.83.0/24No ROA covers it. Add a ROA for AS269600, maxLength 24.671 of 673
Route object: RIR45.187.83.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none45.187.80.0/24No ROA covers it. Add a ROA for AS269600, maxLength 24.670 of 673
Route object: RIR45.187.80.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none45.187.81.0/24No ROA covers it. Add a ROA for AS269600, maxLength 24.670 of 673
Route object: RIR45.187.81.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:670c::/32No ROA covers it. Add a ROA for AS269600, maxLength 32.636 of 636
Route object: RIR2804:670c::/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 AS269600 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.