Starlink has bufferbloat. Bad.
 help / color / mirror / Atom feed
From: Sascha Meinrath <sascha@thexlab.org>
Cc: starlink@lists.bufferbloat.net
Subject: [Starlink] Why Data Centers In Space Won't Work [Yet] (A non-canonical list).
Date: Fri, 27 Feb 2026 09:26:52 -0500	[thread overview]
Message-ID: <3e2d9c26-f468-4380-8c88-a76679248a16@thexlab.org> (raw)
In-Reply-To: <53546r56-154r-o38n-1ns2-8ponps4ss1o5@ynat.uz>

Hi everyone,

Synthesizing from what we know thus far, I think it would be helpful to have a 
topline bullet list of the major issues detrimentally impacting the viability of 
data centers in space.

I remain highly skeptical of the concept, given today's technological realities, 
and feel that there would be utility in having a quick reference of the major 
shortcomings that need to be overcome.

Here's a starting point for some of the major limitations to data centers in 
space (please add, though keep bullets pithy):

1. Thermal cooling/heat dissipation
2. Radiation hardening
3. Launch costs
4. Upgrade/maintenance costs
5. Kessler syndrome/ablation cascade risks (& collision avoidance)
6. Power generation/storage
7. Latency/bandwidth
8. Risk-adjusted ROI
9. ???
.
.
.

--Sascha

-- 
Sascha Meinrath
Director, X-Lab
Palmer Chair in Telecommunications
Penn State University


  reply	other threads:[~2026-02-27 14:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-25 14:05 [Starlink] Data centers are racing to space — and regulation can’t keep up Hesham ElBakoury
2026-02-25 14:30 ` [Starlink] " David Collier-Brown
2026-02-25 14:32   ` [Starlink] Re: Data centers are racing to space ??? and regulation can???t " Gert Doering
2026-02-25 14:42   ` [Starlink] Re: Data centers are racing to space — and regulation can’t " Hesham ElBakoury
2026-02-26  4:28     ` J Pan
     [not found]       ` <CAFvDQ9p68AFJ5cQTpyx=HkA2Cf6r1m6F3ssaJh-OJK4kqK=PDQ@mail.gmail.com>
2026-02-26  5:54         ` J Pan
2026-02-26  6:01           ` Hesham ElBakoury
2026-02-25 14:50   ` Daniel AJ Sokolov
2026-02-26  1:33     ` David Lang
2026-02-26  2:38       ` Nick Matthews
2026-02-26  4:39         ` David Lang
2026-02-26 11:54           ` Mark Handley
2026-02-26 13:36             ` Vint Cerf
2026-02-26 13:56               ` Nitinder Mohan
2026-02-26 21:36                 ` Ulrich Speidel
2026-02-26 23:02                   ` Brandon Butterworth
2026-02-26 23:16                     ` Nitinder Mohan
2026-02-26 23:44                       ` Ulrich Speidel
2026-02-27  1:01                         ` Joe Hamelin
2026-02-27  1:47                           ` David Lang
2026-02-27 14:26                             ` Sascha Meinrath [this message]
2026-02-27 15:07                               ` [Starlink] Re: Why Data Centers In Space Won't Work [Yet] (A non-canonical list) David Lang
2026-02-27 15:15                               ` Daniel AJ Sokolov
2026-02-27 15:22                                 ` Gert Doering
2026-02-26 14:14               ` [Starlink] Re: Data centers are racing to space — and regulation can’t keep up Mark Handley
2026-02-26 18:01             ` David Lang
2026-02-25 20:26   ` Brandon Butterworth
2026-02-26  1:28   ` David Lang
2026-02-26  4:49 ` David Lang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3e2d9c26-f468-4380-8c88-a76679248a16@thexlab.org \
    --to=sascha@thexlab.org \
    --cc=starlink@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox