bgpreport

Network · data from 2026-11-12

AS19036 LORAL-CYBERSTAR - Telesat Network Services Inc

Registry name: LORAL-CYBERSTAR - Telesat Network Services Inc, US · not in PeeringDB

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

Announced routes

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

192.137.158.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 67
24.142.96.0/19 No ROA Other IRR onlyNTTCOM 672 100% 67
209.221.224.0/20 No ROA Other IRR onlyNTTCOM 672 100% 67
209.239.64.0/19 No ROA Other IRR onlyNTTCOM 672 100% 67

AS-SET

AS19036 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 188 are in fix.csv.

  • ROA: none4
  • Route object: RIR4
  • Route object: not announced180
ChangePrefix or setDetailFull-table peers
ROA: none192.137.158.0/24No ROA covers it. Add a ROA for AS19036, maxLength 24.673 of 673
Route object: RIR192.137.158.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none24.142.96.0/19No ROA covers it. Add a ROA for AS19036, maxLength 19.672 of 673
Route object: RIR24.142.96.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none209.221.224.0/20No ROA covers it. Add a ROA for AS19036, maxLength 20.672 of 673
Route object: RIR209.221.224.0/20Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none209.239.64.0/19No ROA covers it. Add a ROA for AS19036, maxLength 19.672 of 673
Route object: RIR209.239.64.0/19Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

