bgpreport

Network · data from 2026-11-12

AS265430 AS265430 - JDA Net - SKYNET Teleinformatica

Registry name: AS265430 - JDA Net - SKYNET Teleinformatica, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265430, 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.
168.195.88.0/23 No ROA Nonecovered by 168.195.88.0/22 666 99% 66
168.195.90.0/24 No ROA Nonecovered by 168.195.88.0/22 660 98% 66
2804:3400::/33 No ROA Nonecovered by 2804:3400::/32 631 99% 67
2804:3400:8000::/34 No ROA Other IRR onlyRADB 627 99% 67
168.195.91.0/24 No ROA Other IRR onlyRADB 5 1%low visibility 4

AS-SET

AS265430 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: none3
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none168.195.88.0/23No ROA covers it. Add a ROA for AS265430, maxLength 23.666 of 673
Route object: none168.195.88.0/23No route object for it. A route object for 168.195.88.0/22 with origin AS265430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265430 in the RIR database for the space.666 of 673
ROA: none168.195.90.0/24No ROA covers it. Add a ROA for AS265430, maxLength 24.660 of 673
Route object: none168.195.90.0/24No route object for it. A route object for 168.195.88.0/22 with origin AS265430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265430 in the RIR database for the space.660 of 673
ROA: none2804:3400::/33No ROA covers it. Add a ROA for AS265430, maxLength 33.631 of 636
Route object: none2804:3400::/33No route object for it. A route object for 2804:3400::/32 with origin AS265430 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265430 in the RIR database for the space.631 of 636
ROA: none2804:3400:8000::/34No ROA covers it. Add a ROA for AS265430, maxLength 34.627 of 636
Route object: RIR2804:3400:8000::/34Route object only in RADB. Add it in the RIR database for the space.627 of 636
ROA: none168.195.91.0/24No ROA covers it. Add a ROA for AS265430, maxLength 24.5 of 673
Route object: RIR168.195.91.0/24Route object only in RADB. Add it in the RIR database for the space.5 of 673

Route objects not announced

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

168.195.88.0/22RADBNo ROA
2804:3400::/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.