bgpreport

Network · data from 2026-11-12

AS264000 AS264000 - FibraON - Fabricio Piloni Bertolo - ME

Registry name: AS264000 - FibraON - Fabricio Piloni Bertolo - ME, BR · not in PeeringDB

10IPv4 routes 70.0% RPKI valid · 80.0% with a route object
2IPv6 routes 50.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
30Route objects not announced registered with origin AS264000, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS264000, 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.
177.72.147.0/24 No ROA Other origin onlycovered by 177.72.146.0/23 671 100% 67
177.72.146.0/24 No ROA Other origin onlycovered by 177.72.146.0/23 670 100% 67
2804:62dc:ffff::/48 No ROA None 636 100% 67
177.72.146.0/23 No ROA Other IRR onlyRADB 670 100% 67
143.0.124.0/23 Valid Other IRR onlyRADB 672 100% 67
143.0.124.0/24 Valid Other IRR onlyRADB 672 100% 67
143.0.125.0/24 Valid Other IRR onlyRADB 672 100% 67
143.0.126.0/23 Valid Other IRR onlyRADB 672 100% 67
143.0.126.0/24 Valid Other IRR onlyRADB 672 100% 67
143.0.124.0/22 Valid Other IRR onlyALTDB, RADB 671 100% 67
143.0.127.0/24 Valid Other IRR onlyRADB 671 100% 67
2804:2924::/32 Valid Other IRR onlyALTDB, RADB 634 100% 69

AS-SET

AS264000 isn't in PeeringDB, where networks name their 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 46 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: RIR9
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
ROA: none177.72.147.0/24No ROA covers it. Add a ROA for AS264000, maxLength 24.671 of 673
Route object: none177.72.147.0/24Route objects for it name AS262414. A route object for 177.72.146.0/23 with origin AS264000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264000 in the RIR database for the space.671 of 673
ROA: none177.72.146.0/24No ROA covers it. Add a ROA for AS264000, maxLength 24.670 of 673
Route object: none177.72.146.0/24Route objects for it name AS262414. A route object for 177.72.146.0/23 with origin AS264000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264000 in the RIR database for the space.670 of 673
ROA: none2804:62dc:ffff::/48No ROA covers it. Add a ROA for AS264000, maxLength 48.636 of 636
Route object: none2804:62dc:ffff::/48No route object for it. Add a route object with origin AS264000 in the RIR database for the space.636 of 636
ROA: none177.72.146.0/23No ROA covers it. Add a ROA for AS264000, maxLength 23.670 of 673
Route object: RIR177.72.146.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR143.0.124.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.124.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.125.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.126.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR143.0.124.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR143.0.127.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:2924::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2804:2924::/33RADBValid
2804:2924::/34RADBValid
2804:2924::/35RADBValid
2804:2924::/36RADBValid
2804:2924:1000::/36RADBValid
2804:2924:2000::/35RADBValid
2804:2924:2000::/36RADBValid
2804:2924:3000::/36RADBValid
2804:2924:4000::/34RADBValid
2804:2924:4000::/35RADBValid
2804:2924:4000::/36RADBValid
2804:2924:5000::/36RADBValid
2804:2924:6000::/35RADBValid
2804:2924:6000::/36RADBValid
2804:2924:7000::/36RADBValid
2804:2924:8000::/33RADBValid
2804:2924:8000::/34RADBValid
2804:2924:8000::/35RADBValid
2804:2924:8000::/36RADBValid
2804:2924:9000::/36RADBValid
2804:2924:a000::/35RADBValid
2804:2924:a000::/36RADBValid
2804:2924:b000::/36RADBValid
2804:2924:c000::/34RADBValid
2804:2924:c000::/35RADBValid
2804:2924:c000::/36RADBValid
2804:2924:d000::/36RADBValid
2804:2924:e000::/35RADBValid
2804:2924:e000::/36RADBValid
2804:2924:f000::/36RADBValid

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.