bgpreport

Network · data from 2026-11-12

AS272250 AS272250 - FX INFOTELECOM

Registry name: AS272250 - FX INFOTELECOM, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272250, 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:8444::/34 No ROA Nonecovered by 2804:8444::/33 634 100% 67
2804:8444:4000::/34 No ROA Nonecovered by 2804:8444::/33 634 100% 67
2804:8444:8000::/34 No ROA Nonecovered by 2804:8444:8000::/33 634 100% 67
2804:8444:c000::/34 No ROA Nonecovered by 2804:8444:8000::/33 634 100% 67
2804:8444::/32 No ROA Other IRR onlyRADB, TC 1 0%low visibility 1

AS-SET

AS272250 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 12 are in fix.csv.

  • ROA: none5
  • Route object: none4
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:8444::/34No ROA covers it. Add a ROA for AS272250, maxLength 34.634 of 636
Route object: none2804:8444::/34No route object for it. A route object for 2804:8444::/33 with origin AS272250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272250 in the RIR database for the space.634 of 636
ROA: none2804:8444:4000::/34No ROA covers it. Add a ROA for AS272250, maxLength 34.634 of 636
Route object: none2804:8444:4000::/34No route object for it. A route object for 2804:8444::/33 with origin AS272250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272250 in the RIR database for the space.634 of 636
ROA: none2804:8444:8000::/34No ROA covers it. Add a ROA for AS272250, maxLength 34.634 of 636
Route object: none2804:8444:8000::/34No route object for it. A route object for 2804:8444:8000::/33 with origin AS272250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272250 in the RIR database for the space.634 of 636
ROA: none2804:8444:c000::/34No ROA covers it. Add a ROA for AS272250, maxLength 34.634 of 636
Route object: none2804:8444:c000::/34No route object for it. A route object for 2804:8444:8000::/33 with origin AS272250 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272250 in the RIR database for the space.634 of 636
ROA: none2804:8444::/32No ROA covers it. Add a ROA for AS272250, maxLength 32.1 of 636
Route object: RIR2804:8444::/32Route object only in RADB, TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

2804:8444::/33TCNo ROA
2804:8444:8000::/33TCNo 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.