bgpreport

Network · data from 2026-11-12

AS54238 SATCOM-DIRECT-INC - Satcom Direct Inc.

Registry name: SATCOM-DIRECT-INC - Satcom Direct Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS54238, 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.
164.153.28.0/24 Invalid: maxLength Nonecovered by 164.153.28.0/22 56 8%low visibility 31
164.153.29.0/24 Invalid: maxLength Nonecovered by 164.153.28.0/22 56 8%low visibility 31
89.255.208.0/21 Valid Other IRR onlyRADB 673 100% 67
209.151.220.0/22 Valid Other IRR onlyRADB 673 100% 67
216.213.108.0/22 Valid Other IRR onlyRADB 673 100% 67
216.213.104.0/22 Valid Other IRR onlyRADB 669 99% 67
164.153.28.0/22 Valid RIR databaseAPNIC 669 99% 67

AS-SET

AS54238 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 11 are in fix.csv.

  • ROA: maxLength2
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: maxLength164.153.28.0/24ROA 164.153.28.0/22 AS54238 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 164.153.28.0/24.56 of 673
Route object: none164.153.28.0/24No route object for it. A route object for 164.153.28.0/22 with origin AS54238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54238 in the RIR database for the space.56 of 673
ROA: maxLength164.153.29.0/24ROA 164.153.28.0/22 AS54238 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 164.153.29.0/24.56 of 673
Route object: none164.153.29.0/24No route object for it. A route object for 164.153.28.0/22 with origin AS54238 covers it (filters allowing more-specifics accept it). Add a route object with origin AS54238 in the RIR database for the space.56 of 673
Route object: RIR89.255.208.0/21Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR209.151.220.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.213.108.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR216.213.104.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

89.255.212.0/22RIPEValid
89.255.215.0/24RADBValid
209.151.221.0/24RADBValid

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.