
What to Collect Before Contacting Starlink Support: A Faster Troubleshooting Handoff
Troubleshooting & Fixes
A good support request is easier to act on when it describes one clear symptom, the time it started, what is affected, and what you already tested. This checklist helps you prepare that handoff without sharing passwords or changing several settings at once.
What this guide is for
Use this when Starlink is slow, offline, unstable, or behaving differently from normal and you may need help from Starlink support. It is useful whether the problem is continuous or happens only at certain times.
The goal is not to guess the cause. The goal is to give support a clean, repeatable description of the problem.
1. Name the symptom precisely
Start with the smallest statement that is definitely true:
- No internet anywhere: Starlink's status appears offline, or every tested device loses internet access.
- Wi-Fi problem: the Starlink connection appears available, but devices cannot join or lose the wireless connection.
- One-device problem: other devices work normally, but one laptop, phone, console, or smart device does not.
- Slow or unstable service: pages load, but speed, latency, packet loss, video calls, or uploads are unreliable.
- Short interruptions: service returns by itself and the timing or duration is repeatable.
Record whether the problem affects all devices, only wireless devices, only wired devices, or only one room or access point. That distinction is often more useful than a single speed-test result.
2. Record when it happens
Write down:
- The date and local time the problem began.
- Your time zone.
- Whether it is continuous, intermittent, or tied to a particular time of day.
- The approximate start and end time of at least two interruptions.
- Whether the problem began after a move, storm, power event, cable change, router change, software update, or new device.
Use the same clock for every test. If you take screenshots, keep the timestamp visible where possible.
3. Record the complete connection path
Support needs to know what sits between the Starlink terminal and the device showing the problem. Note:
- The terminal and router names or models as shown in the Starlink app or on the equipment.
- Whether you use the Starlink router, a third-party router, mesh Wi-Fi, an Ethernet adapter, a switch, or additional access points.
- Whether a third-party router or mesh system is using Starlink bypass mode.
- Whether the issue occurs over Wi-Fi, Ethernet, or both.
- Any visible cable damage, loose connection, unusual light, heat, smell, or power warning.
- Any recent change to the dish position, cable route, router, network settings, or power supply.
Do not climb onto a roof or handle damaged electrical equipment just to collect evidence. Describe what you can safely observe.
4. Run a small set of low-risk checks
Record the result of each check rather than only writing “still broken”:
- Check the Starlink app for its current status, alerts, and any visible service or obstruction information.
- Test one device close to the router, then test a second device.
- If a wired connection is already available, compare it with Wi-Fi.
- Open more than one unrelated website or service so one failed site is not mistaken for a complete outage.
- Run one speed or connectivity test and record the time, device, connection type, download result, upload result, and latency if shown.
- Check whether the same symptom appears on another access point or room.
- If power was interrupted, record when it happened and whether Starlink recovered without further changes.
Avoid a factory reset, repeated power cycling, or several network changes before recording the original state. If you do make a change, write down exactly what changed and the time.
5. Prepare useful evidence
A short set of relevant screenshots is better than a large bundle with no explanation. Useful evidence may include:
- The Starlink app status or alert screen.
- The app's statistics or outage view with the time range visible.
- A speed test showing the device and connection type.
- A photo of the indoor equipment and cable connections, if it can be taken safely.
- A simple network sketch showing terminal, router, mesh or access points, and the affected device.
- The exact wording of an error message.
Review every image before sending it. Remove Wi-Fi names, personal addresses, email addresses, device names, QR codes, and other information that is not needed for the support request.
6. Keep secrets out of the request
Never send any of these in a post, public forum, screenshot, or ordinary message:
- Your Starlink account password or Wi-Fi password.
- A one-time verification code.
- Full payment-card or bank details.
- Recovery codes.
- Unredacted personal documents.
Use Starlink's authenticated support channel for account-specific information. Support may need to verify the account, but that does not mean you should place credentials in the troubleshooting description.
7. Use this support handoff template
Copy this into a private support request and replace the brackets:
unknown nodeDo not paste passwords, verification codes, or full payment details into the template.
8. Keep a small case log
After contacting support, record the case number, the time of each reply, the instruction you were given, and the result of each test. Change one variable at a time when possible. A short log prevents a later support agent from repeating steps and makes it easier to tell whether a change actually helped.
Quick checklist
Before sending the request, confirm that you have:
- One precise symptom.
- A start time, time zone, and interruption pattern.
- The affected-device scope.
- The Starlink app status or alert wording.
- At least one comparison test.
- The equipment and network path.
- Recent changes and power events.
- Redacted screenshots or photos.
- No passwords, codes, or payment details.
This information does not replace Starlink support's diagnosis. It makes the first conversation clearer and gives the next troubleshooting step a better starting point.