Get One Month of Starlink FreeSPECIAL OFFER: GET A FREE MONTH OF STARLINK >
Close-up of an outdoor CCTV camera installed on a wall for security purposes.

How to Keep a Starlink-Connected Camera System Useful During Internet Outages

Tips & Tricks

Back to Tips & Tricks

A Starlink outage does not have to make every camera useless, but only if the system has a local path and local storage. A cloud-only camera may stop recording or sending remote alerts when the internet disappears, while a camera and recorder on the same powered LAN can often remain viewable from inside the property.

This guide separates local recording, local viewing, remote alerts and power so you can test the setup before an outage matters.

Menu names and offline behaviour vary by camera, recorder and router. Treat the camera manufacturer's documentation as the authority for supported local recording, app access and storage limits. Do not rely on this guide as a substitute for a monitored alarm or emergency service.

The short answer

  1. Identify which cameras can record to an SD card, NVR or other local storage.
  2. Keep the cameras, recorder and at least one local viewing device on the same trusted network.
  3. Give the recorder and network equipment dependable power, and check storage health.
  4. Test local viewing with the Starlink internet path unavailable while the LAN stays powered.
  5. Use a separate cellular or monitored path for alerts that must reach you away from the property.
  6. After Starlink recovers, confirm time, storage, uploads and notifications rather than assuming everything caught up.

A local camera system can preserve evidence during an internet outage. It cannot guarantee remote viewing, cloud recording or phone notifications without another working internet path.

Separate the four paths

Write down what happens to each of these when Starlink is unavailable:

  • Camera capture: the camera continues producing video.
  • Local recording: an SD card, NVR or computer saves that video on the property.
  • Local viewing: a phone, laptop or monitor on the same LAN can open the camera or recorder.
  • Remote access and alerts: a cloud service or phone outside the property can receive video or notifications.

These paths are often treated as one feature, but they fail differently. A camera may keep recording locally while its cloud app shows the device as offline. Conversely, a cloud-only camera may still display a cached status while no new footage is being stored.

Choose a local recording path

Use the camera or recorder documentation to confirm which option is supported:

  • An SD card inside the camera.
  • A network video recorder (NVR) on the same LAN.
  • A local server or NAS with a supported camera-recording application.
  • A camera hub that records locally and syncs to the cloud later.

Check the details, not just the word local:

  • Does recording continue when the internet is disconnected?
  • Does the camera require a subscription for motion recording?
  • Does the recorder keep recording when its cloud account is unreachable?
  • Is the storage encrypted, and can you export a short clip?
  • What happens when the card or disk is full?
  • Does the system overwrite old footage or stop?
  • Is the camera's clock maintained during an outage?

For a critical view, use a recording path that you can open and test from the LAN without an account sign-in that depends on the cloud.

Keep the local network simple

Cameras and the recorder should normally be on the same trusted LAN during the first test.

  • Identify which router is providing DHCP addresses.
  • Avoid putting the camera on a guest network if the recorder cannot reach guest devices.
  • If a third-party router is connected to Starlink, confirm whether it is in router mode, access-point mode or a planned bypass design.
  • Keep the recorder's local address predictable with a supported DHCP reservation if you need to find it easily.
  • Do not expose a camera, recorder or router admin page to the public internet just to make remote access work.

If cameras are split across VLANs or separate routers, local recording may still be possible, but discovery and management need deliberate firewall and multicast rules. Prove the basic same-LAN design first.

Build a power plan

An internet outage and a power cut are different tests.

For a short power interruption, consider the equipment that must remain on together:

  • Cameras and their PoE switch or power injectors.
  • The recorder, storage and monitor if local viewing matters.
  • The Starlink router or the third-party router providing the LAN.
  • Any access point used by wireless cameras.
  • The Starlink dish and power supply if you also want internet service to continue.

A UPS can keep selected equipment running, but its runtime depends on the load. Do not assume that a router UPS will also power a PoE switch or camera. Label each power adapter, test the actual runtime, and keep an orderly shutdown plan for the recorder.

