I’ve been using Starlink for a few months now. It’s great for the cost. One annoying thing is their super non-standard and kind of broken network setup if you want to use your own router. They have two subnets with different IP ranges (cgNAT and local) on the same Ethernet link. You have to do some weird manual routes, interface resets, and dhcp client configuration if you want things to work reliably.
When they're doing network maintenance/beta downtime/terminal firmware updates, your router will fail to get an IP address in the cgnat space, but the terminal itself will give the router a new lease in 192.168.100.x (you can ping the antenna at 192.168.100.1), and your router will be happy because it has successfully received a lease and can keep renewing it).
Then when the network unavailability is finished, your router keeps its 192.168.100.whatever address and the terminal doesn't issue it a new cgnat address.
This sort of setup is weird and not normal, so once your default-configuration DHCP client WAN port router is stuck, you need to manually tell it to go get a new lease, or set up your dhcp client in such a way that it always rejects IPs and leases in 192.168.100.x. I can see why they do it, because they want the starlink app on peoples' phones to be able to communicate with the grpc endpoint on the terminal during outages.
But they'll clearly need to do something different with the terminal's firmware and how it treats BYOD router customers, because people will expect to connect a ordinary DHCP client and have it 'just work', and resume working after an outage has cleared.