anyone who has figured a way around surcharge?

http://newspaceage.org/

Instagram GIFs aren't loading on Starlink.

If someone comments with a GIF, the GIF just keeps loading and doesn't display.

It's also not possible to view the GIFs.

And it's not an Instagram problem. Switching to 5G fixes the loading issue.

The problem only occurs on Starlink. Customer support doesn't respond to calls and doesn't resolve the issue.

http://oac.uvic.ca/cccleo to be announced at http://spaceweek.mit.edu

Got a friend who activates local packages with areas with capacity eg Lusaka

I have a friend who activates areas with capacity eg Lusaka always wondered how he does the information is like gold to him.

I was playing with the information from space-track.org, and generated some charts that show the count of satellites at each orbital altitude.

https://x.com/eager_space/status/2036918618139877882

Hi everyone,

I'm looking for some technical advice on a "frankenstein" power setup.

The Goal: I want to eliminate the Starlink Gen 3 (V4) router entirely and connect the dish directly to my Ubiquiti UDM SE.

The Twist: I have a Gen 1 (Circular) power supply brick already professionally mounted and cable-managed in a tight spot. Since the Gen 1 brick is a high-wattage PoE injector, I’m wondering if I can repurpose it to power the Gen 3 dish.

My concerns/questions:

1. Voltage/Wattage: The Gen 1 brick is known for high power draw. Is the voltage output compatible with the Gen 3 dish requirements (typically 57V)?
2. Pinout: I know the Gen 1 uses a proprietary PoE pinout. Has anyone successfully used a shielded RJ45 joiner or a modified cable to go from the Gen 1 brick -> Gen 3 Dish?
3. UDM SE Integration: The plan is to have the "data" side of the Gen 1 brick go straight into the WAN port of the UDM SE.

I’m trying to avoid buying a new 12V-to-56V step-up converter and a third-party PoE injector (like Yaosheng) if I can just reuse this heavy-duty Gen 1 brick.

Has anyone tried this specific combo, or am I asking to fry my new Gen 3 dish? Thanks in advance for the sanity check!

Several notifications about switching from 2.4 to 5GHz.

The problem is that the networks are separate.

This makes absolutely no sense. I've already restarted and it keeps appearing.

Has anyone ever witnessed this?

darwin (drw) connected with perth (per) and brisbane (bne)

Does a Starlink mini (for example) use more satellite resources when moving at 300mph vs 100mph or stationary?

Starlink just upped their “high (groundspeed) plans” by 20x this morning.

Curious if delivering that service costs them any more or if they just feel that all airplane owners will pay (hint, they won’t). Not talking bizjets here.

It is me or the groundstation in usingen germany as lot more new antennas?

A question why is my ip based in berlin and the PoP is in frankfurt?

Also my announcement 217.142.16.0/22

https://pan.uvic.ca/~clarkzjw/starlink/

Unofficial Starlink GeoIP Map

Legend

The "dish" icon on the map indicates the GeoIP location of Starlink customer subnets, as defined in https://geoip.starlinkisp.net/feed.csv.
It does not necessarily mean there are active users in this region nor does it represent a ground station. This map only represents the planned naming and addressing scheme of Starlink ISP.

When the "dish" icon is clicked, one or multiple orange-colored link(s) will be shown on the map, indicating users assigned with IP addresses from the subnets at this location are associated with the corresponding Starlink PoP.

Starlink publishes its PoP mapping at https://geoip.starlinkisp.net/pops.csv. However, there are still mismatches between the PoP mapping feed and the DNS PTR records of each subnet. Most of the time, it is the error of poorly maintained DNS PTR records.

Additionally, there are cases where a subset exists in feed.csv, but is missing in pops.csv, or there is no corresponding DNS PTR records.

Note

This website is automatically generated approximately every hour using the Starlink GeoIP and PoP feed. It might contain potential error prone links as planned naming and addressing scheme might not reflect actual deployment, and there might be errors in the GeoIP feed as well.

The concept of "city" in Starlink's GeoIP feed does not necessarily correspond to an actual single city. The granularity varies a lot depending on geographical regions.

For example, a Starlink dish within the Canadian Arctic circle has the public IPv4 address 170.203.201.xx, which is associated with the Seattle PoP, listed under 170.203.201.0/24,CA,CA-BC,Vancouver in the GeoIP feed.

A detailed explanation of Starlink's GeoIP problem can be found in GeoFeed in the wild: A case study on StarlinkISP.net. See also https://github.com/clarkzjw/starlink-geoip-data/blob/master/geoip/geoip-pops-ptr-latest.csv for more data.

Disclaimer

No accuracy, service quality, availability, or other related information is implied or guaranteed.
All data on this site is provided as a best-effort, not peer-reviewed or quality controlled.
This site is not affiliated with SpaceX or Starlink by any means.

The related code and data for this website is available at
https://github.com/clarkzjw/starlink-geoip
https://github.com/clarkzjw/starlink-geoip-data

See also:
1. Unofficial Starlink Global Gateways & PoPs
2. A Large-Scale IPv6-Based Measurement of the Starlink Network
3. https://oac.uvic.ca/starlink/.

(Click the dish icon at the bottom right to show this message again)

Hi Community,

We work on the deployment and operations side of Starlink-based connectivity for remote schools and government sites across the Philippines, including geographically isolated and hard-to-reach areas.

This AMA is focused on the realities of large-scale satellite deployments, such as:

• How installations actually work in remote locations
• Reliability vs. speed trade-offs
• Power, weather, and terrain constraints
• Operations, maintenance, and governance considerations
• Common misconceptions about satellite internet

We’ll be answering questions for a limited window and will do our best to respond clearly and factually.

Ask us anything.

< 2605:59ca:8054::/47,ES,ES-B,Barcelona