bgpreport

Network · data from 2026-11-12

AS270286 AS270286 - CONECT ISP - SERVICOS DE COMUNICACAO MULTIMID LTDA

Registry name: AS270286 - CONECT ISP - SERVICOS DE COMUNICACAO MULTIMID LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270286, 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.
201.71.20.0/23 No ROA Other origin onlycovered by 201.71.20.0/22 671 100% 67
2804:69b4:7800::/38 No ROA Nonecovered by 2804:69b4::/32 2 0%low visibility 2
201.71.22.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 66
201.71.23.0/24 No ROA Other IRR onlyRADB 667 99% 67
2804:69b4::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS270286 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: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none201.71.20.0/23No ROA covers it. Add a ROA for AS270286, maxLength 23.671 of 673
Route object: none201.71.20.0/23Route objects for it name AS262907. A route object for 201.71.20.0/22 with origin AS270286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270286 in the RIR database for the space.671 of 673
ROA: none2804:69b4:7800::/38No ROA covers it. Add a ROA for AS270286, maxLength 38.2 of 636
Route object: none2804:69b4:7800::/38No route object for it. A route object for 2804:69b4::/32 with origin AS270286 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270286 in the RIR database for the space.2 of 636
ROA: none201.71.22.0/24No ROA covers it. Add a ROA for AS270286, maxLength 24.671 of 673
Route object: RIR201.71.22.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none201.71.23.0/24No ROA covers it. Add a ROA for AS270286, maxLength 24.667 of 673
Route object: RIR201.71.23.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:69b4::/32No ROA covers it. Add a ROA for AS270286, maxLength 32.634 of 636
Route object: RIR2804:69b4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

201.71.20.0/22RADB, TCNo ROA
201.71.20.0/24RADBNo 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.