bgpreport

Network · data from 2026-11-12

AS272249 AS272249 - IFLEX TELECOM LTDA

Registry name: AS272249 - IFLEX TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272249, 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:8440::/34 No ROA Nonecovered by 2804:8440::/33 628 99% 67
2804:8440:4000::/34 No ROA Nonecovered by 2804:8440::/33 628 99% 67
2804:8440:8000::/33 No ROA Nonecovered by 2804:8440::/32 628 99% 67
2804:8440:8000::/34 No ROA Nonecovered by 2804:8440::/32 628 99% 67
2804:8440:c000::/34 No ROA Nonecovered by 2804:8440::/32 628 99% 67
2804:8440::/32 No ROA Other IRR onlyALTDB, RADB, TC 628 99% 67
2804:8440::/33 No ROA Other IRR onlyTC 628 99% 67

AS-SET

AS272249 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none5
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2804:8440::/34No ROA covers it. Add a ROA for AS272249, maxLength 34.628 of 636
Route object: none2804:8440::/34No route object for it. A route object for 2804:8440::/33 with origin AS272249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272249 in the RIR database for the space.628 of 636
ROA: none2804:8440:4000::/34No ROA covers it. Add a ROA for AS272249, maxLength 34.628 of 636
Route object: none2804:8440:4000::/34No route object for it. A route object for 2804:8440::/33 with origin AS272249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272249 in the RIR database for the space.628 of 636
ROA: none2804:8440:8000::/33No ROA covers it. Add a ROA for AS272249, maxLength 33.628 of 636
Route object: none2804:8440:8000::/33No route object for it. A route object for 2804:8440::/32 with origin AS272249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272249 in the RIR database for the space.628 of 636
ROA: none2804:8440:8000::/34No ROA covers it. Add a ROA for AS272249, maxLength 34.628 of 636
Route object: none2804:8440:8000::/34No route object for it. A route object for 2804:8440::/32 with origin AS272249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272249 in the RIR database for the space.628 of 636
ROA: none2804:8440:c000::/34No ROA covers it. Add a ROA for AS272249, maxLength 34.628 of 636
Route object: none2804:8440:c000::/34No route object for it. A route object for 2804:8440::/32 with origin AS272249 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272249 in the RIR database for the space.628 of 636
ROA: none2804:8440::/32No ROA covers it. Add a ROA for AS272249, maxLength 32.628 of 636
Route object: RIR2804:8440::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.628 of 636
ROA: none2804:8440::/33No ROA covers it. Add a ROA for AS272249, maxLength 33.628 of 636
Route object: RIR2804:8440::/33Route object only in TC. Add it in the RIR database for the space.628 of 636

Route objects not announced

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