bgpreport

Network · data from 2026-11-12

AS265320 SATLINK TELECOM

Registry name: AS265320 - SATLINK TELECOM LTDA, BR · PeeringDB

2IPv4 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
3No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS265320, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS265320, 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.121.104.0/22 No ROA Other IRR onlyRADB, TC 669 99% 67
168.121.104.0/23 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:2e10::/32 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

AS265320'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 18 are in fix.csv.

  • ROA: none3
  • Route object: RIR3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none168.121.104.0/22No ROA covers it. Add a ROA for AS265320, maxLength 22.669 of 673
Route object: RIR168.121.104.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none168.121.104.0/23No ROA covers it. Add a ROA for AS265320, maxLength 23.669 of 673
Route object: RIR168.121.104.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:2e10::/32No ROA covers it. Add a ROA for AS265320, maxLength 32.635 of 636
Route object: RIR2804:2e10::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

168.121.104.0/24RADB, TCNo ROA
168.121.105.0/24RADB, TCNo ROA
168.121.106.0/23RADB, TCNo ROA
168.121.106.0/24ALTDB, RADB, TCNo ROA
168.121.106.0/27TCNo ROA
168.121.107.0/24RADBNo ROA
2804:2e10::/33TCNo ROA
2804:2e10::/34TCNo ROA
2804:2e10:4000::/34TCNo ROA
2804:2e10:8000::/33TCNo ROA
2804:2e10:8000::/34TCNo ROA
2804:2e10:c000::/34TCNo 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.