The Event Log in the Starlink app is your window into what’s happening on your network. It shows key moments that may affect your connection — including outages, router issues, and other events that can impact performance.

The goal of the Event Log is transparency. We want you to see what’s happening in your network in real time, not just when service is completely offline. This helps you understand the cause of issues when they happen.

​

How is this different from the old Outage Log?

Previously, the Starlink app included an Outage Log, which only tracked periods where your user terminal lost connectivity.

The new Event Log includes:

• All of the information from the previous Outage Log.
• Router-related outages (for example, if your Starlink router was powered off or disconnected).
• Non-outage events that may affect service quality but don’t necessarily bring your network fully offline (such as elevated packet loss or device reboots)

This expanded view makes the Event Log a more powerful tool for diagnosing issues across your whole Starlink setup.

​

Why does Starlink show events that don’t cause full outages?

Not every issue that impacts your experience will take your network completely offline. For example, a spike in packet loss might not interrupt web browsing but could cause video calls or online games to stutter.

By showing these events, we:

• Help you connect the dots between what you’re experiencing (e.g., "my video call stuttered") and what’s happening on the network.
• Give transparency into the health of your connection, even during minor issues.
• Use the same data internally to improve the network — what you see is what we see.

​

Will more events be added over time?

Yes. The Event Log is designed to grow. We’re continually adding new event types as we refine what’s most useful to share. Our philosophy is to be as open as possible about what’s happening on your network.

The goal isn’t to alarm you, but to keep you informed. Many events are minor and won’t affect everyday use, but when something does go wrong, the Event Log gives you the context you need to understand why.