10 ms·

You can see a lot of Starlink’s peering at https://www.peeringdb.com/net/18747 https://www.peeringdb.com/net/18747

mike_d 5y ago
I'm not sure what they are actually using this for. All Starlink customer traffic egresses via Google's network, and all their ground stations are along Google fiber paths.
- londons_explore 5y ago
  Perhaps to have a decent negotiating position next time their contract with Google comes up for renewal? You get much better prices if Google can see you already have most of your own infrastructure set up and ready to migrate to with not much effort.
- walrus01 5y ago
  > all their ground stations are along Google fiber paths. actually most of their earth stations are colocated near long haul dwdm regen huts from older, more traditional big telco players like what is now lumen (former qwest/centurylink), level3, zayo, etc. The fact that they can buy transport circuits from those huts to the nearest major cities to meet google is useful. by no means does google really own/run/control most of the long haul dark fiber and dwdm networks in north america. or even a good portion of it. the predecessor entities that have now been rolled up into lumen or zayo do.
  - mike_d 5y ago
    I meant Google fiber paths in the logical sense. Most people don't care to understand the distinctions in how bits on glass are purchased.
    - walrus01 5y ago
      In most of those places it's not even a Google fiber path in the logical sense, where Google doesn't have a DWDM chassis at the Regen hut, site or an iru in any dark strands there. Starlink is buying transport circuits from the traditional telcos who operate on the route to get to a major city with a Google POP. Like, if you go out to the Prosser Regen hut site and starlink earth station, that's all legacy level3, now lumen.
    - deleted 5y ago
      [deleted]
- kortilla 5y ago
  > All Starlink customer traffic egresses via Google's network That’s not true. Customers that were getting public IPs without CGNAT were coming from a non-Google ASN.
  - JustFinishedBSG 5y ago
    That doesn't mean anything, Google will announce your routes for you if you want. [1] [1] https://cloud.google.com/network-connectivity/docs/router/how-to/configuring-bgp https://cloud.google.com/network-connectivity/docs/router/ho...
    - kortilla 5y ago
      The google asn would still show up in the path if that were the case.
  - mike_d 5y ago
    > That’s not true. My two Starlink terminals respectfully disagree. It has been mentioned numerous times on the Starlink forums. It's IP space previously used by Google Station.
    - walrus01 5y ago
      both are happening simultaneously in different areas, there are still many starlink terminals behind cgnat inside the google ASN, there are now some starlink terminals that have been giving out dhcp leases of public addresses owned/controlled by the starlink ASN, and there are also starlink terminals that have been seen doing cgnat and with an exit point in the starlink ASN. it really depends on where you are and whether your terminal has been selected by (some unknown criteria) for spacex's network topology changes.
    - kortilla 5y ago
      Do you have public IP addresses assigned directly to your router? This was showing up on the people who got public IPs.
- virtuallynathan 5y ago
  Not anymore, customers are being migrated to AS14593. I'm one of em.. I'm in 170.203.91.0/24.
jcun4128 5y ago
I barely understand what this is. Wondering would you find these through traceroute or something? huh Or people populate them at will
- walrus01 5y ago
  peeringdb runs on trust, any ISP could put in non factual entries, but it would be useless to anyone. it's meant to be used by network admins at other ASNs that want to set up peering sessions across IXes and PNIs.

I'm not sure what they are actually using this for. All Starlink customer traffic egresses via Google's network, and all their ground stations are along Google fiber paths.

londons_explore 5y ago
Perhaps to have a decent negotiating position next time their contract with Google comes up for renewal? You get much better prices if Google can see you already have most of your own infrastructure set up and ready to migrate to with not much effort.
walrus01 5y ago
> all their ground stations are along Google fiber paths. actually most of their earth stations are colocated near long haul dwdm regen huts from older, more traditional big telco players like what is now lumen (former qwest/centurylink), level3, zayo, etc. The fact that they can buy transport circuits from those huts to the nearest major cities to meet google is useful. by no means does google really own/run/control most of the long haul dark fiber and dwdm networks in north america. or even a good portion of it. the predecessor entities that have now been rolled up into lumen or zayo do.
- mike_d 5y ago
  I meant Google fiber paths in the logical sense. Most people don't care to understand the distinctions in how bits on glass are purchased.
  - walrus01 5y ago
    In most of those places it's not even a Google fiber path in the logical sense, where Google doesn't have a DWDM chassis at the Regen hut, site or an iru in any dark strands there. Starlink is buying transport circuits from the traditional telcos who operate on the route to get to a major city with a Google POP. Like, if you go out to the Prosser Regen hut site and starlink earth station, that's all legacy level3, now lumen.
  - deleted 5y ago
    [deleted]
kortilla 5y ago
> All Starlink customer traffic egresses via Google's network That’s not true. Customers that were getting public IPs without CGNAT were coming from a non-Google ASN.
- JustFinishedBSG 5y ago
  That doesn't mean anything, Google will announce your routes for you if you want. [1] [1] https://cloud.google.com/network-connectivity/docs/router/how-to/configuring-bgp https://cloud.google.com/network-connectivity/docs/router/ho...
  - kortilla 5y ago
    The google asn would still show up in the path if that were the case.
- mike_d 5y ago
  > That’s not true. My two Starlink terminals respectfully disagree. It has been mentioned numerous times on the Starlink forums. It's IP space previously used by Google Station.
  - walrus01 5y ago
    both are happening simultaneously in different areas, there are still many starlink terminals behind cgnat inside the google ASN, there are now some starlink terminals that have been giving out dhcp leases of public addresses owned/controlled by the starlink ASN, and there are also starlink terminals that have been seen doing cgnat and with an exit point in the starlink ASN. it really depends on where you are and whether your terminal has been selected by (some unknown criteria) for spacex's network topology changes.
  - kortilla 5y ago
    Do you have public IP addresses assigned directly to your router? This was showing up on the people who got public IPs.
virtuallynathan 5y ago
Not anymore, customers are being migrated to AS14593. I'm one of em.. I'm in 170.203.91.0/24.

jcun4128 5y ago

I barely understand what this is. Wondering would you find these through traceroute or something? huh Or people populate them at will

walrus01 5y ago
peeringdb runs on trust, any ISP could put in non factual entries, but it would be useless to anyone. it's meant to be used by network admins at other ASNs that want to set up peering sessions across IXes and PNIs.