bgpreport

Network · data from 2026-11-12

AS271138 AS271138 - GR FAST NET TELECOMUNICACOES

Registry name: AS271138 - GR FAST NET TELECOMUNICACOES, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271138, 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:76d8::/33 No ROA Nonecovered by 2804:76d8::/32 99 16% 40
2804:76d8:8000::/33 No ROA Nonecovered by 2804:76d8::/32 99 16% 40
187.86.196.0/22 No ROA Other IRR onlyRADB, TC 672 100% 66
187.86.196.0/23 No ROA Other IRR onlyRADB 672 100% 66
187.86.198.0/23 No ROA Other IRR onlyRADB 672 100% 66
2804:76d8::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS271138 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: none6
  • Route object: none2
  • Route object: RIR4
ChangePrefix or setDetailFull-table peers
ROA: none2804:76d8::/33No ROA covers it. Add a ROA for AS271138, maxLength 33.99 of 636
Route object: none2804:76d8::/33No route object for it. A route object for 2804:76d8::/32 with origin AS271138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271138 in the RIR database for the space.99 of 636
ROA: none2804:76d8:8000::/33No ROA covers it. Add a ROA for AS271138, maxLength 33.99 of 636
Route object: none2804:76d8:8000::/33No route object for it. A route object for 2804:76d8::/32 with origin AS271138 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271138 in the RIR database for the space.99 of 636
ROA: none187.86.196.0/22No ROA covers it. Add a ROA for AS271138, maxLength 22.672 of 673
Route object: RIR187.86.196.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none187.86.196.0/23No ROA covers it. Add a ROA for AS271138, maxLength 23.672 of 673
Route object: RIR187.86.196.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none187.86.198.0/23No ROA covers it. Add a ROA for AS271138, maxLength 23.672 of 673
Route object: RIR187.86.198.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none2804:76d8::/32No ROA covers it. Add a ROA for AS271138, maxLength 32.634 of 636
Route object: RIR2804:76d8::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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