Cameras · Troubleshooting guide
Verkada Camera Flashing Blue or Offline: Network Troubleshooting
Identify which blue indicator you are seeing, then check device identity, address assignment and cloud connectivity in order.
Draft · Nov 13, 2026 · 6 min read
Editorial review pending. This sample article demonstrates the design; verify model-specific instructions before use.
Before you start
Start by distinguishing the physical camera LED from the status icon in Command. A flashing-blue camera LED on supported generations can indicate loss of cloud connectivity; a flashing-blue Command icon indicates a firmware download or upgrade. Record the camera model and exact pattern before interpreting it.
Find the right troubleshooting path
| What you observe | What to investigate | Next check |
|---|---|---|
| Physical LED flashes blue | Cloud connection may be unavailable | Use the model-specific LED reference; check address and reachability. |
| Command icon flashes blue | Firmware download or upgrade | Observe progress; do not interrupt the update. |
| Blue/orange or red flash sequence | Model-specific diagnostic code | Record the full sequence rather than reporting only its color. |
| Solid blue camera; expected record offline | Device identity may not match | Compare the installed serial with the Command record. |
Use these observations to narrow the cause; they are not a definitive diagnosis.
Work through the checks
Identify the indicator and preserve the timeline
Record whether the light is on the device or in Command, its sequence, the model and when it changed. The LED reference includes different patterns for newer models. Keep power connected during a firmware update. A video of the physical sequence can be more useful to support than a description such as “blinking.”
Reference: Camera LED Status Indicators (opens in a new tab)Confirm you are troubleshooting the correct device
Match the serial on the installed camera to the Command record. Do not rely on the box label or a familiar display name. If the serial is wrong, resolve that mismatch first; moving cables cannot fix a record that points to another camera.
Reference: Troubleshoot Offline Camera (opens in a new tab)Check IP assignment, gateway and DNS
Have the network administrator locate the camera by MAC address. Confirm its IPv4 assignment, subnet, gateway and DNS, and compare these with the intended camera VLAN. Record whether the lease exists and whether the address matches the current network design. A working office laptop on another VLAN does not validate this path.
Reference: Camera Network Settings (opens in a new tab)Test the camera network against the current regional requirements
Use the linked camera network reference for the organization’s region. Ask the administrator to check endpoint access and any proxy or TLS inspection affecting the device. Run the Network Tester from the relevant network and retain the results. It tests the path where it runs, not every VLAN at the site.
Reference: Camera Network Settings (opens in a new tab)Make one controlled comparison
Arrange a maintenance window if a cable swap would interrupt coverage. Compare a known-good cable and compatible port, changing one variable at a time. If the result follows the device across a working path, provide that result to support rather than repeatedly resetting it.
Reference: Troubleshoot Offline Camera (opens in a new tab)Verify recovery without assuming history is already synchronized
Once the device reconnects, compare its serial with the same Command record and check live video. Network recovery and the availability of older footage are separate checks; synchronization can take time. If a specific interval remains unavailable, use the historical-playback guide and record the exact time range.
Reference: Camera Network Settings (opens in a new tab)
Verify the result
Confirm the same serial appears online, then open live video and review a recent interval of history. Record the restoration time and monitor for recurrence during the conditions that originally caused the outage.
If the issue remains
Give authorized support the model, serial, outage timeline, LED sequence, network test location and comparison results. State clearly whether one camera or a whole group is affected.
Official Verkada walkthrough
Watch the official tutorial
Official Verkada tutorial linked from the product documentation. Interface details may differ from your current Command version.
Official documentation
Sources checked November 13, 2026. Monarch’s diagnostic sequence combines these references with practical verification checks. Editorial review pending.
Join the conversation
Share what worked for you, or ask a follow-up. No account needed.
Network operations
I would add the VLAN to the test notes. Our laptop and the camera were taking different paths through the firewall.
Site technician
Matching the physical serial is now my first check after a camera replacement.