Aala Main 3
4020 tests (3626 successful) from 22/09/2026 17:26 to 11/11/2026 04:01. Average 88.3 Mbps down (min 0.6, max 118.8), 90.4 Mbps up, 4 ms ping.
All tests
showing 851–875 of 4020| Image | Time | Status | Down | Up | Ping | Loss | ISP / external IP | |
|---|---|---|---|---|---|---|---|---|
|
31/10/2026 23:162026-10-31T23:16:33+05:00 | ✓OK | 104.3 | 106.5 | 4 | 0.0% | Cybernet202.47.54.140 | |
|
31/10/2026 23:022026-10-31T23:02:26+05:00 | ✓OK | 101.8 | 104.1 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 22:462026-10-31T22:46:49+05:00 | ✓OK | 103.4 | 104.2 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 22:312026-10-31T22:31:29+05:00 | ✓OK | 103.0 | 105.7 | 4 | - | Cybernet202.47.54.140 | |
|
31/10/2026 22:172026-10-31T22:17:36+05:00 | ✓OK | 96.4 | 100.7 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 22:012026-10-31T22:01:30+05:00 | ✓OK | 103.6 | 104.7 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 21:472026-10-31T21:47:07+05:00 | ✓OK | 111.2 | 103.7 | 5 | 0.0% | Cybernet202.47.54.140 | |
|
31/10/2026 21:312026-10-31T21:31:58+05:00 | ✓OK | 103.5 | 104.4 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 21:172026-10-31T21:17:11+05:00 | ✓OK | 103.1 | 105.2 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 21:022026-10-31T21:02:30+05:00 | ✓OK | 109.1 | 104.5 | 5 | 0.0% | Cybernet202.47.54.140 | |
|
31/10/2026 20:462026-10-31T20:46:45+05:00 | ✓OK | 105.6 | 105.6 | 5 | 0.0% | Cybernet202.47.54.140 | |
|
31/10/2026 20:312026-10-31T20:31:41+05:00 | ✓OK | 107.3 | 105.3 | 5 | 0.0% | Cybernet202.47.54.140 | |
|
31/10/2026 20:162026-10-31T20:16:31+05:00 | ✓OK | 68.4 | 106.1 | 5 | - | Cybernet202.47.54.140 | |
|
31/10/2026 20:022026-10-31T20:02:07+05:00 | ✓OK | 104.2 | 104.0 | 4 | - | Cybernet202.47.54.140 | |
|
31/10/2026 19:462026-10-31T19:46:33+05:00 | ✓OK | 104.4 | 104.8 | 5 | 0.0% | Cybernet202.47.54.140 | |
|
31/10/2026 19:312026-10-31T19:31:32+05:00sent 17 min later | ✕No connection connected but no internet access | - | - | - | - | - | |
|
31/10/2026 19:162026-10-31T19:16:21+05:00 | ✕No connection connected but no internet access | - | - | - | - | - | |
|
31/10/2026 19:012026-10-31T19:01:24+05:00 | ✕No connection connected but no internet access | - | - | - | - | - | |
|
31/10/2026 18:462026-10-31T18:46:20+05:00 | ✕No connection connected but no internet access | - | - | - | - | - | |
|
31/10/2026 18:312026-10-31T18:31:15+05:00sent 17 min later | ✕No connection connected but no internet access | - | - | - | - | - | |
|
31/10/2026 18:162026-10-31T18:16:14+05:00 | ✕No connection connected but no internet access | - | - | - | - | - | |
|
31/10/2026 18:032026-10-31T18:03:23+05:00 | ✕No connection Error: Connection activation failed: The Wi-Fi network could not be fo | - | - | - | - | - | |
|
31/10/2026 17:472026-10-31T17:47:26+05:00 | ✕No connection the access point did not complete the connection in time [nmcli: Error | - | - | - | - | - | |
|
31/10/2026 17:322026-10-31T17:32:55+05:00 | ✕No connection Error: Connection activation failed: The Wi-Fi network could not be fo | - | - | - | - | - | |
|
31/10/2026 17:162026-10-31T17:16:24+05:00sent 18 min later | ✕No connection Error: Connection activation failed: The Wi-Fi network could not be fo | - | - | - | - | - |