Skip to main content
OpenEye Knowledge Base

Starlink Best Practices

Optimizing Starlink for Network Stability, Reliability, and Throughput with IP Camera Deployments

Starlink is a low-earth orbit (LEO) satellite internet service provided by SpaceX. While it delivers broadband-quality speeds to remote and rural locations, its upload bandwidth constraints and network behavior require careful planning — especially for deployments involving IP cameras and video surveillance systems. This article covers Starlink hardware options, service plans, setup best practices, and optimization strategies to maximize stability, reliability, and throughput.


Starlink Hardware Kits

Starlink offers several dish hardware options. Choosing the right kit is the first step toward a stable deployment.

https://starlink.com/specifications/1 

Starlink Service Plans

Starlink offers multiple service tiers. Plan selection directly impacts network priority, upload/download speeds, and data availability.

https://starlink.com/business/service-plans 

Dish Placement & Physical Setup

Proper physical installation is the single most impactful factor in Starlink performance. No software or router configuration can compensate for a poorly placed dish.

  • Clear Sky View is Critical: The dish requires an unobstructed view of the sky. Use the Starlink app's obstruction viewer and cross-check the line of sight — red areas represent directions where something is blocking the dish's view of satellites.
  • Mount as High as Possible: Roof mounts consistently outperform ground mounts. Raising the dish by even 6 feet in treed areas can add 5–10% usable throughput and materially improve stability. Ground mounts are the easiest to install but sit in the worst position for sightlines.
  • Pole Mounts in Treed Areas: In heavily wooded environments, a pole mount that elevates the dish above the tree line is the most effective solution. Ranking: Pole > Roof Peak > Suction/Low Roof > Ground.
  • Account for Seasonal Changes: Trees that appear clear in winter may cause significant obstruction in summer. Evaluate placement during the leafy season if possible.
  • Cable Routing: The Standard kit includes a standard-length cable; the Performance kit includes a 25m (82 ft) cable for greater mounting flexibility on tall masts or remote rooftop positions.

Network Setup & Router Configuration

QoS & Traffic Management

Quality of Service (QoS) does not create additional bandwidth — it determines which traffic gets priority when the upload pipe is constrained.

  • Prioritize camera event traffic and remote access over background processes.
  • De-prioritize or schedule: OS updates, firmware downloads, and bulk file transfers.
  • Set upload bandwidth limits per device to prevent a single device from saturating the upload channel.
  • Use VLANs to segment camera/NVR traffic from general office or user traffic. This isolates video traffic and makes QoS rules easier to apply and enforce.
  • Monitor per-device usage through your router's dashboard to identify unexpected bandwidth consumers.

Bandwidth Requirements

OpenEye recommends an NVR site upload bandwidth speed of 5 Mbps for an optimal experience when remotely viewing video over the WAN (Internet). This will result in a positive user experience when reviewing video from one 4MP high definition stream, or up to 9 standard definition streams. In instances where less than 5 Mbps is available remote users should plan to utilize standard definition streams for retrieving video over the WAN.

While the OWS platform is highly configurable to meet exact bandwidth usage requirements the following table may be referenced as a typical use case:

Average bandwidth usage based on D1/4MP, 4,000Kbps, 15 IPS, 30 GOP IP Cameras
Channel Count Live & Search SD Playback Live & Search HD Playback
Single channel 800 Kbps 4 Mbps
4 channel grid 3 Mbps 16 Mbps
9 channel grid 7 Mbps 36 Mbps
16 channel grid 13 Mbps 64 Mbps

NOTE: The OWS platform dynamically chooses HD or SD streams for viewing based on the client display configuration selected by the user. For example, a 4-channel view will deliver SD video by default while a single-channel view will automatically deliver the HD stream. Stream selection may also be manually controlled using the stream selection control at the top of the applicable display screen.

Upload Bandwidth Optimization for IP Cameras

Upload bandwidth is the primary constraint on Starlink for camera deployments. The following settings help ensure upload activity does not saturate available bandwidth.

Camera Configuration

Setting

Recommendation

Impact

Resolution

720p–1080p (avoid 4K for clip uploads)

Reduces upload size by 50–75% vs. 4K

Frame Rate

10–15 fps (vs. 30 fps)

Reduces file size and upload time by ~40–50%

Encoding

Variable Bitrate (VBR)

Adapts to scene complexity; smaller files on static scenes

Remote Viewing

Limit simultaneous live streams

Each remote stream consumes upload bandwidth

Clip Uploads to OWS

Upload during off-peak hours when possible

Avoids competing with live remote access traffic

Recorder Data Usage

OpenEye recorders always maintain a lightweight connection to OWS. OpenEye recommends a weekly configuration backup, alert transmissions of recorder health, and day/night images for cameras. Alert images attached to video events is optional.

While the OWS platform is highly configurable to meet exact data usage requirements the following table may be referenced as a typical use case:

Data Usage based on minimum one image per alert per day / minimum one weekly config backup
Usage Category Usage per 30 Days (MB) Average per Day (MB)
Baseline Cloud Communication 1350 45
Configuration File Backup .24 .01
Alert Transmission .99 .03
Alert Images 45 1.5
Day / Night Images 1440 48
Estimated Total with All Options 2836.23 94.54

 

Export 20 mins. to OWS per month
Usage Category Usage per Clip (MB)
20 Minute Incident Review (4MP to OWS) 984
20 Minute Incident Backup (2MP to OWS) 306

NOTE: Measurement of 20 minutes covers a 20 minute clip or multiple clips equaling up to 20 minutes.

NOTE: Video is downsized before export to 2MP. An option is available to keep at 4MP, but for more data usage.

NOTE: Once stored in OWS, review of incident clips in the cloud do not affect data usage of individual sites.

Scheduling & Off-Peak Usage

  • Schedule clip uploads to OWS during off-peak hours (5–8 AM is typically the lowest congestion window on Starlink).
  • Avoid large uploads during peak hours (6 PM – 11 PM local time), when Starlink's ground stations and satellites experience the highest traffic load. Upload channels are more limited than download and become bottlenecked faster.
  • Disable automatic updates on non-critical devices (smart TVs, tablets, phones) connected to the same network to prevent unexpected bandwidth spikes.

Reliability & Redundancy

  • Cellular Bonding / Failover: For mission-critical sites, pair Starlink with a cellular connection (LTE/5G) using a router with multi-WAN support (e.g., Pepwave). This provides combined bandwidth and automatic failover if Starlink experiences an outage.
  • UPS (Uninterruptible Power Supply): Power the Starlink dish and router on a UPS to maintain connectivity during brief power outages. A UPS on the router alone does not help if the Starlink power supply goes offline — both must be protected.
  • Periodic Reboots: Scheduled reboots of the dish and router can resolve memory leaks, clear network congestion, and apply firmware updates. Allow ~15 minutes after a dish reboot for the connection to fully stabilize.
  • Monitor Outages vs. Wi-Fi Issues: Use your router's WAN monitoring tools to distinguish between Starlink satellite-side outages and local Wi-Fi/LAN issues before troubleshooting or replacing hardware.

Starlink App — Key Features for Monitoring

  • Obstruction Viewer: Real-time and historical view of sky obstructions affecting the dish.
  • Speed Test: Built-in speed test to measure current upload/download performance.
  • Data Usage: Monitor monthly data consumption (especially important on Priority/Roam plans with data caps).
  • Alerts & Notifications: Set up usage alerts to stay ahead of data cap thresholds.
  • Reboot Controls: Remotely reboot the dish and router from the app.
  • Dish Statistics: Accessible even in Bypass Mode via 192.168.100.1.

 

  • Was this article helpful?