A few years ago when I was in the WAN optimisation space, IIRC Sydney/Singapore latency was ~150ms, partly raw distance, partly because the route was physically quite convoluted.
There's some expectation that once Starlink's mesh comms ramp up, it'll be significantly faster to go up to a bird, across through one or more at close-to-c, and then down into the local base station.
The fiber cable they ran from Perth up to Singapore a few years certainly won't be abandoned - it'll still be much cheaper / wider - but I can't imagine much appetite for any future under-sea cabling out of Australia (f.e.).
Is it because ISLs will require more powerful lasers because the light is focused through a lens instead of guided through a fiber?
Because laser energies, signal paths, traveling through free space must literally share that space with each other. It is effectively one wire. An underground cable can have hundreds, thousands, even millions of wires lying beside each other without interference.
It is comparable to the difference between a wifi connection and bundle of ethernet cables. One can scale and one cannot.
Could you just add more beams on each satellite?
[0] https://lilibots.blogspot.com/2020/04/starlink-satellite-dim...
Space is pretty big, lasers are pretty narrowly focused, and not many people have lasers in space yet.
I doubt the laser links support this, and I wonder if any could, when in a non-encapsulated environment. EG, spectral pollution from sunlight/etc.
"I can't imagine much appetite for any future under-sea cabling out of Australia"
And the reality is that satellites can not compete with the bandwidth of subsea cables for bulk data transfer, HFT is a whole other world.
If you want to observe events at one exchange and send orders to another, all that matters is total latency. For that use it doesn't matter whether your servers are in the same room as one of the exchanges or 200 miles away from either one.
You tend to get bandwidth spikes on most feeds at market open and close, but intraday rates are low
Every time SpaceX makes a goal, someone claims it's really far away until it is completed.
If there was a need for Terabit/s laser capacity for Starlink, there's no particularly good reason it couldn't be developed.
www.bloomberg.com/features/elon-musk-goals
I can imagine being able to do this when you control both sides by letting one type of data flow over one IP and the other over a different one with different peerings. But I wonder whether this is generally available.
I expect some ISPs will end up using differential routing over Starlink and fiber. They could have the routers on each end automatically switch large one-way TCP transfers from the Starlink connection to the fiber connection after the first 2MB.
They could even make the transition smooth, by buffering data transferred over Starlink and slowly adding delay to match the delay of the fiber connection. This would require some RAM, but only during the transition period for each TCP session. The client would see the throughput go down during the transition period.
If the remote server could increase the data rate, then the ISP could perform the transition with no drop in throughput seen by the client. The sending router would send fake ACKs to the server to get it to send data faster. The sending router would send the burst of data through the fiber link and also buffer it and send it through Starlink at the original rate. Once the receiving router is receiving the same data at the same time over both the fiber link and Starlink, the sending router can stop sending over Starlink. The client's TCP ACK packets would continue to flow over Starlink.
You would probably have to configure your own routing table to direct traffic for each application through the appropriate link, but that's completely doable as long as you can write rules to distinguish the packets (for example based on destination).
I can imagine that it would be beneficial for the internet experience if we could segregate low latency traffic (human/hft) traffic from hulk traffic such as video. Although this goes against net neutrality I suppose.
By your lightsped math, Starlink won’t ever be able to compete on latency except in the most rural of areas with poor connectivity since low earth orbit has far more travel distance than convoluted surface routing.
Since I moved on from that last gig, I note that Telstra completed their Sydney-Perth re-cabling project, and the Vocus Perth-Singapore undersea link came online (2018-04).
(I believe east coast traffic routes through Perth to get to Singapore, which was/is/will continue to be part of the problem.)
"lightspeed math" means LEO may well offer performance improvements over terrestrial cabling in many non-obvious scenarios.
I think the key word here is properly. I put my pre-order in Feb 9th and I'm in the Perth hills in Western Australia. My wired link is ~35Mb down and ~11Mb up. Whilst StarLink will be more expensive I'm expecting a tripling of download speeds and a doubling of upload speeds for less than double the price. That math works for me, especially when you consider my link is as fast as it can go (I pay for a 50/25 service) due to my last hop being a twisted pair cable that was run half a century ago.
Also, what is their IPv6 support like? Can I get a routable /60 or similar? Static IPv4/IPv6? And do you need to use their router or can you hook in anything you want? Bandwidth limits? Any other restrictions, either via their TOS or through some kind of firewall? Is this experience ever going to approach something like fiber or even cable?
Keep in mind that on something like a DOCSIS3 cable coax last mile segment can have a minimum latency of 12-16ms from just the cablemodem to the local CMTS in the neighborhood, so that's actually really good. It's not as good as fiber but it's significantly better than many other options. One has to account for the need for the antenna/modem to modulate and apply FEC on the Tx at both my CPE antenna and the spacex earth station on the other end (at least a few ms).
b. no ipv6 yet. They have people who know what they are doing for neteng so I am sure it is planned.
c. all IPs are in cgnat IP space right now. Nobody is getting a discrete dhcp-assigned public ipv4 /32 yet. You can hook up whatever router you want, anything you plug into the PoE injector that is an ordinary 1000BaseT 1500 mtu DHCP client will be given an address. The router they hand out is a very bare bones 802.11ac 2x2 MIMO thing that is based on openwrt.
restrictions, you can't move it from your designated service location. That's part of the beta TOS.
Using it, it is a real 150 Mbps down x 16.5 Mbps up. I have put non technical guest users on it doing various things and from their perspective it cannot be distinguished from the separate terrestrial connection at the same location.
Some individuals in /r/starlink have started reporting being assigned globally routable ipv6 addresses. So right now it's probably being tested.
Interesting, this is more like an internet proxy than connecting devices to the internet. Hope they fix it soon. Does the TOS forbid running eg ssh or remote desktop services? Or VPNs?
Eventually the Comcasts of the world will sell off the majority of the IPv4 they hold to the AWSs of the world.
I don't see why not in an IPv6 world.
And so died what was knows as "Internet" and AOL was resurrected…
citation needed
https://www.europol.europa.eu/newsroom/news/are-you-sharing-...
It is a fairly simple design.
heh, my assumption when I hear that people who know what they're doing are involved is the opposite ;)
Thank you for the detailed report! I'm very excited for the tech, especially once the lasers are up and it doesn't rely on the base station (i.e. I can take my uplink on a road trip)
I've read multiple tutorials on IPv6 and it's so complicated that I still can't grasp how it all works in my head. For some context, I've personally written an Ethernet IPv4 network stack with DHCP from scratch. I also worked on Ethernet switch firmware, coincidentally for SpaceX...
Also getting an entire public prefix assigned instead of just a single address is amazing too. On my public servers I let my ssh service listen on a randomly generated static IPv6 address from my prefix, which is not used for anything else. On that same machine I can have dozens of other public services on their own IP each (they can even all run on the same port because they're using different addresses), and when someone then decides to scan the IP of my website for interesting ports, they won't find anything.
To be honest, if someone doesn't understand IPv6, I doubt they really understand IPv4 either. Many issues with IPv6 today come from the fact that everyone and everything is so used to V4 concepts, that most products focus on IPv4 first and then half-ass IPv6 support (if they implement it at all).
Address asignment in an IPv6 world is more complicated - you can do DHCPv6, or your can do stateless auto-config. Which should you choose and when? Many other aspects of the stack require more knowledge.
And THEN you ALSO need to understand how v4 and v6 interacts so you can provide suitable compatibility - the various different methods of tunnelling and negotiation.
In my opinion you shouldn't really bother with compatibility. Just do dual stack and maybe NAT IPv4 if necessary.
For my personal use cases IPv6 just proved to be much more versatile than IPv4. It did take some getting used to since it's approached differently, but learning it is very worth it and also helps using IPv4 better
SLAAC is only a drop in replacement in the (typical) home.
I have seen too many people that have the same excuse. The advise I gave them is to forgot all the things learnt from IPv4 and study IPv6 as a totally new IP stack.
The problem is people look at it from IPv4 view, which is a currently a mess with IPv4 exhaustion.
Most people who would know how to set up port forwarding could probably set it up. I think even some routers support it built in now.
Of course, today IPv6 only can't be considered full internet access, so providers usually need both – and given that CGNAT gets consumers 99% of what they want/are willing to pay for, providers sometimes can't be bothered to also implement IPv6.
I used to have GCNAT + IPv6 on my provider, but the v6 part of their CPE was worse than useless – no option to open ports since "port forwarding is not needed on IPv6" (nevermind the mandatory firewall that doesn't allow inbound traffic unless completely disabled).
At night it's something like 10ms.
The ISP network and node is oversaturated and they plan to do nothing about it (Cox).
So I'm actually excited if Starlink can provide 20-30ms stable latency, I have an option which is not tied to the regional operators.
Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=12ms TTL=115
Reply from 1.1.1.1: bytes=32 time<1ms TTL=60
Some sort of local caching going on.
Even my ISP's next hop is 2.5ms, 8.8.8.8 and 1.1.1.1 are both at 4.7ms.
To Stockholm, which is only 80 or so km away if you measure straight line, is 3.5 ms away.
Iv'e always been curious as to what adds so much latency and what I did read was that its the network equipment itself mostly. The inherent latency in the fiber should be on the order of much less than 1 ms as far as I understand. 3.33 us per km, and 3,33 * 104 (more realistic distance) is only 346 microseconds.
Its weird though, using mtr its very clear that its the "long" hop that most of the latency, or at least 2.8 ms. So is the figures for speed of light in fiber wrong, or is there something else that adds up to a lot of latency in fiber connections? Is it the optical components?
Signals in fiber do not travel at c. They travel at lightspeed in glass. Light speed in a material is c/(the refractive index of the material). For commercial glass fiber, 1.5 is a reasonable estimate for it's refractive index. So the actual time for 1 km is ~5 us.
Then you’ve got the buffers - you could feed 5x100M streams on 1G carriers into a 1G uplink port and have plenty of bandwidth, but if all the packets of those 100M streams arrive in 100ms, then have no packet for the next 900ms, your outbound traffic will have to either delay your packets upto 900ms, or drop them.
Or I guess more generally, as an existing user of the service who is seeing dashboards I'm not seeing, how do you think this would play out for "occasional" users.
there is no seasonal 'pause' service plan offered yet.
But they don't seem to be selling that capability to consumers just yet - presumably to avoid issues with too many subscribers congregating in one place. See the faq answers on "Can I travel" and "Can I change my service address" https://www.starlink.com/faq
I like how technical they still are. Probably a matte of time before they have to dumb-down everything there.
There's no way you are crossing borders with it and transmitting from a country where it's not approved.
I noticed this:
https://www.canadasatellite.ca/Satellite-Phone-Limitations.h...
"While satellite phones work essentially anywhere on earth, there are some physical and political limitations."
one limitation was not what I expected:
"Cuba restricts the use of satellite phones because they’re seen as tools for subversive purposes"
Back to starlink - I think distributed living is a wonderful if not the most wonderful application of this.
I can imagine in a number of years having a tesla pull a trailer with fold-out solar panels. Have a little self-sufficient base camp with power for climate, cooking, transportation. And now internet.
Like North Hollywood, CA.
https://abc7.com/att-internet-fiber-man-takes-out-wall-stree...
the current terminal has motion sensors in it and is not designed for a moving vehicle, it will turn itself off. the same 6-axis sensors that are used to orient and tilt it to the proper angle can also tell it when it's being moved.
Except then this thing were they assign you to a single cell and the vessel may pass the boundaries of said cell? Do you expect some sort of protocol for automatic handoff to the next cell in the future?
The limitation with the cells is that currently not all cells have the same amount of sats above them so they will not claim that guarantee anything.
Some people have tested that and it worked fine if you move it.
They will likely have a different terminal or plan for mobile service, would be my assumption.
How often do packets get dropped? Have you given it a try with quake or counterstrike?
Mine is averaging about 0.5% packet loss over a 3 hour period. There will be very brief periods of slightly higher loss. I don't play a lot of fps but most realtime lag, loss and jitter sensitive applications work just fine.
But do you think it would still work in a fixed configuration like that?
And how much do you think tree coverage would affect service?
Trees cannot be in the way. 11GHz+ doesn't like trees.
The ability to align itself allows for mildly to moderately improved reception. It's more cost-effective than improving the beamforming, and easier for the user. It's a good feature. But the terminal doesn't need it to work. (On a hardware level. Any possible software lockout is a separate issue.)
That's extremely impressive, all things considered.
So how does it handle the switch from that satellite to the next one without losing signal?
Any discernible pattern for the hops through the constellation?
Any general thoughts about the topology?
I appreciate it. My family got into the beta today, not just the pre-order but it sounds like it won't ship for a few weeks. Thanks again.
nothing obviously satellite related shows up at layer 3. There's a few hops of stuff with no rDNS, and then the edge of the AS36492 network and whatever transits or peers your traffic is going to.
You can clearly discern from pinging your first hop (15.9 to 30ms away) that it's something on the other side of the up-and-back satellite link.
topology at present is logically a bent pipe. satellites need to be simultaneously in view of your terminal and a spacex earth station. The ten satellites they launched into a polar orbit last month are the first with inter-satellite laser links.
Does that mean that there is no connection between satellites?
https://caseyhandmer.wordpress.com/2020/09/23/starlink-packe...
It's unlikely that anyone's traffic is passing through multiple satellite links at this time, but that may change with higher elevation orbits serving states like Alaska.
But i think that they would have to become ISP and comply with local law with most jurisdictions if they want to have local ground stations. Not sure how that will go.
Maybe a few people in Asia, Africa, South America can afford it, but it is very few, and in the places where people can they are likely to already have better service.
About 3.5 billion people don't have reliable access to the internet[1]. That's a large market.
The satellites are orbiting anyway.
For household customers in OECD countries, Starlink will charge OECD retail prices.
Customers in developing countries represent extra revenue for negligible extra cost, so Starlink can practise geographic price discrimination to maximise net revenue.
Or Starlink could permit "village WISP" bandwidth reselling arrangements in specific geographic areas. A video call needs no more than 2 Mbps down and up, so you can probably serve up to 50 undemanding households plus a one-room school and a medical clinic on one connection (with appropriate rate limiting and local caching).
Starlink can also price-discriminate by latency tier for high-frequency traders and arbitrageurs. They can price-discriminate by QoS for organisations that demand a guaranteed minimum bandwith (e.g. militaries). And then there are shipping lines and air lines.
1. https://www.weforum.org/agenda/2020/04/coronavirus-covid-19-...
("weforum" is the World Economic Forum.)
Today every where in the poorest parts of the world are connected with cell phones.
If you split between 5 houses, you still get decent bandwidth (you wont be watching 4k, but then again if you can afford 4k screens ...), and the price is 100 USD + 20 per month.
If you don't have any other option this might be decent alternative
Netflix says you need 25 Mbps for "Ultra HD Quality"[1], so yes, you could watch a different 4K stream in every house simultaneously. And have 25 Mbps left over for other traffic.
Edit to add: Netflix is right.
If you can't get reliable 4K with a 25 Mbps connection, the most likely reasons are:
- First by a wide margin, is that you are using Wi-Fi to connect your display device. Don't do that. Use ethernet (at least until you have 802.11ax everywhere).
- Second, you have a flaky connection to your ISP. Misconfigured, marginal (e.g. DSL more than 2.5 kilometres from the cabinet) or in poor electrical condition.
- Third, you have neighbours regularly operating very large electric motors or electric arc welders.
- Fourth, your ISP doesn't know what it's doing, or is deliberately monkeying with your service to try to upsell you.
This is something to keep in mind and not obvious to people living in 1st world countries.
Anyway, even that number alone is a sizable market, and even Comcast would be happy with a fraction of it. I know some parts of the world are better off than the USA, but I also know many parts are worse off.
$499 USD for the dish, $99 USD per month for service (no data cap.) Price seems to change to local currency if your country is not USA.
Is it though? Perhaps it's because it's not available in Croatia, but there is nothing on the front page that mentions price, and it's not in the FAQ either.
I really dislike this kind of (almost dark) pattern. TIDAL also is not showing you the cost until you start down the sign up process, it's quite frustrating if what you really want to do is compare service costs.
Besides, it's not like if you click that Order Now button that it instantly places an order and a SpaceX kit drops from space in your front yard seconds later. There's a few more steps before that happens, like payment info.
Doesn't change to Rupees in India despite being able to find the address. Still shows 99$ for me.
My most important message to everyone reading this is that it's not intended to compete with properly implemented wireline based services. It's going to absolutely blow away consumer-grade highly oversubscribed, bottom of the barrel ku and ka band geostationary satellite services (hughesnet, viasat in the USA, xplornet in Canada), and any WISP that can't keep up with a 150 Mbps figure.
And eventually for really hard to reach places in the developing world, and much of the same offshore/aviation/maritime industry that right now pays tons of money to Inmarsat.