URL Details: rsync://mirror.hafeezh.com/archlinux/
| URL: | rsync://mirror.hafeezh.com/archlinux/ |
|---|---|
| Mirror: | hafeezh.com |
| Protocol: | rsync |
| Country: | United Arab Emirates |
| IPv4: | Yes |
| IPv6: | No |
Check Logs
| Check Time | Check Location | Check IP | Last Sync | Delay (hh:mm) | Duration (s) | Success? | Error Message |
|---|---|---|---|---|---|---|---|
| 2025-04-26 16:00 | United Kingdom | 185.73.44.89 | 2025-04-26 15:09 | 0:50 | 5.53 | Yes | |
| 2025-04-26 15:59 | Hong Kong | 84.17.57.98 | 2025-04-26 13:09 | 2:50 | 1.94 | Yes | |
| 2025-04-26 15:25 | Czechia | 89.187.191.12 | 2025-04-26 13:09 | 2:16 | 1.93 | Yes | |
| 2025-04-26 15:07 | United States | 143.244.34.62 | 2025-04-26 13:09 | 1:58 | 3.21 | Yes | |
| 2025-04-26 14:54 | Germany | 78.46.209.220 | 2025-04-26 13:09 | 1:45 | 1.74 | Yes | |
| 2025-04-26 14:33 | United Kingdom | 185.73.44.89 | 2025-04-26 13:09 | 1:24 | 2.30 | Yes | |
| 2025-04-26 14:24 | Hong Kong | 84.17.57.98 | 2025-04-26 13:09 | 1:14 | 1.74 | Yes | |
| 2025-04-26 13:57 | United States | 143.244.34.62 | 2025-04-26 11:10 | 2:47 | 3.17 | Yes | |
| 2025-04-26 13:52 | Czechia | 89.187.191.12 | 2025-04-26 11:10 | 2:42 | 1.97 | Yes | |
| 2025-04-26 13:52 | Germany | 78.46.209.220 | 2025-04-26 11:10 | 2:42 | 1.67 | Yes | |
| 2025-04-26 13:09 | Hong Kong | 84.17.57.98 | 2025-04-26 11:10 | 1:59 | 2.09 | Yes | |
| 2025-04-26 12:41 | United Kingdom | 185.73.44.89 | 2025-04-26 11:10 | 1:31 | 5.49 | Yes | |
| 2025-04-26 12:25 | United States | 143.244.34.62 | 2025-04-26 11:10 | 1:15 | 3.16 | Yes | |
| 2025-04-26 12:17 | Germany | 78.46.209.220 | 2025-04-26 11:10 | 1:07 | 1.74 | Yes | |
| 2025-04-26 11:53 | Czechia | 89.187.191.12 | 2025-04-26 09:09 | 2:44 | 2.74 | Yes | |
| 2025-04-26 11:43 | Hong Kong | 84.17.57.98 | 2025-04-26 09:09 | 2:34 | 1.92 | Yes | |
| 2025-04-26 11:28 | United Kingdom | 185.73.44.89 | 2025-04-26 09:09 | 2:18 | 2.38 | Yes | |
| 2025-04-26 10:51 | United States | 143.244.34.62 | 2025-04-26 09:09 | 1:42 | 3.10 | Yes | |
| 2025-04-26 10:31 | Germany | 78.46.209.220 | 2025-04-26 09:09 | 1:22 | 1.72 | Yes | |
| 2025-04-26 10:21 | Czechia | 89.187.191.12 | 2025-04-26 09:09 | 1:12 | 2.01 | Yes | |
| 2025-04-26 10:18 | Hong Kong | 84.17.57.98 | 2025-04-26 09:09 | 1:09 | 1.98 | Yes | |
| 2025-04-26 09:29 | United Kingdom | 185.73.44.89 | 2025-04-26 07:10 | 2:19 | 4.69 | Yes | |
| 2025-04-26 09:21 | United States | 143.244.34.62 | 2025-04-26 07:10 | 2:11 | 3.21 | Yes | |
| 2025-04-26 08:52 | Czechia | 89.187.191.12 | 2025-04-26 07:10 | 1:42 | 2.10 | Yes | |
| 2025-04-26 08:33 | Germany | 78.46.209.220 | 2025-04-26 07:10 | 1:23 | 1.65 | Yes | |
| 2025-04-26 08:21 | Hong Kong | 84.17.57.98 | 2025-04-26 07:10 | 1:11 | 1.94 | Yes | |
| 2025-04-26 08:13 | United Kingdom | 185.73.44.89 | 2025-04-26 07:10 | 1:03 | 2.31 | Yes | |
| 2025-04-26 07:30 | United States | 143.244.34.62 | 2025-04-26 05:09 | 2:21 | 3.07 | Yes | |
| 2025-04-26 07:03 | Czechia | 89.187.191.12 | 2025-04-26 05:09 | 1:53 | 2.10 | Yes | |
| 2025-04-26 06:37 | Germany | 78.46.209.220 | 2025-04-26 05:09 | 1:28 | 4.19 | Yes | |
| 2025-04-26 06:22 | Hong Kong | 84.17.57.98 | 2025-04-26 05:09 | 1:12 | 11.26 | Yes | |
| 2025-04-26 06:20 | United Kingdom | 185.73.44.89 | 2025-04-26 05:09 | 1:11 | 2.29 | Yes | |
| 2025-04-26 05:37 | United States | 143.244.34.62 | 2025-04-26 03:10 | 2:27 | 3.04 | Yes | |
| 2025-04-26 05:28 | Germany | 78.46.209.220 | 2025-04-26 03:10 | 2:18 | 1.74 | Yes | |
| 2025-04-26 05:12 | Czechia | 89.187.191.12 | 2025-04-26 03:10 | 2:02 | 2.17 | Yes | |
| 2025-04-26 04:46 | Hong Kong | 84.17.57.98 | 2025-04-26 03:10 | 1:36 | 2.18 | Yes | |
| 2025-04-26 04:24 | United Kingdom | 185.73.44.89 | 2025-04-26 03:10 | 1:14 | 4.75 | Yes | |
| 2025-04-26 03:57 | United States | 143.244.34.62 | 2025-04-26 01:09 | 2:47 | 3.08 | Yes | |
| 2025-04-26 03:48 | Germany | 78.46.209.220 | 2025-04-26 01:09 | 2:39 | 1.75 | Yes | |
| 2025-04-26 03:14 | Czechia | 89.187.191.12 | 2025-04-26 01:09 | 2:04 | 1.96 | Yes | |
| 2025-04-26 03:06 | Hong Kong | 84.17.57.98 | 2025-04-26 01:09 | 1:57 | 1.77 | Yes | |
| 2025-04-26 02:34 | United Kingdom | 185.73.44.89 | 2025-04-26 01:09 | 1:25 | 4.79 | Yes | |
| 2025-04-26 02:08 | United States | 143.244.34.62 | 2025-04-26 01:09 | 0:58 | 3.91 | Yes | |
| 2025-04-26 01:48 | Germany | 78.46.209.220 | 2025-04-25 23:09 | 2:38 | 1.79 | Yes | |
| 2025-04-26 01:45 | Hong Kong | 84.17.57.98 | 2025-04-25 23:09 | 2:35 | 1.78 | Yes | |
| 2025-04-26 01:28 | Czechia | 89.187.191.12 | 2025-04-25 23:09 | 2:19 | 2.07 | Yes | |
| 2025-04-26 00:57 | United Kingdom | 185.73.44.89 | 2025-04-25 23:09 | 1:48 | 3.12 | Yes | |
| 2025-04-26 00:46 | United States | 143.244.34.62 | 2025-04-25 23:09 | 1:37 | 3.12 | Yes | |
| 2025-04-26 00:42 | Hong Kong | 84.17.57.98 | 2025-04-25 23:09 | 1:32 | 1.74 | Yes | |
| 2025-04-26 00:13 | Czechia | 89.187.191.12 | 2025-04-25 23:09 | 1:04 | 1.95 | Yes | |
| 2025-04-25 23:52 | Germany | 78.46.209.220 | 2025-04-25 21:10 | 2:42 | 2.81 | Yes | |
| 2025-04-25 23:30 | United Kingdom | 185.73.44.89 | 2025-04-25 21:10 | 2:20 | 3.95 | Yes | |
| 2025-04-25 23:25 | United States | 143.244.34.62 | 2025-04-25 21:10 | 2:15 | 3.10 | Yes | |
| 2025-04-25 22:59 | Czechia | 89.187.191.12 | 2025-04-25 21:10 | 1:49 | 2.02 | Yes | |
| 2025-04-25 22:47 | Hong Kong | 84.17.57.98 | 2025-04-25 21:10 | 1:37 | 2.23 | Yes | |
| 2025-04-25 22:33 | Germany | 78.46.209.220 | 2025-04-25 21:10 | 1:23 | 1.94 | Yes | |
| 2025-04-25 22:10 | United States | 143.244.34.62 | 2025-04-25 21:10 | 1:00 | 3.18 | Yes | |
| 2025-04-25 21:55 | United Kingdom | 185.73.44.89 | 2025-04-25 19:09 | 2:46 | 2.42 | Yes | |
| 2025-04-25 21:22 | Hong Kong | 84.17.57.98 | 2025-04-25 19:09 | 2:13 | 1.83 | Yes | |
| 2025-04-25 21:02 | Germany | 78.46.209.220 | 2025-04-25 19:09 | 1:53 | 1.72 | Yes | |
| 2025-04-25 20:59 | Czechia | 89.187.191.12 | 2025-04-25 19:09 | 1:50 | 2.06 | Yes | |
| 2025-04-25 20:41 | United States | 143.244.34.62 | 2025-04-25 19:09 | 1:32 | 3.41 | Yes | |
| 2025-04-25 19:59 | United Kingdom | 185.73.44.89 | 2025-04-25 17:10 | 2:49 | 2.29 | Yes | |
| 2025-04-25 19:58 | Hong Kong | 84.17.57.98 | 2025-04-25 17:10 | 2:48 | 2.18 | Yes | |
| 2025-04-25 19:53 | Czechia | 89.187.191.12 | 2025-04-25 17:10 | 2:43 | 1.98 | Yes | |
| 2025-04-25 19:42 | Germany | 78.46.209.220 | 2025-04-25 17:10 | 2:32 | 1.84 | Yes | |
| 2025-04-25 19:18 | United States | 143.244.34.62 | 2025-04-25 17:10 | 2:08 | 3.13 | Yes | |
| 2025-04-25 18:49 | Hong Kong | 84.17.57.98 | 2025-04-25 17:10 | 1:39 | 2.17 | Yes | |
| 2025-04-25 18:27 | United Kingdom | 185.73.44.89 | 2025-04-25 17:10 | 1:17 | 2.30 | Yes | |
| 2025-04-25 18:18 | Czechia | 89.187.191.12 | 2025-04-25 17:10 | 1:08 | 1.98 | Yes | |
| 2025-04-25 17:47 | Germany | 78.46.209.220 | 2025-04-25 15:10 | 2:37 | 1.67 | Yes | |
| 2025-04-25 17:32 | Hong Kong | 84.17.57.98 | 2025-04-25 15:10 | 2:22 | 2.22 | Yes | |
| 2025-04-25 17:30 | United States | 143.244.34.62 | 2025-04-25 15:10 | 2:20 | 3.85 | Yes | |
| 2025-04-25 16:53 | Czechia | 89.187.191.12 | 2025-04-25 15:10 | 1:43 | 2.03 | Yes | |
| 2025-04-25 16:29 | United Kingdom | 185.73.44.89 | 2025-04-25 15:10 | 1:19 | 4.73 | Yes | |
| 2025-04-25 16:28 | United States | 143.244.34.62 | 2025-04-25 15:10 | 1:18 | 3.21 | Yes | |
| 2025-04-25 16:26 | Germany | 78.46.209.220 | 2025-04-25 15:10 | 1:16 | 1.74 | Yes | |
| 2025-04-25 16:16 | Hong Kong | 84.17.57.98 | 2025-04-25 15:10 | 1:06 | 2.00 | Yes | |
| 2025-04-25 15:19 | United States | 143.244.34.62 | 2025-04-25 13:09 | 2:10 | 3.72 | Yes | |
| 2025-04-25 15:14 | Czechia | 89.187.191.12 | 2025-04-25 13:09 | 2:05 | 1.99 | Yes | |
| 2025-04-25 15:10 | Germany | 78.46.209.220 | 2025-04-25 13:09 | 2:01 | 1.75 | Yes | |
| 2025-04-25 14:30 | United Kingdom | 185.73.44.89 | 2025-04-25 13:09 | 1:21 | 3.07 | Yes | |
| 2025-04-25 14:09 | Hong Kong | 84.17.57.98 | 2025-04-25 13:09 | 1:00 | 1.87 | Yes | |
| 2025-04-25 14:01 | Czechia | 89.187.191.12 | 2025-04-25 13:09 | 0:52 | 2.89 | Yes | |
| 2025-04-25 13:53 | Germany | 78.46.209.220 | 2025-04-25 11:09 | 2:44 | 1.77 | Yes | |
| 2025-04-25 13:26 | United Kingdom | 185.73.44.89 | 2025-04-25 11:09 | 2:17 | 4.63 | Yes | |
| 2025-04-25 13:24 | United States | 143.244.34.62 | 2025-04-25 11:09 | 2:15 | 3.14 | Yes | |
| 2025-04-25 12:52 | Germany | 78.46.209.220 | 2025-04-25 11:09 | 1:43 | 1.73 | Yes | |
| 2025-04-25 12:12 | Hong Kong | 84.17.57.98 | 2025-04-25 11:09 | 1:03 | 1.77 | Yes | |
| 2025-04-25 12:10 | Czechia | 89.187.191.12 | 2025-04-25 11:09 | 1:01 | 1.97 | Yes | |
| 2025-04-25 11:57 | United States | 143.244.34.62 | 2025-04-25 09:10 | 2:47 | 3.98 | Yes | |
| 2025-04-25 11:46 | United Kingdom | 185.73.44.89 | 2025-04-25 09:10 | 2:36 | 2.33 | Yes | |
| 2025-04-25 11:24 | Germany | 78.46.209.220 | 2025-04-25 09:10 | 2:14 | 1.77 | Yes | |
| 2025-04-25 10:54 | United States | 143.244.34.62 | 2025-04-25 09:10 | 1:44 | 3.11 | Yes | |
| 2025-04-25 10:40 | Hong Kong | 84.17.57.98 | 2025-04-25 09:10 | 1:30 | 2.26 | Yes | |
| 2025-04-25 10:31 | United Kingdom | 185.73.44.89 | 2025-04-25 09:10 | 1:21 | 3.96 | Yes | |
| 2025-04-25 10:22 | Czechia | 89.187.191.12 | 2025-04-25 09:10 | 1:12 | 2.04 | Yes | |
| 2025-04-25 09:40 | United States | 143.244.34.62 | 2025-04-25 07:09 | 2:31 | 3.16 | Yes | |
| 2025-04-25 09:38 | Germany | 78.46.209.220 | 2025-04-25 07:09 | 2:29 | 2.55 | Yes | |
| 2025-04-25 09:35 | Hong Kong | 84.17.57.98 | 2025-04-25 07:09 | 2:25 | 1.87 | Yes | |
| 2025-04-25 09:18 | Czechia | 89.187.191.12 | 2025-04-25 07:09 | 2:09 | 2.16 | Yes | |
| 2025-04-25 08:44 | United Kingdom | 185.73.44.89 | 2025-04-25 07:09 | 1:34 | 4.94 | Yes | |
| 2025-04-25 08:27 | United States | 143.244.34.62 | 2025-04-25 07:09 | 1:18 | 3.19 | Yes | |
| 2025-04-25 08:08 | Germany | 78.46.209.220 | 2025-04-25 07:09 | 0:58 | 1.74 | Yes | |
| 2025-04-25 08:08 | Czechia | 89.187.191.12 | 2025-04-25 07:09 | 0:58 | 2.03 | Yes | |
| 2025-04-25 07:34 | United Kingdom | 185.73.44.89 | 2025-04-25 05:10 | 2:24 | 2.35 | Yes | |
| 2025-04-25 06:43 | United States | 143.244.34.62 | 2025-04-25 05:10 | 1:33 | 3.19 | Yes | |
| 2025-04-25 06:40 | Czechia | 89.187.191.12 | 2025-04-25 05:10 | 1:30 | 1.92 | Yes | |
| 2025-04-25 06:30 | Hong Kong | 84.17.57.98 | 2025-04-25 05:10 | 1:20 | 2.00 | Yes | |
| 2025-04-25 06:11 | Germany | 78.46.209.220 | 2025-04-25 05:10 | 1:01 | 1.75 | Yes | |
| 2025-04-25 05:54 | United Kingdom | 185.73.44.89 | 2025-04-25 03:10 | 2:44 | 2.30 | Yes | |
| 2025-04-25 05:39 | United States | 143.244.34.62 | 2025-04-25 03:10 | 2:29 | 3.15 | Yes | |
| 2025-04-25 05:35 | Czechia | 89.187.191.12 | 2025-04-25 03:10 | 2:25 | 1.93 | Yes | |
| 2025-04-25 05:00 | Hong Kong | 84.17.57.98 | 2025-04-25 03:10 | 1:50 | 2.04 | Yes | |
| 2025-04-25 04:43 | Germany | 78.46.209.220 | 2025-04-25 03:10 | 1:33 | 1.71 | Yes | |
| 2025-04-25 04:20 | United Kingdom | 185.73.44.89 | 2025-04-25 03:10 | 1:10 | 2.25 | Yes | |
| 2025-04-25 04:06 | Czechia | 89.187.191.12 | 2025-04-25 03:10 | 0:56 | 1.95 | Yes | |
| 2025-04-25 03:51 | United States | 143.244.34.62 | 2025-04-25 01:09 | 2:42 | 3.13 | Yes | |
| 2025-04-25 03:22 | Hong Kong | 84.17.57.98 | 2025-04-25 01:09 | 2:13 | 2.11 | Yes | |
| 2025-04-25 03:06 | Czechia | 89.187.191.12 | 2025-04-25 01:09 | 1:57 | 1.98 | Yes | |
| 2025-04-25 03:02 | Germany | 78.46.209.220 | 2025-04-25 01:09 | 1:53 | 1.81 | Yes | |
| 2025-04-25 02:51 | United States | 143.244.34.62 | 2025-04-25 01:09 | 1:42 | 3.29 | Yes | |
| 2025-04-25 02:27 | United Kingdom | 185.73.44.89 | 2025-04-25 01:09 | 1:18 | 2.31 | Yes | |
| 2025-04-25 01:56 | Hong Kong | 84.17.57.98 | 2025-04-24 23:10 | 2:46 | 1.87 | Yes | |
| 2025-04-25 01:18 | Germany | 78.46.209.220 | 2025-04-24 23:10 | 2:08 | 1.66 | Yes | |
| 2025-04-25 01:16 | Czechia | 89.187.191.12 | 2025-04-24 23:10 | 2:06 | 2.09 | Yes | |
| 2025-04-25 01:09 | United States | 143.244.34.62 | 2025-04-24 23:10 | 1:59 | 3.13 | Yes | |
| 2025-04-25 01:03 | United Kingdom | 185.73.44.89 | 2025-04-24 23:10 | 1:53 | 3.92 | Yes | |
| 2025-04-25 00:41 | Hong Kong | 84.17.57.98 | 2025-04-24 23:10 | 1:31 | 2.35 | Yes | |
| 2025-04-25 00:10 | Czechia | 89.187.191.12 | 2025-04-24 23:10 | 1:00 | 2.07 | Yes | |
| 2025-04-25 00:08 | United States | 143.244.34.62 | 2025-04-24 23:10 | 0:58 | 7.28 | Yes | |
| 2025-04-24 23:56 | United Kingdom | 185.73.44.89 | 2025-04-24 21:10 | 2:46 | 4.15 | Yes | |
| 2025-04-24 23:37 | Germany | 78.46.209.220 | 2025-04-24 21:10 | 2:27 | 1.75 | Yes | |
| 2025-04-24 23:35 | Hong Kong | 84.17.57.98 | 2025-04-24 21:10 | 2:25 | 2.36 | Yes | |
| 2025-04-24 22:54 | United States | 143.244.34.62 | 2025-04-24 21:10 | 1:44 | 3.07 | Yes | |
| 2025-04-24 22:36 | Czechia | 89.187.191.12 | 2025-04-24 21:10 | 1:26 | 1.95 | Yes | |
| 2025-04-24 22:28 | Hong Kong | 84.17.57.98 | 2025-04-24 21:10 | 1:18 | 1.87 | Yes | |
| 2025-04-24 22:08 | Germany | 78.46.209.220 | 2025-04-24 21:10 | 0:58 | 2.03 | Yes | |
| 2025-04-24 22:02 | United Kingdom | 185.73.44.89 | 2025-04-24 21:10 | 0:52 | 2.27 | Yes | |
| 2025-04-24 21:41 | United States | 143.244.34.62 | 2025-04-24 19:09 | 2:31 | 3.26 | Yes | |
| 2025-04-24 21:33 | Czechia | 89.187.191.12 | 2025-04-24 19:09 | 2:24 | 2.75 | Yes | |
| 2025-04-24 21:05 | Germany | 78.46.209.220 | 2025-04-24 19:09 | 1:56 | 1.89 | Yes | |
| 2025-04-24 20:58 | United Kingdom | 185.73.44.89 | 2025-04-24 19:09 | 1:49 | 3.88 | Yes | |
| 2025-04-24 20:45 | Hong Kong | 84.17.57.98 | 2025-04-24 19:09 | 1:35 | 1.81 | Yes | |
| 2025-04-24 20:37 | United States | 143.244.34.62 | 2025-04-24 19:09 | 1:28 | 3.31 | Yes | |
| 2025-04-24 20:04 | Czechia | 89.187.191.12 | 2025-04-24 19:09 | 0:55 | 2.93 | Yes | |
| 2025-04-24 19:51 | United Kingdom | 185.73.44.89 | 2025-04-24 17:10 | 2:41 | 2.44 | Yes | |
| 2025-04-24 19:30 | United States | 143.244.34.62 | 2025-04-24 17:10 | 2:20 | 3.06 | Yes | |
| 2025-04-24 19:22 | Germany | 78.46.209.220 | 2025-04-24 17:10 | 2:12 | 3.47 | Yes | |
| 2025-04-24 19:16 | Hong Kong | 84.17.57.98 | 2025-04-24 17:10 | 2:06 | 1.89 | Yes | |
| 2025-04-24 18:47 | Czechia | 89.187.191.12 | 2025-04-24 17:10 | 1:37 | 2.00 | Yes | |
| 2025-04-24 18:08 | United Kingdom | 185.73.44.89 | 2025-04-24 17:10 | 0:58 | 2.28 | Yes | |
| 2025-04-24 18:04 | United States | 143.244.34.62 | 2025-04-24 17:10 | 0:54 | 3.98 | Yes | |
| 2025-04-24 17:44 | Germany | 78.46.209.220 | 2025-04-24 15:09 | 2:35 | 1.76 | Yes | |
| 2025-04-24 17:19 | Hong Kong | 84.17.57.98 | 2025-04-24 15:09 | 2:10 | 2.77 | Yes | |
| 2025-04-24 17:18 | Czechia | 89.187.191.12 | 2025-04-24 15:09 | 2:09 | 2.16 | Yes | |
| 2025-04-24 16:55 | United States | 143.244.34.62 | 2025-04-24 15:09 | 1:46 | 3.24 | Yes | |
| 2025-04-24 16:36 | United Kingdom | 185.73.44.89 | 2025-04-24 15:09 | 1:27 | 2.54 | Yes | |
| 2025-04-24 16:13 | Hong Kong | 84.17.57.98 | 2025-04-24 15:09 | 1:03 | 2.31 | Yes | |
| 2025-04-24 16:08 | Germany | 78.46.209.220 | 2025-04-24 15:09 | 0:59 | 1.74 | Yes | |
| 2025-04-24 15:44 | Czechia | 89.187.191.12 | 2025-04-24 13:10 | 2:34 | 1.86 | Yes | |
| 2025-04-24 15:32 | United States | 143.244.34.62 | 2025-04-24 13:10 | 2:22 | 3.52 | Yes | |
| 2025-04-24 15:30 | United Kingdom | 185.73.44.89 | 2025-04-24 13:10 | 2:20 | 2.28 | Yes | |
| 2025-04-24 14:55 | Germany | 78.46.209.220 | 2025-04-24 13:10 | 1:45 | 1.79 | Yes | |
| 2025-04-24 14:36 | Hong Kong | 84.17.57.98 | 2025-04-24 13:10 | 1:26 | 3.49 | Yes | |
| 2025-04-24 14:23 | Czechia | 89.187.191.12 | 2025-04-24 13:10 | 1:13 | 2.87 | Yes | |
| 2025-04-24 13:51 | United Kingdom | 185.73.44.89 | 2025-04-24 11:09 | 2:41 | 2.31 | Yes | |
| 2025-04-24 13:39 | United States | 143.244.34.62 | 2025-04-24 11:09 | 2:29 | 3.07 | Yes | |
| 2025-04-24 13:32 | Hong Kong | 84.17.57.98 | 2025-04-24 11:09 | 2:23 | 2.68 | Yes | |
| 2025-04-24 13:03 | Germany | 78.46.209.220 | 2025-04-24 11:09 | 1:53 | 1.73 | Yes | |
| 2025-04-24 12:37 | Czechia | 89.187.191.12 | 2025-04-24 11:09 | 1:27 | 2.04 | Yes | |
| 2025-04-24 12:27 | United Kingdom | 185.73.44.89 | 2025-04-24 11:09 | 1:18 | 2.28 | Yes | |
| 2025-04-24 12:06 | Hong Kong | 84.17.57.98 | 2025-04-24 11:09 | 0:56 | 2.27 | Yes | |
| 2025-04-24 12:01 | Germany | 78.46.209.220 | 2025-04-24 11:09 | 0:52 | 1.80 | Yes | |
| 2025-04-24 11:53 | United States | 143.244.34.62 | 2025-04-24 09:10 | 2:43 | 3.12 | Yes | |
| 2025-04-24 11:22 | United Kingdom | 185.73.44.89 | 2025-04-24 09:10 | 2:12 | 2.35 | Yes | |
| 2025-04-24 11:12 | Czechia | 89.187.191.12 | 2025-04-24 09:10 | 2:02 | 1.99 | Yes | |
| 2025-04-24 10:49 | Hong Kong | 84.17.57.98 | 2025-04-24 09:10 | 1:39 | 1.92 | Yes | |
| 2025-04-24 10:21 | Germany | 78.46.209.220 | 2025-04-24 09:10 | 1:11 | 1.74 | Yes | |
| 2025-04-24 10:01 | United States | 143.244.34.62 | 2025-04-24 09:10 | 0:51 | 3.03 | Yes | |
| 2025-04-24 09:59 | Czechia | 89.187.191.12 | 2025-04-24 07:09 | 2:49 | 2.82 | Yes | |
| 2025-04-24 09:40 | United Kingdom | 185.73.44.89 | 2025-04-24 07:09 | 2:30 | 2.31 | Yes | |
| 2025-04-24 09:15 | Hong Kong | 84.17.57.98 | 2025-04-24 07:09 | 2:05 | 1.82 | Yes | |
| 2025-04-24 08:37 | United States | 143.244.34.62 | 2025-04-24 07:09 | 1:27 | 4.01 | Yes | |
| 2025-04-24 08:22 | Germany | 78.46.209.220 | 2025-04-24 07:09 | 1:12 | 1.75 | Yes | |
| 2025-04-24 08:13 | Czechia | 89.187.191.12 | 2025-04-24 07:09 | 1:04 | 2.11 | Yes | |
| 2025-04-24 07:59 | United Kingdom | 185.73.44.89 | 2025-04-24 05:10 | 2:48 | 4.66 | Yes | |
| 2025-04-24 07:33 | Hong Kong | 84.17.57.98 | 2025-04-24 05:10 | 2:23 | 1.88 | Yes | |
| 2025-04-24 07:08 | Germany | 78.46.209.220 | 2025-04-24 05:10 | 1:58 | 1.80 | Yes | |
| 2025-04-24 06:56 | United States | 143.244.34.62 | 2025-04-24 05:10 | 1:46 | 3.14 | Yes | |
| 2025-04-24 06:19 | Czechia | 89.187.191.12 | 2025-04-24 05:10 | 1:09 | 2.12 | Yes | |
| 2025-04-24 06:17 | United Kingdom | 185.73.44.89 | 2025-04-24 05:10 | 1:07 | 2.26 | Yes | |
| 2025-04-24 06:06 | Hong Kong | 84.17.57.98 | 2025-04-24 05:10 | 0:56 | 1.99 | Yes | |
| 2025-04-24 05:25 | United States | 143.244.34.62 | 2025-04-24 03:09 | 2:16 | 3.13 | Yes | |
| 2025-04-24 05:18 | Germany | 78.46.209.220 | 2025-04-24 03:09 | 2:09 | 1.79 | Yes | |
| 2025-04-24 05:13 | Czechia | 89.187.191.12 | 2025-04-24 03:09 | 2:04 | 1.97 | Yes | |
| 2025-04-24 04:26 | United Kingdom | 185.73.44.89 | 2025-04-24 03:09 | 1:16 | 2.30 | Yes | |
| 2025-04-24 04:12 | Hong Kong | 84.17.57.98 | 2025-04-24 03:09 | 1:03 | 1.81 | Yes | |
| 2025-04-24 04:11 | United States | 143.244.34.62 | 2025-04-24 03:09 | 1:01 | 3.14 | Yes | |
| 2025-04-24 03:29 | Czechia | 89.187.191.12 | 2025-04-24 01:10 | 2:19 | 2.04 | Yes | |
| 2025-04-24 03:24 | Germany | 78.46.209.220 | 2025-04-24 01:10 | 2:14 | 1.79 | Yes | |
| 2025-04-24 02:48 | Hong Kong | 84.17.57.98 | 2025-04-24 01:10 | 1:38 | 1.85 | Yes | |
| 2025-04-24 02:46 | United States | 143.244.34.62 | 2025-04-24 01:10 | 1:36 | 3.27 | Yes | |
| 2025-04-24 02:33 | United Kingdom | 185.73.44.89 | 2025-04-24 01:10 | 1:23 | 3.06 | Yes | |
| 2025-04-24 02:04 | Germany | 78.46.209.220 | 2025-04-24 01:10 | 0:54 | 1.71 | Yes | |
| 2025-04-24 01:53 | Czechia | 89.187.191.12 | 2025-04-23 23:09 | 2:43 | 1.99 | Yes | |
| 2025-04-24 01:26 | United Kingdom | 185.73.44.89 | 2025-04-23 23:09 | 2:16 | 2.29 | Yes | |
| 2025-04-24 01:24 | Hong Kong | 84.17.57.98 | 2025-04-23 23:09 | 2:15 | 2.14 | Yes | |
| 2025-04-24 00:56 | Germany | 78.46.209.220 | 2025-04-23 23:09 | 1:46 | 1.56 | Yes | |
| 2025-04-24 00:55 | United States | 143.244.34.62 | 2025-04-23 23:09 | 1:46 | 3.21 | Yes | |
| 2025-04-24 00:19 | Hong Kong | 84.17.57.98 | 2025-04-23 23:09 | 1:09 | 1.94 | Yes | |
| 2025-04-24 00:06 | Czechia | 89.187.191.12 | 2025-04-23 23:09 | 0:57 | 2.08 | Yes | |
| 2025-04-23 23:56 | United Kingdom | 185.73.44.89 | 2025-04-23 21:10 | 2:46 | 2.29 | Yes | |
| 2025-04-23 23:24 | United States | 143.244.34.62 | 2025-04-23 21:10 | 2:14 | 3.19 | Yes | |
| 2025-04-23 23:05 | Germany | 78.46.209.220 | 2025-04-23 21:10 | 1:55 | 1.76 | Yes | |
| 2025-04-23 23:03 | Hong Kong | 84.17.57.98 | 2025-04-23 21:10 | 1:53 | 1.75 | Yes | |
| 2025-04-23 22:54 | United Kingdom | 185.73.44.89 | 2025-04-23 21:10 | 1:44 | 4.72 | Yes | |
| 2025-04-23 22:41 | Czechia | 89.187.191.12 | 2025-04-23 21:10 | 1:31 | 2.06 | Yes | |
| 2025-04-23 21:43 | United States | 143.244.34.62 | 2025-04-23 19:10 | 2:33 | 3.27 | Yes | |
| 2025-04-23 21:42 | Germany | 78.46.209.220 | 2025-04-23 19:10 | 2:32 | 1.89 | Yes | |
| 2025-04-23 21:24 | Czechia | 89.187.191.12 | 2025-04-23 19:10 | 2:14 | 1.96 | Yes | |
| 2025-04-23 21:09 | Hong Kong | 84.17.57.98 | 2025-04-23 19:10 | 1:59 | 1.86 | Yes | |
| 2025-04-23 20:57 | United Kingdom | 185.73.44.89 | 2025-04-23 19:10 | 1:47 | 2.28 | Yes | |
| 2025-04-23 20:42 | United States | 143.244.34.62 | 2025-04-23 19:10 | 1:32 | 3.18 | Yes | |
| 2025-04-23 20:20 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 19:41 | United States | 143.244.34.62 | 2025-04-17 05:09 | 158:32 | 3.09 | Yes | |
| 2025-04-23 19:31 | Czechia | 89.187.191.12 | 2025-04-17 05:09 | 158:22 | 2.02 | Yes | |
| 2025-04-23 19:26 | Hong Kong | 84.17.57.98 | 2025-04-17 05:09 | 158:17 | 1.85 | Yes | |
| 2025-04-23 19:00 | United Kingdom | 185.73.44.89 | 2025-04-17 05:09 | 157:51 | 2.35 | Yes | |
| 2025-04-23 18:38 | United States | 143.244.34.62 | 3.04 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (176.205.75.110): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-23 18:36 | Germany | 78.46.209.220 | 1.36 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (176.205.75.110): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-23 17:46 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 17:35 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 17:29 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 17:15 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 16:53 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 15:59 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 15:50 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 15:47 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 15:40 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 15:40 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 14:56 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 14:38 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 14:36 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 14:24 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 14:06 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 13:51 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 13:11 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 13:07 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 12:38 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 12:34 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 12:15 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 12:11 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 11:37 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 11:07 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 11:04 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 11:02 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 10:35 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 09:56 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 09:54 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 09:20 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 09:11 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 09:04 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 08:39 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 08:09 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 08:05 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 07:36 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 07:27 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 06:49 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 06:43 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 06:21 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 06:19 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 05:53 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 05:27 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 05:23 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 04:52 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 04:48 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 04:37 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 03:56 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 03:35 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 03:29 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 02:54 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 02:48 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 02:48 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 02:00 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 01:55 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 01:49 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 01:37 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 01:23 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 00:15 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 00:12 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-23 00:02 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 23:50 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 23:49 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 22:32 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 22:30 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 22:22 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 22:14 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 22:09 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 21:22 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 21:03 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 20:59 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 20:39 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 20:17 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 19:55 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 19:50 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 19:13 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 19:01 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 18:42 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 18:24 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 18:22 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 18:08 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 17:23 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 17:01 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 16:43 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 16:35 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 16:29 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 16:00 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 15:43 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 15:23 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 15:18 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 14:37 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 14:29 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 14:17 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 13:56 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 13:48 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 13:05 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 12:56 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 12:56 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 12:31 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 12:18 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 11:42 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 11:30 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 11:28 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 11:12 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 10:29 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 10:10 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 10:10 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 09:59 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 09:43 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 09:07 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 09:01 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 08:17 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 08:16 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 08:07 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 07:21 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 07:17 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 06:34 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 06:21 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 06:18 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 06:01 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 05:44 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 05:16 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 05:00 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 04:40 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 04:36 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 04:29 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 03:30 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 03:20 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 03:19 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 03:03 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 02:54 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 01:55 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 01:42 | United Kingdom | 185.73.44.89 | 0.14 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-22 01:42 | Czechia | 89.187.191.12 | 0.14 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-22 01:39 | Hong Kong | 84.17.57.98 | 0.12 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-22 01:21 | United States | 143.244.34.62 | 0.24 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-22 00:39 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 00:15 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-22 00:12 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 23:59 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 23:44 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 23:29 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 22:31 | United States | 143.244.34.62 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 22:24 | Hong Kong | 84.17.57.98 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 22:16 | Czechia | 89.187.191.12 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 22:06 | United Kingdom | 185.73.44.89 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 22:05 | Germany | 78.46.209.220 | No | rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.4.1] | |||
| 2025-04-21 21:25 | United States | 143.244.34.62 | 1.90 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 21:16 | Hong Kong | 84.17.57.98 | 2.14 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 20:35 | United Kingdom | 185.73.44.89 | 1.51 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 20:25 | Czechia | 89.187.191.12 | 1.43 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 20:10 | Germany | 78.46.209.220 | 2.88 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 19:41 | Hong Kong | 84.17.57.98 | 2.92 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 19:39 | United States | 143.244.34.62 | 0.38 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 18:57 | Germany | 78.46.209.220 | 0.16 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 18:39 | Czechia | 89.187.191.12 | 2.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 18:39 | United Kingdom | 185.73.44.89 | 1.07 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 18:20 | Hong Kong | 84.17.57.98 | 1.06 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 18:14 | United States | 143.244.34.62 | 3.28 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 17:38 | Germany | 78.46.209.220 | 2.80 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 17:17 | Czechia | 89.187.191.12 | 2.55 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 17:10 | United States | 143.244.34.62 | 3.25 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 16:59 | Hong Kong | 84.17.57.98 | 1.60 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 16:57 | United Kingdom | 185.73.44.89 | 3.02 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 16:01 | Germany | 78.46.209.220 | 3.17 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 15:49 | United States | 143.244.34.62 | 2.88 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 15:31 | Czechia | 89.187.191.12 | 3.20 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 15:09 | Hong Kong | 84.17.57.98 | 3.24 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 15:06 | United Kingdom | 185.73.44.89 | 2.57 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 14:24 | Germany | 78.46.209.220 | 3.26 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 14:24 | Czechia | 89.187.191.12 | 0.62 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 13:57 | Hong Kong | 84.17.57.98 | 0.78 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 13:52 | United States | 143.244.34.62 | 3.07 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 13:38 | United Kingdom | 185.73.44.89 | 2.50 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 13:10 | Germany | 78.46.209.220 | 2.33 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 12:46 | Czechia | 89.187.191.12 | 1.65 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 12:10 | United States | 143.244.34.62 | 3.31 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 12:04 | United Kingdom | 185.73.44.89 | 2.62 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 12:00 | Hong Kong | 84.17.57.98 | 3.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 11:16 | Germany | 78.46.209.220 | 2.76 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 11:06 | Czechia | 89.187.191.12 | 3.08 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 10:50 | Hong Kong | 84.17.57.98 | 1.54 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 10:12 | United States | 143.244.34.62 | 1.85 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 10:04 | United Kingdom | 185.73.44.89 | 2.89 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 09:30 | Hong Kong | 84.17.57.98 | 3.18 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 09:27 | Germany | 78.46.209.220 | 3.15 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 09:09 | Czechia | 89.187.191.12 | 3.22 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 08:22 | United Kingdom | 185.73.44.89 | 2.43 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 08:18 | United States | 143.244.34.62 | 2.78 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 08:11 | Germany | 78.46.209.220 | 2.93 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 07:41 | Hong Kong | 84.17.57.98 | 3.30 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 07:21 | Czechia | 89.187.191.12 | 2.18 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 07:15 | United States | 143.244.34.62 | 3.13 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 07:04 | United Kingdom | 185.73.44.89 | 3.04 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 06:45 | Germany | 78.46.209.220 | 3.12 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 05:54 | Hong Kong | 84.17.57.98 | 3.25 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 05:50 | United States | 143.244.34.62 | 3.24 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 05:46 | United Kingdom | 185.73.44.89 | 2.55 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 05:35 | Czechia | 89.187.191.12 | 2.41 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 04:54 | Germany | 78.46.209.220 | 2.82 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 04:44 | Hong Kong | 84.17.57.98 | 3.10 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 04:35 | United Kingdom | 185.73.44.89 | 2.36 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 04:26 | United States | 143.244.34.62 | 2.49 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 04:01 | Czechia | 89.187.191.12 | 2.61 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 03:24 | United Kingdom | 185.73.44.89 | 2.40 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 03:17 | Germany | 78.46.209.220 | 2.08 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 03:03 | Hong Kong | 84.17.57.98 | 1.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 02:32 | United States | 143.244.34.62 | 2.93 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 02:08 | Czechia | 89.187.191.12 | 3.23 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 02:02 | Germany | 78.46.209.220 | 3.17 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 02:01 | Hong Kong | 84.17.57.98 | 2.83 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 01:56 | United Kingdom | 185.73.44.89 | 3.28 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 01:01 | United States | 143.244.34.62 | 2.71 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 00:42 | Hong Kong | 84.17.57.98 | 1.87 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 00:24 | Germany | 78.46.209.220 | 1.01 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 00:14 | Czechia | 89.187.191.12 | 0.19 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-21 00:05 | United Kingdom | 185.73.44.89 | 1.84 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 23:37 | Hong Kong | 84.17.57.98 | 2.77 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 23:34 | United States | 143.244.34.62 | 2.65 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 23:15 | Germany | 78.46.209.220 | 1.62 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 22:53 | Czechia | 89.187.191.12 | 3.18 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 22:42 | United Kingdom | 185.73.44.89 | 1.13 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 22:06 | Germany | 78.46.209.220 | 2.69 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 22:03 | United States | 143.244.34.62 | 3.42 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 21:44 | Hong Kong | 84.17.57.98 | 3.29 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 21:11 | United Kingdom | 185.73.44.89 | 1.89 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 20:56 | Czechia | 89.187.191.12 | 1.61 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 20:23 | United States | 143.244.34.62 | 3.33 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 20:11 | Germany | 78.46.209.220 | 2.72 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 19:57 | Hong Kong | 84.17.57.98 | 3.46 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 19:36 | United Kingdom | 185.73.44.89 | 1.27 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 19:17 | Czechia | 89.187.191.12 | 1.73 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 18:51 | United States | 143.244.34.62 | 3.22 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 18:29 | Hong Kong | 84.17.57.98 | 3.09 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 18:26 | Germany | 78.46.209.220 | 2.76 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 18:12 | United Kingdom | 185.73.44.89 | 2.30 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 18:06 | Czechia | 89.187.191.12 | 2.99 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 17:18 | United States | 143.244.34.62 | 1.72 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 17:14 | Hong Kong | 84.17.57.98 | 3.71 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 16:58 | United Kingdom | 185.73.44.89 | 2.51 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 16:53 | Germany | 78.46.209.220 | 3.29 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 16:27 | Czechia | 89.187.191.12 | 2.89 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 15:51 | United States | 143.244.34.62 | 3.01 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 15:50 | Germany | 78.46.209.220 | 2.80 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 15:28 | United Kingdom | 185.73.44.89 | 3.28 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 15:16 | Hong Kong | 84.17.57.98 | 2.84 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 14:34 | Czechia | 89.187.191.12 | 2.76 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 14:08 | Hong Kong | 84.17.57.98 | 2.86 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 14:02 | United Kingdom | 185.73.44.89 | 1.21 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 13:54 | United States | 143.244.34.62 | 3.24 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 13:51 | Germany | 78.46.209.220 | 2.97 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 13:09 | Czechia | 89.187.191.12 | 1.18 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 12:47 | Hong Kong | 84.17.57.98 | 3.47 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 12:18 | United Kingdom | 185.73.44.89 | 2.07 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 12:17 | United States | 143.244.34.62 | 2.04 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 12:00 | Germany | 78.46.209.220 | 2.18 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 11:26 | Czechia | 89.187.191.12 | 0.80 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 11:24 | Hong Kong | 84.17.57.98 | 3.27 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 10:49 | United States | 143.244.34.62 | 3.09 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 10:33 | United Kingdom | 185.73.44.89 | 2.89 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 10:23 | Hong Kong | 84.17.57.98 | 3.67 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 10:06 | Germany | 78.46.209.220 | 2.85 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 09:38 | Czechia | 89.187.191.12 | 2.45 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 09:17 | United States | 143.244.34.62 | 3.17 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 09:12 | United Kingdom | 185.73.44.89 | 3.12 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 08:59 | Hong Kong | 84.17.57.98 | 3.17 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 08:32 | Czechia | 89.187.191.12 | 2.42 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 08:22 | Germany | 78.46.209.220 | 2.89 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 08:14 | United States | 143.244.34.62 | 3.30 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 07:54 | United Kingdom | 185.73.44.89 | 3.00 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 07:20 | Hong Kong | 84.17.57.98 | 3.58 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 07:12 | United States | 143.244.34.62 | 2.84 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 07:07 | Germany | 78.46.209.220 | 1.74 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 06:55 | Czechia | 89.187.191.12 | 3.09 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 06:09 | United Kingdom | 185.73.44.89 | 3.19 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 06:05 | Hong Kong | 84.17.57.98 | 3.28 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 05:59 | Germany | 78.46.209.220 | 2.79 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 05:23 | United States | 143.244.34.62 | 2.94 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 05:19 | Czechia | 89.187.191.12 | 3.24 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 04:45 | United Kingdom | 185.73.44.89 | 2.97 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 04:34 | Germany | 78.46.209.220 | 2.85 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 04:20 | Hong Kong | 84.17.57.98 | 3.17 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 04:03 | United States | 143.244.34.62 | 3.10 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 03:44 | Czechia | 89.187.191.12 | 3.12 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 03:08 | United Kingdom | 185.73.44.89 | 2.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 02:45 | Germany | 78.46.209.220 | 3.06 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 02:39 | Hong Kong | 84.17.57.98 | 3.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 02:20 | United States | 143.244.34.62 | 3.06 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 02:04 | Czechia | 89.187.191.12 | 3.29 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 02:02 | United Kingdom | 185.73.44.89 | 3.29 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 01:03 | Hong Kong | 84.17.57.98 | 1.10 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 00:54 | Germany | 78.46.209.220 | 3.23 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 00:28 | United States | 143.244.34.62 | 1.13 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 00:22 | Czechia | 89.187.191.12 | 1.15 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-20 00:08 | United Kingdom | 185.73.44.89 | 3.27 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 23:52 | Hong Kong | 84.17.57.98 | 3.21 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 23:23 | Germany | 78.46.209.220 | 2.80 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 23:11 | United States | 143.244.34.62 | 3.35 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 23:04 | United Kingdom | 185.73.44.89 | 0.49 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 22:45 | Czechia | 89.187.191.12 | 0.99 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 22:27 | Hong Kong | 84.17.57.98 | 1.46 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 22:00 | Germany | 78.46.209.220 | 3.12 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 21:30 | United States | 143.244.34.62 | 0.69 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 21:26 | United Kingdom | 185.73.44.89 | 2.23 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 21:19 | Czechia | 89.187.191.12 | 2.40 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 21:15 | Hong Kong | 84.17.57.98 | 0.18 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 20:22 | United Kingdom | 185.73.44.89 | 1.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 20:14 | Germany | 78.46.209.220 | 2.27 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 20:08 | United States | 143.244.34.62 | 0.92 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 19:27 | Czechia | 89.187.191.12 | 3.25 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 19:15 | Hong Kong | 84.17.57.98 | 3.22 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 19:06 | United Kingdom | 185.73.44.89 | 2.99 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 18:54 | United States | 143.244.34.62 | 3.32 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 18:38 | Germany | 78.46.209.220 | 2.75 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 18:14 | Czechia | 89.187.191.12 | 2.48 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 17:43 | Hong Kong | 84.17.57.98 | 3.39 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 17:42 | United States | 143.244.34.62 | 3.21 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 17:18 | United Kingdom | 185.73.44.89 | 2.43 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 16:43 | Germany | 78.46.209.220 | 3.15 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |
||
| 2025-04-19 16:25 | Hong Kong | 84.17.57.98 | 3.22 | No | rsync: [Receiver] failed to connect to mirror.hafeezh.com (92.99.95.40): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(139) [Receiver=3.4.1] |