bgpreport

Network · data from 2026-11-12

AS264229 GLOBAL FLASH TELECOM E TECNOLOGIA LTDA - ME

Registry name: AS264229 - GLOBAL FLASH TELECOM E TECNOLOGIA LTDA - ME, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264229, 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.117.55.0/24 Valid Nonecovered by 138.117.54.0/23 665 99% 67
2804:248c:c000::/34 Valid Nonecovered by 2804:248c::/32 635 100% 67
138.117.52.0/24 Valid Other IRR onlyRADB 671 100% 67
138.117.53.0/24 Valid Other IRR onlyRADB 671 100% 67
138.117.54.0/24 Valid Other IRR onlyRADB 671 100% 67
2804:248c::/32 Valid Other IRR onlyRADB, TC 2 0%low visibility 2

AS-SET

AS264229'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.

  • Route object: none2
  • Route object: RIR4
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none138.117.55.0/24No route object for it. A route object for 138.117.54.0/23 with origin AS264229 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264229 in the RIR database for the space.665 of 673
Route object: none2804:248c:c000::/34No route object for it. A route object for 2804:248c::/32 with origin AS264229 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264229 in the RIR database for the space.635 of 636
Route object: RIR138.117.52.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.53.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR138.117.54.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:248c::/32Route object only in RADB, TC. Add it in the RIR database for the space.2 of 636

Route objects not announced

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

138.117.52.0/22RADB, TCNo ROA
138.117.52.0/23RADBNo ROA
138.117.54.0/23RADBNo ROA
2804:248c:4000::/34RADBValid
2804:248c:8000::/34RADBValid

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.