bgpreport

Network · data from 2026-11-12

AS262597 AS262597 - CONTINUY SERVICOS EM TECNOLOGIA DA INFORMACAO LTDA

Registry name: AS262597 - CONTINUY SERVICOS EM TECNOLOGIA DA INFORMACAO LTDA, BR · not in PeeringDB

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

Announced routes

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

177.85.32.0/21 No ROA Other IRR onlyRADB 670 100% 67
177.85.32.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.33.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.34.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.35.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.36.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.37.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.38.0/24 No ROA Other IRR onlyRADB 670 100% 67
177.85.39.0/24 No ROA Other IRR onlyRADB 670 100% 67
2804:6a0:100::/40 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS262597 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 24 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none177.85.32.0/21No ROA covers it. Add a ROA for AS262597, maxLength 21.670 of 673
Route object: RIR177.85.32.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.32.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.32.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.33.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.33.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.34.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.34.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.35.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.35.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.36.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.36.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.37.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.37.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.38.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.38.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none177.85.39.0/24No ROA covers it. Add a ROA for AS262597, maxLength 24.670 of 673
Route object: RIR177.85.39.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2804:6a0:100::/40No ROA covers it. Add a ROA for AS262597, maxLength 40.636 of 636
Route object: RIR2804:6a0:100::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

177.85.32.0/22RADBNo ROA
177.85.32.0/23RADBNo ROA
177.85.34.0/23RADBNo ROA
2804:6a0::/32RADBNo 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.