bgpreport

Network · data from 2026-11-12

AS263385 CSNET TELECOM LTDA

Registry name: AS263385 - CSNET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263385, 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.87.124.0/22 No ROA Other IRR onlyRADB 672 100% 66
177.87.126.0/24 No ROA Other IRR onlyRADB 672 100% 66
177.87.124.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.87.125.0/24 No ROA Other IRR onlyRADB 671 100% 66
177.87.127.0/24 No ROA Other IRR onlyRADB 671 100% 66
2804:1558::/32 No ROA Other IRR onlyRADB 635 100% 67
2804:1558:2000::/36 No ROA Other IRR onlyRADB 635 100% 67

AS-SET

AS263385's PeeringDB record names no 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 20 are in fix.csv.

  • ROA: none7
  • Route object: RIR7
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none177.87.124.0/22No ROA covers it. Add a ROA for AS263385, maxLength 22.672 of 673
Route object: RIR177.87.124.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.87.126.0/24No ROA covers it. Add a ROA for AS263385, maxLength 24.672 of 673
Route object: RIR177.87.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.87.124.0/24No ROA covers it. Add a ROA for AS263385, maxLength 24.671 of 673
Route object: RIR177.87.124.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.87.125.0/24No ROA covers it. Add a ROA for AS263385, maxLength 24.671 of 673
Route object: RIR177.87.125.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.87.127.0/24No ROA covers it. Add a ROA for AS263385, maxLength 24.671 of 673
Route object: RIR177.87.127.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:1558::/32No ROA covers it. Add a ROA for AS263385, maxLength 32.635 of 636
Route object: RIR2804:1558::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:1558:2000::/36No ROA covers it. Add a ROA for AS263385, maxLength 36.635 of 636
Route object: RIR2804:1558:2000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

177.87.124.0/23RADBNo ROA
177.87.126.0/23RADBNo ROA
2804:1558::/33RADBNo ROA
2804:1558:4::/48RADBNo ROA
2804:1558:4000::/36RADBNo ROA
2804:1558:8000::/33RADBNo 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.