Network QoS Dashboard

National Mobile Coverage & Data Quality Intelligence
Powered by IP Centric Systems

Use the administrator credentials configured in api/auth.php. HTTPS required.

Network QoS Dashboard

Pakistan · Islamabad default view · Mobile Coverage, Speed & Application Quality · Powered by IP Centric Systems
● LIVE SENSORSConnecting…
Existing records are shown for continuity; their Pakistan location is not independently verified.

Mobile RF Intelligence & Wi-Fi

Latest sensor readings from MariaDB. LTE/5G cells and Wi-Fi data appear only when supplied by a compatible Android sensor. No estimated values.

Loading sensor telemetry…
SensorOperatorTransportTechnologyRSRPRSRQSINRWi-Fi RSSIWi-Fi MHzCell band / PCILocation status

Network performance overview · historical Android and browser measurements

Loading all-time statistics from MariaDB…

Operator comparison · Android + browser; unidentified networks are not mobile operators

Measurement volume · daily readings (up to 90 latest days)

Application QoE · historical reachability across all operators

Historical figures include Android and browser tests. Browser operator labels are not SIM-verified; radio metrics are Android-only. The location, operator and technology controls below apply to the live-monitoring sections; use Historical Analytics for detailed historical operator/technology filters.

Live monitoring · most recent reading per sensor

Auto-refreshes every 5 seconds
Areas to analyse
Areas
Time range
Auto refresh: 5 seconds

Live mobile network performance · latest sensor readings · selected areas

Top applications · Application QoE on mobile data ·

Open full Application QoE →

Islamabad — Live Sensor Coverage Map · measurements received from Android devices

Loading geographic map…
Signal (RSRP) ≥ -90 dBm Good -90 to -100 Fair < -100 dBm Poor No RSRP

Live operator performance · latest sensor readings + recent app probes

Application availability by operator · selected areas ·

≥ 99% Good97–99% Degraded< 97% PoorFewer than 3 probes / no data

Area comparison · mobile performance next to app performance

Application metrics are measured by the Android sensors on mobile data: availability = the app's server answered over the cellular network (HTTP 2xx–4xx); response = time to the HTTP status including DNS, connection, TLS and server time. This shows reachability and speed of response, not full in-app experience. Application figures use the latest probes stored on the server (up to 300).

Historical Network Analytics · all stored readings

Operator averages combine Android and browser measurements with valid-sample weighting. Browser operator identification is not SIM-verified. Unidentified network is a separate category, not a mobile operator; radio metrics remain Android-only.

Loading MySQL history…

Network / operator performance · unidentified connections shown separately

Daily measurement volume · historical trend

Individual measurement records · most recent 200, averages above cover all matching records

Application QoE · original application logos retained

Loading application history…

Web Speed Tests · IP Centric Systems Servers

Browser-based network measurements stored in MariaDB. Unknown connections are labeled Unidentified network; operator selection is user-confirmed, not SIM-verified.

Run new web test

Open this section to load browser measurements.

Browser test history · latest 200 results

Application connectivity · browser HTTP probes, not native app QoE

Opaque browser responses indicate that a request completed; they do not prove application availability.

Compare · side by side · country, city or area

Time range
VS

Application QoE summary · last 24 hours · all areas

OperatorApplicationSamplesAvailabilityMedian msP95 msLast failure
Open this page to load the summary.

Recent probe results · selected areas and filters

SensorAreaOperatorApplicationTransportResponseHTTPReachableObserved (UTC)Error

Active application tests · WhatsApp, WhatsApp Business, YouTube, TikTok, Instagram, Facebook, X

Summary by application, test and operator

ApplicationTestOperatorRunsSuccessMedian timeLast failure
Open this page to load results.

Recent test results

Observed (UTC)SensorApplicationTestResultKey timeOperatorRSRPNetworkData used

Radio survey · drive/walk test samples uploaded from the phones

Per sensor

SensorOperatorSamplesLast sample (UTC)Avg RSRPWorst RSRPAvg SINRCells seenHandoversNo-service samples
Open this page to load the survey.

Latest samples

Observed (UTC)SensorOperatorTechRSRPRSRQSINRPCICellPositionEvent

Sensor registry · sensors that have reported data

Sensors appear automatically after their first upload. Provisioning uses the Sensor ID and token configured on the server.

Android Measurement Catalog

Availability varies by Android version, handset, permissions, carrier and measurement method. Voice-network KPIs are not exposed as general-purpose Android counters.

CategoryKPIs / MetadataCollection
Radio LTERSRP, RSRQ, RSSI, RSSNR/SINR, CQI, timing advanceDevice/API dependent
Radio 5GSS-RSRP, SS-RSRQ, SS-SINR, CSI metricsSupported devices only
Cell identityMCC, MNC, TAC, PCI, EARFCN/NRARFCN, Cell ID, band (derived)Location permissions / API
ConnectionOperator, RAT, roaming, registered cell, connectivity, transportAndroid APIs
Active testsDownload, upload, RTT, jitter, DNS, HTTP responseApp-generated tests
Device & locationGPS, timestamp, battery, device model, OS versionWith permission
QoS operationsHeartbeat, test success, offline gaps, measurement freshness, errorsSensor agent

Incidents & Alerts

Alerts are not implemented yet. No simulated incidents are shown.

Administration

Live Android telemetry is received through api/ingest.php and application probes through api/app-ingest.php, stored in the configured database. A sensor is shown offline after 180 seconds without uploads.

Application logos: place official logo files in assets/logos/ named whatsapp, youtube, facebook, instagram and x (.svg, .png or .webp). Logos are built in.