bgpreport

Network · data from 2026-11-12

AS269016 F T L Net Provedor de Internet Ltda- ME

Registry name: AS269016 - F T L Net Provedor de Internet Ltda- ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269016, 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.
138.99.98.0/24 No ROA Other origin only 495 74% 67
45.178.27.0/24 Valid Nonecovered by 45.178.26.0/23 667 99% 67
45.178.25.0/24 Valid Nonecovered by 45.178.24.0/23 664 99% 67
45.178.26.0/24 Valid Nonecovered by 45.178.26.0/23 664 99% 67
2804:5e2c::/36 Valid Nonecovered by 2804:5e2c::/32 1 0%low visibility 1
45.178.24.0/22 Valid Other IRR onlyNTTCOM, TC 670 100% 67
45.178.24.0/24 Valid Other IRR onlyRADB 664 99% 67
2804:5e2c::/32 Valid Other IRR onlyNTTCOM, TC 634 100% 67
45.178.24.0/23 Valid Other IRR onlyRADB 202 30% 56
45.178.26.0/23 Valid Other IRR onlyRADB 202 30% 56

AS-SET

AS269016'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: none1
  • Route object: none5
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: none138.99.98.0/24No ROA covers it. Add a ROA for AS269016, maxLength 24.495 of 673
Route object: none138.99.98.0/24Route objects for it name AS28657. Add a route object with origin AS269016 in the RIR database for the space.495 of 673
Route object: none45.178.27.0/24No route object for it. A route object for 45.178.26.0/23 with origin AS269016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269016 in the RIR database for the space.667 of 673
Route object: none45.178.25.0/24No route object for it. A route object for 45.178.24.0/23 with origin AS269016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269016 in the RIR database for the space.664 of 673
Route object: none45.178.26.0/24No route object for it. A route object for 45.178.26.0/23 with origin AS269016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269016 in the RIR database for the space.664 of 673
Route object: none2804:5e2c::/36No route object for it. A route object for 2804:5e2c::/32 with origin AS269016 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269016 in the RIR database for the space.1 of 636
Route object: RIR45.178.24.0/22Route object only in NTTCOM, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.178.24.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:5e2c::/32Route object only in NTTCOM, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR45.178.24.0/23Route object only in RADB. Add it in the RIR database for the space.202 of 673
Route object: RIR45.178.26.0/23Route object only in RADB. Add it in the RIR database for the space.202 of 673

Route objects not announced

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