How to use LostaFound

Monitor refresh and statistics behavior

Choose a reporting period for request and location totals. Active IPs · 5 min always counts the last five minutes, including when the selected reporting period is shorter; it still respects the exact-IP filter. Watch alerts also use five minutes, across watched addresses. All figures use only retained events.
Refresh now or change filters to cancel a pending refresh and load the latest selection. A temporarily failed endpoint cancels the other endpoint and leaves the last complete snapshot marked stale; lost authorization clears it. Old responses cannot overwrite a newer snapshot. Pause cancels in-flight updates; manual Refresh now still works. Backgrounding stops requests and returning resumes automatic polling when enabled. Back-navigation from the browser cache also resumes it. An authorization failure clears displayed private statistics and requires signing in again and reloading.
A location pin uses the highest-request IP with valid coordinates in that named place, with a stable IP tie-break. Sorting or paging the IP table does not change that representative. Pins may change when the period or underlying request counts change. These remain approximate database estimates, not GPS. Missing map code or map errors leave statistics and a leading IP available; other addresses remain accessible in the paged IP table. Website, Android WebView and iPhone web-app screens use the same code on online reopen or Refresh.