If cameras are battery-powered, check whether they continue recording without their cloud service and whether a low battery changes motion detection or night vision.

Test a Starlink internet outage safely

Test the system while someone is on site and while you can still reach the equipment locally.

Test local recording

  1. Confirm the camera clock, storage status and remaining capacity.
  2. Walk through the camera view and note the time.
  3. Leave the cameras, recorder and LAN powered.
  4. Make the Starlink internet path unavailable using a supported router control or a controlled WAN-disconnect method. On a third-party router, this may mean disabling the Starlink WAN. On an all-in-one Starlink setup, use the camera or router's documented offline test instead of repeatedly unplugging dish cables.
  5. Wait long enough for a motion event or scheduled recording.
  6. From a device still connected to the trusted LAN, open the recorder or camera locally.
  7. Export a short clip and confirm that its timestamp is sensible.
  8. Restore the Starlink path and check that the LAN and cameras reconnect without a reset.

Do not factory-reset the router, change the camera account or pull outdoor connectors as part of an outage test. The goal is to remove the internet path, not to create a hardware fault.

Test a power interruption

Repeat the test with the protected equipment on its intended UPS or backup supply:

  1. Confirm the recorder is writing video.
  2. Remove utility power from the protected equipment using the UPS test procedure.
  3. Check that the cameras and recorder remain available locally.
  4. Observe the recorder's response when the UPS battery becomes low.
  5. Restore power and confirm the recorder closes files cleanly and resumes recording.

If the LAN disappears as soon as Starlink internet is unavailable, the system is not locally resilient yet. Decide whether the router, access point or recorder needs a different power or network arrangement.

Plan alerts honestly

A local recording system can preserve footage without being able to contact you. For alerts that must reach someone away from the property, choose an independent path:

  • A camera or alarm service with a supported cellular connection.
  • A monitored alarm path that is separate from Starlink.
  • A second WAN such as cellular, configured and tested through the router.
  • A local siren or light for people near the property.

Do not call a cloud push notification a guaranteed alarm. Test what happens when Starlink is down, when the phone has no signal, and when the camera loses power. Keep emergency and life-safety decisions independent of a single consumer internet connection.

Check storage and timestamps

Before relying on the system, make a small outage record:

  • Camera name and physical location.
  • Local address or recorder channel.
  • Storage type, free space and overwrite policy.
  • Expected retention at the chosen resolution and frame rate.
  • Time zone and clock source.
  • Last successful exported clip.
  • What event should trigger a local recording.
  • Which alert path is expected to work without Starlink.

After an outage, look for gaps rather than only checking whether the camera appears online. Confirm the first and last recorded timestamps, storage health, and whether delayed cloud uploads created duplicates or missed events.

If local viewing fails

Work through the layers in order:

  1. Confirm the camera and recorder have power.
  2. Check that the viewing device is on the same trusted Wi-Fi or Ethernet network.
  3. Check the router's client list for the camera and recorder.
  4. Test the recorder's local interface by its documented address or hostname.
  5. If the address changed, check DHCP reservations and the correct MAC address.
  6. Check whether a guest network, VLAN or firewall rule blocks local traffic.
  7. Only after local access works, investigate the Starlink internet path and cloud service.

A camera that is offline locally has a power, Wi-Fi, LAN, storage or device problem. A camera that is reachable locally but absent from a cloud app has a separate internet or vendor-service problem.

Quick checklist

  • [ ] At least one camera can record locally without cloud access.
  • [ ] The recorder or SD card has free space and a known overwrite policy.
  • [ ] Cameras, recorder and a local viewing device share a trusted LAN.
  • [ ] Router, access point, recorder and camera power have been considered separately.
  • [ ] I tested local recording while Starlink internet was unavailable.
  • [ ] I exported and opened a test clip with a sensible timestamp.
  • [ ] I tested recovery after restoring the Starlink path.
  • [ ] I know which alerts fail without internet and which backup path replaces them.
  • [ ] I did not expose a camera or recorder directly to the internet.