24.142.96.0/20NTTCOMNo ROA
24.142.96.0/21NTTCOMNo ROA
24.142.96.0/22NTTCOMNo ROA
24.142.96.0/23NTTCOMNo ROA
24.142.96.0/24NTTCOMNo ROA
24.142.97.0/24NTTCOMNo ROA
24.142.98.0/23NTTCOMNo ROA
24.142.98.0/24NTTCOMNo ROA
24.142.99.0/24NTTCOMNo ROA
24.142.100.0/22NTTCOMNo ROA
24.142.100.0/23NTTCOMNo ROA
24.142.100.0/24NTTCOMNo ROA
24.142.101.0/24NTTCOMNo ROA
24.142.102.0/23NTTCOMNo ROA
24.142.102.0/24NTTCOMNo ROA
24.142.103.0/24NTTCOMNo ROA
24.142.104.0/21NTTCOMNo ROA
24.142.104.0/22NTTCOMNo ROA
24.142.104.0/23NTTCOMNo ROA
24.142.104.0/24NTTCOMNo ROA
24.142.105.0/24NTTCOMNo ROA
24.142.106.0/23NTTCOMNo ROA
24.142.106.0/24NTTCOMNo ROA
24.142.107.0/24NTTCOMNo ROA
24.142.108.0/22NTTCOMNo ROA
24.142.108.0/23NTTCOMNo ROA
24.142.108.0/24NTTCOMNo ROA
24.142.109.0/24NTTCOMNo ROA
24.142.110.0/23NTTCOMNo ROA
24.142.110.0/24NTTCOMNo ROA
24.142.111.0/24NTTCOMNo ROA
24.142.112.0/20NTTCOMNo ROA
24.142.112.0/21NTTCOMNo ROA
24.142.112.0/22NTTCOMNo ROA
24.142.112.0/23NTTCOMNo ROA
24.142.112.0/24NTTCOMNo ROA
24.142.113.0/24NTTCOMNo ROA
24.142.114.0/23NTTCOMNo ROA
24.142.114.0/24NTTCOMNo ROA
24.142.115.0/24NTTCOMNo ROA
24.142.116.0/22NTTCOMNo ROA
24.142.116.0/23NTTCOMNo ROA
24.142.116.0/24NTTCOMNo ROA
24.142.117.0/24NTTCOMNo ROA
24.142.118.0/23NTTCOMNo ROA
24.142.118.0/24NTTCOMNo ROA
24.142.119.0/24NTTCOMNo ROA
24.142.120.0/21NTTCOMNo ROA
24.142.120.0/22NTTCOMNo ROA
24.142.120.0/23NTTCOMNo ROA
24.142.120.0/24NTTCOMNo ROA
24.142.121.0/24NTTCOMNo ROA
24.142.122.0/23NTTCOMNo ROA
24.142.122.0/24NTTCOMNo ROA
24.142.123.0/24NTTCOMNo ROA
24.142.124.0/22NTTCOMNo ROA
24.142.124.0/23NTTCOMNo ROA
24.142.124.0/24NTTCOMNo ROA
24.142.125.0/24NTTCOMNo ROA
24.142.126.0/23NTTCOMNo ROA
24.142.126.0/24NTTCOMNo ROA
24.142.127.0/24NTTCOMNo ROA
68.67.0.0/20NTTCOMNo ROA
68.67.0.0/21NTTCOMNo ROA
68.67.4.0/22NTTCOMNo ROA
68.67.4.0/23NTTCOMNo ROA
68.67.4.0/24NTTCOMNo ROA
68.67.5.0/24NTTCOMNo ROA
68.67.6.0/23NTTCOMNo ROA
68.67.6.0/24NTTCOMNo ROA
68.67.7.0/24NTTCOMNo ROA
68.67.8.0/21NTTCOMNo ROA
68.67.8.0/22NTTCOMNo ROA
68.67.8.0/23NTTCOMNo ROA
68.67.8.0/24NTTCOMNo ROA
68.67.9.0/24NTTCOMNo ROA
68.67.10.0/23NTTCOMNo ROA
68.67.10.0/24NTTCOMNo ROA
68.67.11.0/24NTTCOMNo ROA
68.67.12.0/22NTTCOMNo ROA
68.67.12.0/23NTTCOMNo ROA
68.67.12.0/24NTTCOMNo ROA
68.67.13.0/24NTTCOMNo ROA
68.67.14.0/23NTTCOMNo ROA
68.67.14.0/24NTTCOMNo ROA
68.67.15.0/24NTTCOMNo ROA
173.243.96.0/21NTTCOMNo ROA
173.243.104.0/23NTTCOMNo ROA
209.221.224.0/21NTTCOMNo ROA
209.221.224.0/22NTTCOMNo ROA
209.221.224.0/23NTTCOMNo ROA
209.221.224.0/24NTTCOMNo ROA
209.221.225.0/24NTTCOMNo ROA
209.221.226.0/23NTTCOMNo ROA
209.221.226.0/24NTTCOMNo ROA
209.221.227.0/24NTTCOMNo ROA
209.221.228.0/22NTTCOMNo ROA
209.221.228.0/23NTTCOMNo ROA
209.221.228.0/24NTTCOMNo ROA
209.221.229.0/24NTTCOMNo ROA
209.221.230.0/23NTTCOMNo ROA
209.221.230.0/24NTTCOMNo ROA
209.221.231.0/24NTTCOMNo ROA
209.221.232.0/21NTTCOMNo ROA
209.221.232.0/22NTTCOMNo ROA
209.221.232.0/23NTTCOMNo ROA
209.221.232.0/24NTTCOMNo ROA
209.221.233.0/24NTTCOMNo ROA
209.221.234.0/23NTTCOMNo ROA
209.221.234.0/24NTTCOMNo ROA
209.221.235.0/24NTTCOMNo ROA
209.221.236.0/22NTTCOMNo ROA
209.221.236.0/23NTTCOMNo ROA
209.221.236.0/24NTTCOMNo ROA
209.221.237.0/24NTTCOMNo ROA
209.221.238.0/23NTTCOMNo ROA
209.221.238.0/24NTTCOMNo ROA
209.221.239.0/24NTTCOMNo ROA
209.239.64.0/20NTTCOMNo ROA
209.239.64.0/21NTTCOMNo ROA
209.239.64.0/22NTTCOMNo ROA
209.239.64.0/23NTTCOMNo ROA
209.239.64.0/24NTTCOMNo ROA
209.239.65.0/24NTTCOMNo ROA
209.239.66.0/23NTTCOMNo ROA
209.239.66.0/24NTTCOMNo ROA
209.239.67.0/24NTTCOMNo ROA
209.239.68.0/22NTTCOMNo ROA
209.239.68.0/23NTTCOMNo ROA
209.239.68.0/24NTTCOMNo ROA
209.239.69.0/24NTTCOMNo ROA
209.239.70.0/23NTTCOMNo ROA
209.239.70.0/24NTTCOMNo ROA
209.239.71.0/24NTTCOMNo ROA
209.239.72.0/21NTTCOMNo ROA
209.239.72.0/22NTTCOMNo ROA
209.239.72.0/23NTTCOMNo ROA
209.239.72.0/24NTTCOMNo ROA
209.239.73.0/24NTTCOMNo ROA
209.239.74.0/23NTTCOMNo ROA
209.239.74.0/24NTTCOMNo ROA
209.239.75.0/24NTTCOMNo ROA
209.239.76.0/22NTTCOMNo ROA
209.239.76.0/23NTTCOMNo ROA
209.239.76.0/24NTTCOMNo ROA
209.239.77.0/24NTTCOMNo ROA
209.239.78.0/23NTTCOMNo ROA
209.239.78.0/24NTTCOMNo ROA
209.239.79.0/24NTTCOMNo ROA
209.239.80.0/20NTTCOMNo ROA
209.239.80.0/21NTTCOMNo ROA
209.239.80.0/22NTTCOMNo ROA
209.239.80.0/23NTTCOMNo ROA
209.239.80.0/24NTTCOMNo ROA
209.239.81.0/24NTTCOMNo ROA
209.239.82.0/23NTTCOMNo ROA
209.239.82.0/24NTTCOMNo ROA
209.239.83.0/24NTTCOMNo ROA
209.239.84.0/22NTTCOMNo ROA
209.239.84.0/23NTTCOMNo ROA
209.239.84.0/24NTTCOMNo ROA
209.239.85.0/24NTTCOMNo ROA
209.239.86.0/23NTTCOMNo ROA
209.239.86.0/24NTTCOMNo ROA
209.239.87.0/24NTTCOMNo ROA
209.239.88.0/21NTTCOMNo ROA
209.239.88.0/22NTTCOMNo ROA
209.239.88.0/23NTTCOMNo ROA
209.239.88.0/24NTTCOMNo ROA
209.239.89.0/24NTTCOMNo ROA
209.239.90.0/23NTTCOMNo ROA
209.239.90.0/24NTTCOMNo ROA
209.239.91.0/24NTTCOMNo ROA
209.239.92.0/22NTTCOMNo ROA
209.239.92.0/23NTTCOMNo ROA
209.239.92.0/24NTTCOMNo ROA
209.239.93.0/24NTTCOMNo ROA
209.239.94.0/23NTTCOMNo ROA
209.239.94.0/24NTTCOMNo ROA
209.239.95.0/24NTTCOMNo 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.