bgpreport

Network · data from 2026-11-12

AS204528 spacecom Space-Communication ltd.

Registry name: spacecom Space-Communication ltd., IL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS204528, 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.
154.56.98.0/23 No ROA Other IRR onlyRADB 670 100% 67
38.22.120.0/24 Valid RIR databaseARIN 672 100% 67
38.126.14.0/24 Valid RIR databaseARIN 672 100% 67
81.199.62.0/24 Valid RIR databaseRIPE 672 100% 67
81.199.97.0/24 Valid RIR databaseRIPE 672 100% 66
81.199.3.0/24 Valid RIR databaseRIPE 671 100% 67
81.199.4.0/24 Valid RIR databaseRIPE 671 100% 67
81.199.15.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
81.199.20.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
81.199.201.0/24 Valid RIR databaseRADB, RIPE 669 99% 67

AS-SET

AS204528 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 4 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none154.56.98.0/23No ROA covers it. Add a ROA for AS204528, maxLength 23.670 of 673
Route object: RIR154.56.98.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

62.56.156.0/24RIPEValid
81.199.94.0/24RIPEValid

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.