bgpreport

Network · data from 2026-11-12

AS271761 CLICK FIBRA TELECOMUNICACOES

Registry name: AS271761 - CLICK FIBRA TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271761, 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.

206.0.90.0/24 No ROA Nonecovered by 206.0.90.0/23 24 4%low visibility 11
206.0.91.0/24 No ROA Nonecovered by 206.0.90.0/23 24 4%low visibility 11
206.0.90.0/23 No ROA Other IRR onlyRADB 672 100% 66
131.255.104.0/24 Valid Nonecovered by 131.255.104.0/23 24 4%low visibility 11
131.255.105.0/24 Valid Nonecovered by 131.255.104.0/23 24 4%low visibility 11
131.255.106.0/24 Valid Nonecovered by 131.255.106.0/23 24 4%low visibility 11
131.255.107.0/24 Valid Nonecovered by 131.255.106.0/23 24 4%low visibility 11
131.255.104.0/22 Valid Other IRR onlyTC 672 100% 66
2804:8098::/32 Valid Other IRR onlyTC 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS271761: TC::AS271761:AS-CUSTOMERS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS271761 isn't in the set, or no route object for AS271761 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS271761 in itNot covered
TC::AS271761:AS-CUSTOMERS TC 117 Yes 0

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: none3
  • Route object: none6
  • Route object: RIR3
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none206.0.90.0/24No ROA covers it. Add a ROA for AS271761, maxLength 24.24 of 673
Route object: none206.0.90.0/24No route object for it. A route object for 206.0.90.0/23 with origin AS271761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271761 in the RIR database for the space.24 of 673
ROA: none206.0.91.0/24No ROA covers it. Add a ROA for AS271761, maxLength 24.24 of 673
Route object: none206.0.91.0/24No route object for it. A route object for 206.0.90.0/23 with origin AS271761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271761 in the RIR database for the space.24 of 673
ROA: none206.0.90.0/23No ROA covers it. Add a ROA for AS271761, maxLength 23.672 of 673
Route object: RIR206.0.90.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none131.255.104.0/24No route object for it. A route object for 131.255.104.0/23 with origin AS271761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271761 in the RIR database for the space.24 of 673
Route object: none131.255.105.0/24No route object for it. A route object for 131.255.104.0/23 with origin AS271761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271761 in the RIR database for the space.24 of 673
Route object: none131.255.106.0/24No route object for it. A route object for 131.255.106.0/23 with origin AS271761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271761 in the RIR database for the space.24 of 673
Route object: none131.255.107.0/24No route object for it. A route object for 131.255.106.0/23 with origin AS271761 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271761 in the RIR database for the space.24 of 673
Route object: RIR131.255.104.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:8098::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

131.255.104.0/23TCValid
131.255.106.0/23TCValid
2804:8098::/33TCValid
2804:8098:8000::/33TCValid

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.