bgpreport

Network · data from 2026-11-12

AS266203 AS266203 - CLICK INTERNET LTDA ME

Registry name: AS266203 - CLICK INTERNET LTDA ME, BR · not in PeeringDB

7IPv4 routes 100.0% RPKI valid · 100.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 1 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS266203, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS266203, 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:3c50::/33 Valid Nonecovered by 2804:3c50::/32 2 0%low visibility 2
192.140.52.0/22 Valid Other IRR onlyALTDB, RADB, TC 670 100% 67
192.140.52.0/23 Valid Other IRR onlyALTDB, RADB, TC 670 100% 67
192.140.54.0/23 Valid Other IRR onlyALTDB, RADB, TC 670 100% 67
2804:3c50::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 69
192.140.52.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
192.140.53.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
192.140.54.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3
192.140.55.0/24 Valid Other IRR onlyALTDB, RADB 3 0%low visibility 3

AS-SET

AS266203 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 9 are in fix.csv.

  • Route object: none1
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
Route object: none2804:3c50::/33No route object for it. A route object for 2804:3c50::/32 with origin AS266203 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266203 in the RIR database for the space.2 of 636
Route object: RIR192.140.52.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR192.140.52.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR192.140.54.0/23Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR2804:3c50::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR192.140.52.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR192.140.53.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR192.140.54.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673
Route object: RIR192.140.55.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.3 of 673

Route objects not announced

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