bgpreport

Network · data from 2026-11-12

AS267214 CLICKPLAY PROVEDOR DE ACESSO

Registry name: AS267214 - CLICKPLAY PROVEDOR DE ACESSO LTDA - ME, BR · PeeringDB

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

Announced routes

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

45.230.160.0/22 No ROA Other IRR onlyRADB, TC 666 99% 67
45.230.160.0/23 No ROA Other IRR onlyRADB, TC 666 99% 67
45.230.162.0/23 No ROA Other IRR onlyRADB, TC 666 99% 67
2804:4a08::/32 No ROA Other IRR onlyRADB, TC 628 99% 67
2804:4a08::/33 No ROA Other IRR onlyTC 628 99% 67
2804:4a08:8000::/33 No ROA Other IRR onlyTC 628 99% 67
2804:4a08::/34 No ROA Other IRR onlyTC 350 55% 64
2804:4a08:4000::/34 No ROA Other IRR onlyTC 350 55% 64
2804:4a08:8000::/34 No ROA Other IRR onlyTC 350 55% 64
2804:4a08:c000::/34 No ROA Other IRR onlyTC 350 55% 64
45.230.160.0/24 No ROA Other IRR onlyRADB, TC 74 11% 39
45.230.161.0/24 No ROA Other IRR onlyRADB, TC 74 11% 39
45.230.162.0/24 No ROA Other IRR onlyRADB, TC 74 11% 39
45.230.163.0/24 No ROA Other IRR onlyRADB, TC 74 11% 39

AS-SET

PeeringDB's irr_as_set for AS267214: AS267214:AS-ANNOUNCEMENTS. 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 (AS267214 isn't in the set, or no route object for AS267214 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 objectsAS267214 in itNot covered
AS267214:AS-ANNOUNCEMENTS TC 1214 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 28 are in fix.csv.

  • ROA: none14
  • Route object: RIR14
ChangePrefix or setDetailFull-table peers
ROA: none45.230.160.0/22No ROA covers it. Add a ROA for AS267214, maxLength 22.666 of 673
Route object: RIR45.230.160.0/22Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none45.230.160.0/23No ROA covers it. Add a ROA for AS267214, maxLength 23.666 of 673
Route object: RIR45.230.160.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none45.230.162.0/23No ROA covers it. Add a ROA for AS267214, maxLength 23.666 of 673
Route object: RIR45.230.162.0/23Route object only in RADB, TC. Add it in the RIR database for the space.666 of 673
ROA: none2804:4a08::/32No ROA covers it. Add a ROA for AS267214, maxLength 32.628 of 636
Route object: RIR2804:4a08::/32Route object only in RADB, TC. Add it in the RIR database for the space.628 of 636
ROA: none2804:4a08::/33No ROA covers it. Add a ROA for AS267214, maxLength 33.628 of 636
Route object: RIR2804:4a08::/33Route object only in TC. Add it in the RIR database for the space.628 of 636
ROA: none2804:4a08:8000::/33No ROA covers it. Add a ROA for AS267214, maxLength 33.628 of 636
Route object: RIR2804:4a08:8000::/33Route object only in TC. Add it in the RIR database for the space.628 of 636
ROA: none2804:4a08::/34No ROA covers it. Add a ROA for AS267214, maxLength 34.350 of 636
Route object: RIR2804:4a08::/34Route object only in TC. Add it in the RIR database for the space.350 of 636
ROA: none2804:4a08:4000::/34No ROA covers it. Add a ROA for AS267214, maxLength 34.350 of 636
Route object: RIR2804:4a08:4000::/34Route object only in TC. Add it in the RIR database for the space.350 of 636
ROA: none2804:4a08:8000::/34No ROA covers it. Add a ROA for AS267214, maxLength 34.350 of 636
Route object: RIR2804:4a08:8000::/34Route object only in TC. Add it in the RIR database for the space.350 of 636
ROA: none2804:4a08:c000::/34No ROA covers it. Add a ROA for AS267214, maxLength 34.350 of 636
Route object: RIR2804:4a08:c000::/34Route object only in TC. Add it in the RIR database for the space.350 of 636
ROA: none45.230.160.0/24No ROA covers it. Add a ROA for AS267214, maxLength 24.74 of 673
Route object: RIR45.230.160.0/24Route object only in RADB, TC. Add it in the RIR database for the space.74 of 673
ROA: none45.230.161.0/24No ROA covers it. Add a ROA for AS267214, maxLength 24.74 of 673
Route object: RIR45.230.161.0/24Route object only in RADB, TC. Add it in the RIR database for the space.74 of 673
ROA: none45.230.162.0/24No ROA covers it. Add a ROA for AS267214, maxLength 24.74 of 673
Route object: RIR45.230.162.0/24Route object only in RADB, TC. Add it in the RIR database for the space.74 of 673
ROA: none45.230.163.0/24No ROA covers it. Add a ROA for AS267214, maxLength 24.74 of 673
Route object: RIR45.230.163.0/24Route object only in RADB, TC. Add it in the RIR database for the space.74 of 673

Route objects not announced

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