A data gap in your weather station history means observations stopped reaching the server during that period. The gap might be 5 minutes or 5 hours, happen randomly or at the same time every day. Each pattern points to a different cause. This guide works through each one systematically.
Pattern 1 — Random Short Gaps (5–30 Minutes)
Random short gaps that occur unpredictably throughout the day are almost always caused by Wi-Fi connectivity drops between the gateway and your router. The gateway reconnects automatically after a short period, which is why the gap appears in history but the station seems "fine" when you check it.
Root causes: (1) 2.4 GHz channel congestion causing periodic interference — set your router to a fixed 2.4 GHz channel rather than auto. Check which channels neighbors are using with a Wi-Fi analyzer app and select the least congested of channels 1, 6, or 11. (2) Marginal signal strength — check RSSI in WSView Plus. Below -70 dBm will produce intermittent dropouts. Add a Wi-Fi extender or mesh node closer to the gateway. (3) Router DHCP lease renewals — some routers briefly disconnect devices when renewing IP leases. Assign a static IP address to your gateway's MAC address in your router's DHCP reservation settings to eliminate lease renewals entirely.
Pattern 2 — Daily Gap at the Same Time
A gap that appears at exactly the same time every day (e.g., always missing 3:00–3:15 AM) is almost always caused by an automated router reboot. Many ISP-provided routers are configured to reboot nightly during low-traffic hours for "maintenance." Check your router admin interface for a scheduled reboot setting and either disable it or change the time window to minimize impact. The gateway reconnects after the router comes back online, but the data during the router's downtime is lost.
Secondary cause of same-time gaps: ISP maintenance windows. Some internet providers briefly disconnect residential customers for network maintenance on a daily or weekly schedule. If your router admin shows no scheduled reboots, check whether your internet connection itself drops at that time by looking at your router's WAN connection log.
Pattern 3 — Long Gaps After Power Events
A gap that starts with a power outage or storm and doesn't resolve until someone manually intervenes means the gateway lost its Wi-Fi credentials or failed to reconnect automatically. Most modern gateways reconnect automatically after power restoration — if yours doesn't, check for a firmware update (older firmware versions had reconnection bugs) and ensure your router is fully online before the gateway tries to reconnect. If power outages are common at your location, a small UPS (uninterruptible power supply) for the gateway and router extends uptime through brief outages.
Pattern 4 — Gaps During Severe Weather
Data gaps that coincide with severe weather events usually mean the event physically affected the station (high winds, ice, lightning nearby). Check the station and sensors after the event for visible damage. Also check for: lightning-induced surge damage to the gateway (common even without a direct strike if surge protection isn't present), ice accumulation jamming anemometer or blocking the funnel, and bird or animal disturbance to sensors. A surge protector on the gateway's power supply is good practice in storm-prone areas.
Pattern 5 — Server-Side Gaps
Sometimes the gap is not a station problem — it's a platform outage. Weather Underground has experienced several significant outages over the years where data upload was accepted but not stored or displayed correctly. Ecowitt's cloud servers (ecowitt.net) have had brief outages. Before assuming your hardware has a problem, check whether the gap exists in your local station data (if you run WeeWX or have local data logging) versus only on the cloud platform. If local data is continuous but the cloud platform shows a gap, contact the platform's support.
Preventing Data Gaps Long-Term
- Static IP reservation: Assign your gateway a fixed IP in the router — eliminates DHCP-related reconnection issues.
- Fixed Wi-Fi channel: Prevents auto-channel changes from disrupting the connection.
- UPS on gateway and router: A $30–$50 mini UPS keeps both running through brief outages.
- Disable router auto-reboot: Check for and disable any scheduled nightly reboots.
- WeeWX as local backup: Running WeeWX on a Raspberry Pi gives you local data that persists even when cloud platforms have outages. See our WeeWX setup guide.
Frequently Asked Questions
For cloud platform gaps: if the data was never received by the server, it cannot be recovered — the gateway doesn't cache observations to retransmit later. For local storage gaps (WeeWX, console internal memory): Davis consoles store several months of 5-minute interval data internally. Ecowitt's GW2000 stores limited data in flash memory that can sometimes be retrieved via the console's SD card slot if one is installed. Most data gaps from connectivity issues are permanently lost unless you have local logging running independently of the cloud upload.
Not necessarily — the app uses local network access to the gateway, while Weather Underground requires the gateway to successfully upload to WU's servers. If you see data in the app but a gap on WU, the gateway is running but either not uploading to WU or WU isn't storing the uploads. Check the WU upload settings in WSView Plus (see our Ecowitt to WU guide) and verify your Station ID and Key are still correct — WU occasionally resets station keys during platform updates.