bgpreport

Network · data from 2026-11-12

AS270744 AS270744 - Forte Telecom Servicos de Comunicacao Multimidia E

Registry name: AS270744 - Forte Telecom Servicos de Comunicacao Multimidia E, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270744, 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.99.230.0/24 No ROA Other IRR onlyRADB, TC 670 100% 66
138.99.231.0/24 No ROA Other IRR onlyRADB, TC 669 99% 66
138.99.228.0/23 No ROA Other IRR onlyRADB, TC 667 99% 66
2804:70b8::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:70b8::/33 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:70b8:8000::/33 No ROA Other IRR onlyRADB, TC 635 100% 67

AS-SET

AS270744 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 16 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none138.99.230.0/24No ROA covers it. Add a ROA for AS270744, maxLength 24.670 of 673
Route object: RIR138.99.230.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
ROA: none138.99.231.0/24No ROA covers it. Add a ROA for AS270744, maxLength 24.669 of 673
Route object: RIR138.99.231.0/24Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none138.99.228.0/23No ROA covers it. Add a ROA for AS270744, maxLength 23.667 of 673
Route object: RIR138.99.228.0/23Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
ROA: none2804:70b8::/32No ROA covers it. Add a ROA for AS270744, maxLength 32.635 of 636
Route object: RIR2804:70b8::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:70b8::/33No ROA covers it. Add a ROA for AS270744, maxLength 33.635 of 636
Route object: RIR2804:70b8::/33Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:70b8:8000::/33No ROA covers it. Add a ROA for AS270744, maxLength 33.635 of 636
Route object: RIR2804:70b8:8000::/33Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

138.99.228.0/22RADB, TCNo ROA
138.99.228.0/24RADB, TCNo ROA
138.99.229.0/24RADB, TCNo ROA
138.99.230.0/23TCNo 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.