bgpreport

Network · data from 2026-11-12

AS265121 FUTURA ONLINE

Registry name: AS265121 - FUTURA ONLINE INFORMATICA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265121, 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.
143.208.116.0/23 No ROA Nonecovered by 143.208.116.0/22 2 0%low visibility 2
143.208.118.0/23 No ROA Nonecovered by 143.208.116.0/22 2 0%low visibility 2
143.208.116.0/24 No ROA Other IRR onlyRADB 667 99% 67
143.208.118.0/24 No ROA Other IRR onlyRADB 667 99% 67
143.208.119.0/24 No ROA Other IRR onlyRADB 667 99% 67
143.208.117.0/24 No ROA Other IRR onlyRADB 666 99% 67
143.208.116.0/22 No ROA Other IRR onlyALTDB, RADB 2 0%low visibility 2

AS-SET

AS265121'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: none7
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none143.208.116.0/23No ROA covers it. Add a ROA for AS265121, maxLength 23.2 of 673
Route object: none143.208.116.0/23No route object for it. A route object for 143.208.116.0/22 with origin AS265121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265121 in the RIR database for the space.2 of 673
ROA: none143.208.118.0/23No ROA covers it. Add a ROA for AS265121, maxLength 23.2 of 673
Route object: none143.208.118.0/23No route object for it. A route object for 143.208.116.0/22 with origin AS265121 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265121 in the RIR database for the space.2 of 673
ROA: none143.208.116.0/24No ROA covers it. Add a ROA for AS265121, maxLength 24.667 of 673
Route object: RIR143.208.116.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none143.208.118.0/24No ROA covers it. Add a ROA for AS265121, maxLength 24.667 of 673
Route object: RIR143.208.118.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none143.208.119.0/24No ROA covers it. Add a ROA for AS265121, maxLength 24.667 of 673
Route object: RIR143.208.119.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none143.208.117.0/24No ROA covers it. Add a ROA for AS265121, maxLength 24.666 of 673
Route object: RIR143.208.117.0/24Route object only in RADB. Add it in the RIR database for the space.666 of 673
ROA: none143.208.116.0/22No ROA covers it. Add a ROA for AS265121, maxLength 22.2 of 673
Route object: RIR143.208.116.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

2804:2ad4::/32ALTDB, RADBNo 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.