Connection locations and map
- Open Admin > IP monitor with Security permission. Top locations defaults to 20; choose any count from 1 to 100. Set Period in minutes from 1 to 10080 (7 days), then Refresh now. Recent contacts defaults to 100; choose any count from 1 to 1000. This caps the newest matching contact rows only, not location/IP totals or their pagination. Changing a control refreshes automatically. The same duration and exact-IP filter apply to the table and map, independently of IP pagination and sorting.
- Locations are ranked by retained PHP request count, not people or TCP connections. Several IPs in the same city/region/country are grouped. The table shows total requests, unique IPs, share of all requests, and an IP address(es) column with each address and its request count. Show all expands multiple addresses into 20-IP pages; the selected address page stays open during live refresh. Select an IP to fill the existing rule form, then separately confirm any rule change. Unknown-location IPs remain in the IP addresses table below. Unknown/private addresses remain in the overall totals and a separate unknown count, not an invented map location.
- City and region are approximate DB-IP Lite estimates. Country is the fallback when city details are missing. VPNs, proxies, mobile and anycast networks can show an exit location far from the person. This is not device GPS, a street address, ownership or identity proof; do not block users solely on a map estimate.
- The map uses the selected top locations; select a circle to see totals, drag to pan and zoom to separate nearby markers. Larger circles represent more requests. Places without valid coordinates remain in the table. The world outline and city lookup are local; no visitor IPs go to an outside geolocation or tile provider.
- Only the retained 7-day / 2 MiB request log is counted; busy logging can drop data or shorten coverage. Seven-day history accumulates after the update; previously expired contacts cannot be recovered. Check Earliest retained contact. Zero rows mean no retained matching requests, not proof there was no network traffic. Counts include monitoring requests and omit static files, other domains and host-rejected requests.
Open feature · All guides