URL Details: rsync://mirror.jingk.ai/archlinux/
| URL: | rsync://mirror.jingk.ai/archlinux/ |
|---|---|
| Mirror: | jingk.ai |
| Protocol: | rsync |
| Country: | Singapore |
| IPv4: | Yes |
| IPv6: | No |
Check Logs
| Check Time | Check Location | Check IP | Last Sync | Delay (hh:mm) | Duration (s) | Success? | Error Message |
|---|---|---|---|---|---|---|---|
| 2026-06-14 20:18 | Germany | 78.46.209.220 | 2026-06-14 09:22 | 10:56 | 2.61 | Yes | |
| 2026-06-14 19:24 | United Kingdom | 185.73.44.89 | 2026-06-14 09:22 | 10:02 | 3.20 | Yes | |
| 2026-06-14 19:01 | Sweden | 194.71.11.121 | 2026-06-14 09:22 | 9:39 | 5.16 | Yes | |
| 2026-06-14 18:45 | Germany | 78.46.209.220 | 2026-06-14 09:22 | 9:23 | 3.03 | Yes | |
| 2026-06-14 17:57 | United Kingdom | 185.73.44.89 | 2026-06-14 09:22 | 8:35 | 3.04 | Yes | |
| 2026-06-14 17:23 | Sweden | 194.71.11.121 | 2026-06-14 09:22 | 8:01 | 4.08 | Yes | |
| 2026-06-14 17:18 | Germany | 78.46.209.220 | 2026-06-14 09:22 | 7:56 | 2.62 | Yes | |
| 2026-06-14 16:45 | United Kingdom | 185.73.44.89 | 2026-06-14 09:22 | 7:23 | 3.17 | Yes | |
| 2026-06-14 16:08 | Sweden | 194.71.11.121 | 2026-06-14 09:22 | 6:46 | 5.10 | Yes | |
| 2026-06-14 15:39 | Germany | 78.46.209.220 | 2026-06-14 09:22 | 6:16 | 3.19 | Yes | |
| 2026-06-14 15:24 | United Kingdom | 185.73.44.89 | 2026-06-14 09:22 | 6:02 | 2.71 | Yes | |
| 2026-06-14 14:31 | Sweden | 194.71.11.121 | 2026-06-14 09:22 | 5:09 | 4.09 | Yes | |
| 2026-06-14 14:26 | Germany | 78.46.209.220 | 2026-06-14 09:22 | 5:04 | 2.63 | Yes | |
| 2026-06-14 14:18 | United Kingdom | 185.73.44.89 | 2026-06-14 09:22 | 4:56 | 2.73 | Yes | |
| 2026-06-14 12:59 | Sweden | 194.71.11.121 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 12:57 | United Kingdom | 185.73.44.89 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 12:44 | Germany | 78.46.209.220 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 11:08 | United Kingdom | 185.73.44.89 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 11:04 | Sweden | 194.71.11.121 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 11:03 | Germany | 78.46.209.220 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 09:48 | Germany | 78.46.209.220 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 09:24 | United Kingdom | 185.73.44.89 | No | rsync subprocess killed after 15.0 seconds | |||
| 2026-06-14 09:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 444:49 | 4.86 | Yes | |
| 2026-06-14 07:58 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 443:36 | 3.03 | Yes | |
| 2026-06-14 07:49 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 443:27 | 2.49 | Yes | |
| 2026-06-14 07:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 442:49 | 3.77 | Yes | |
| 2026-06-14 06:32 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 442:10 | 3.08 | Yes | |
| 2026-06-14 06:00 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 441:38 | 2.79 | Yes | |
| 2026-06-14 05:33 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 441:11 | 4.80 | Yes | |
| 2026-06-14 05:00 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 440:38 | 3.25 | Yes | |
| 2026-06-14 04:22 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 440:00 | 2.93 | Yes | |
| 2026-06-14 03:54 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 439:32 | 3.12 | Yes | |
| 2026-06-14 03:39 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 439:17 | 3.71 | Yes | |
| 2026-06-14 02:54 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 438:32 | 2.64 | Yes | |
| 2026-06-14 02:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 437:48 | 5.83 | Yes | |
| 2026-06-14 02:05 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 437:43 | 2.77 | Yes | |
| 2026-06-14 01:52 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 437:30 | 2.95 | Yes | |
| 2026-06-14 00:32 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 436:10 | 2.79 | Yes | |
| 2026-06-14 00:21 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 435:59 | 3.90 | Yes | |
| 2026-06-14 00:07 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 435:45 | 2.68 | Yes | |
| 2026-06-13 22:43 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 434:21 | 2.79 | Yes | |
| 2026-06-13 22:42 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 434:20 | 4.06 | Yes | |
| 2026-06-13 22:26 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 434:04 | 2.98 | Yes | |
| 2026-06-13 21:20 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 432:58 | 2.78 | Yes | |
| 2026-06-13 21:18 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 432:56 | 2.66 | Yes | |
| 2026-06-13 21:08 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 432:46 | 3.90 | Yes | |
| 2026-06-13 20:03 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 431:41 | 4.50 | Yes | |
| 2026-06-13 19:51 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 431:29 | 2.81 | Yes | |
| 2026-06-13 19:34 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 431:12 | 3.42 | Yes | |
| 2026-06-13 18:24 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 430:02 | 2.48 | Yes | |
| 2026-06-13 18:13 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 429:51 | 3.16 | Yes | |
| 2026-06-13 18:06 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 429:44 | 4.50 | Yes | |
| 2026-06-13 16:34 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 428:12 | 3.87 | Yes | |
| 2026-06-13 16:26 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 428:04 | 3.20 | Yes | |
| 2026-06-13 16:16 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 427:54 | 3.19 | Yes | |
| 2026-06-13 15:12 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 426:50 | 2.87 | Yes | |
| 2026-06-13 15:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 426:48 | 4.69 | Yes | |
| 2026-06-13 14:56 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 426:34 | 2.65 | Yes | |
| 2026-06-13 14:10 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 425:48 | 3.04 | Yes | |
| 2026-06-13 14:06 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 425:44 | 5.14 | Yes | |
| 2026-06-13 13:42 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 425:20 | 3.04 | Yes | |
| 2026-06-13 13:10 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 424:48 | 3.05 | Yes | |
| 2026-06-13 12:26 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 424:04 | 4.71 | Yes | |
| 2026-06-13 11:58 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 423:36 | 2.49 | Yes | |
| 2026-06-13 11:39 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 423:17 | 2.86 | Yes | |
| 2026-06-13 11:19 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 422:57 | 3.61 | Yes | |
| 2026-06-13 10:25 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 422:03 | 3.33 | Yes | |
| 2026-06-13 10:22 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 422:00 | 2.77 | Yes | |
| 2026-06-13 10:10 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 421:48 | 4.81 | Yes | |
| 2026-06-13 09:00 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 420:38 | 2.68 | Yes | |
| 2026-06-13 08:57 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 420:35 | 3.16 | Yes | |
| 2026-06-13 08:55 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 420:33 | 4.76 | Yes | |
| 2026-06-13 07:54 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 419:32 | 2.32 | Yes | |
| 2026-06-13 07:06 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 418:44 | 3.12 | Yes | |
| 2026-06-13 07:00 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 418:38 | 3.92 | Yes | |
| 2026-06-13 06:48 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 418:26 | 2.98 | Yes | |
| 2026-06-13 06:02 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 417:40 | 3.39 | Yes | |
| 2026-06-13 05:32 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 417:10 | 5.61 | Yes | |
| 2026-06-13 04:59 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 416:37 | 2.34 | Yes | |
| 2026-06-13 04:31 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 416:09 | 2.93 | Yes | |
| 2026-06-13 03:39 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 415:17 | 3.17 | Yes | |
| 2026-06-13 03:35 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 415:13 | 4.19 | Yes | |
| 2026-06-13 02:49 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 414:27 | 2.87 | Yes | |
| 2026-06-13 02:32 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 414:10 | 2.33 | Yes | |
| 2026-06-13 02:16 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 413:54 | 4.24 | Yes | |
| 2026-06-13 01:16 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 412:54 | 2.92 | Yes | |
| 2026-06-13 01:13 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 412:51 | 3.11 | Yes | |
| 2026-06-13 00:25 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 412:03 | 3.86 | Yes | |
| 2026-06-12 23:55 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 411:33 | 2.81 | Yes | |
| 2026-06-12 23:51 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 411:29 | 2.31 | Yes | |
| 2026-06-12 23:21 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 410:59 | 4.53 | Yes | |
| 2026-06-12 22:47 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 410:25 | 2.95 | Yes | |
| 2026-06-12 22:15 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 409:53 | 3.10 | Yes | |
| 2026-06-12 21:54 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 409:32 | 4.00 | Yes | |
| 2026-06-12 21:06 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 408:44 | 2.78 | Yes | |
| 2026-06-12 20:52 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 408:30 | 2.32 | Yes | |
| 2026-06-12 19:55 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 407:33 | 5.03 | Yes | |
| 2026-06-12 19:32 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 407:10 | 3.01 | Yes | |
| 2026-06-12 19:26 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 407:04 | 3.07 | Yes | |
| 2026-06-12 18:30 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 406:08 | 2.79 | Yes | |
| 2026-06-12 18:00 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 405:38 | 4.71 | Yes | |
| 2026-06-12 17:53 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 405:31 | 2.85 | Yes | |
| 2026-06-12 17:20 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 404:58 | 2.51 | Yes | |
| 2026-06-12 16:42 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 404:20 | 3.79 | Yes | |
| 2026-06-12 15:57 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 403:35 | 3.04 | Yes | |
| 2026-06-12 15:26 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 403:04 | 5.00 | Yes | |
| 2026-06-12 15:24 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 403:02 | 2.82 | Yes | |
| 2026-06-12 14:39 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 402:17 | 3.00 | Yes | |
| 2026-06-12 13:51 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 401:29 | 4.02 | Yes | |
| 2026-06-12 13:29 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 401:07 | 2.66 | Yes | |
| 2026-06-12 12:56 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 400:34 | 3.14 | Yes | |
| 2026-06-12 12:00 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 399:38 | 5.02 | Yes | |
| 2026-06-12 11:58 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 399:36 | 2.95 | Yes | |
| 2026-06-12 11:54 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 399:32 | 3.17 | Yes | |
| 2026-06-12 10:43 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 398:21 | 4.32 | Yes | |
| 2026-06-12 10:20 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 397:58 | 2.48 | Yes | |
| 2026-06-12 10:19 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 397:57 | 2.88 | Yes | |
| 2026-06-12 09:25 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 397:03 | 4.53 | Yes | |
| 2026-06-12 08:28 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 396:06 | 2.98 | Yes | |
| 2026-06-12 08:25 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 396:03 | 3.13 | Yes | |
| 2026-06-12 07:51 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 395:29 | 3.83 | Yes | |
| 2026-06-12 07:22 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 395:00 | 2.87 | Yes | |
| 2026-06-12 07:04 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 394:41 | 2.67 | Yes | |
| 2026-06-12 06:21 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 393:59 | 3.23 | Yes | |
| 2026-06-12 06:07 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 393:45 | 5.82 | Yes | |
| 2026-06-12 05:41 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 393:19 | 2.88 | Yes | |
| 2026-06-12 05:17 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 392:55 | 3.07 | Yes | |
| 2026-06-12 04:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 391:49 | 3.53 | Yes | |
| 2026-06-12 04:03 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 391:41 | 2.59 | Yes | |
| 2026-06-12 03:44 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 391:22 | 2.57 | Yes | |
| 2026-06-12 02:39 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 390:17 | 4.26 | Yes | |
| 2026-06-12 02:31 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 390:09 | 3.01 | Yes | |
| 2026-06-12 02:30 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 390:08 | 2.82 | Yes | |
| 2026-06-12 01:17 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 388:55 | 2.47 | Yes | |
| 2026-06-12 00:41 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 388:19 | 3.64 | Yes | |
| 2026-06-12 00:32 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 388:10 | 2.78 | Yes | |
| 2026-06-11 23:18 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 386:56 | 2.75 | Yes | |
| 2026-06-11 23:17 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 386:55 | 4.60 | Yes | |
| 2026-06-11 22:52 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 386:30 | 2.77 | Yes | |
| 2026-06-11 22:08 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 385:46 | 3.91 | Yes | |
| 2026-06-11 21:47 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 385:25 | 2.46 | Yes | |
| 2026-06-11 21:34 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 385:12 | 2.78 | Yes | |
| 2026-06-11 20:59 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 384:37 | 5.67 | Yes | |
| 2026-06-11 20:39 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 384:17 | 2.92 | Yes | |
| 2026-06-11 20:31 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 384:09 | 2.90 | Yes | |
| 2026-06-11 19:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 382:49 | 4.63 | Yes | |
| 2026-06-11 18:50 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 382:28 | 3.06 | Yes | |
| 2026-06-11 18:47 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 382:25 | 2.94 | Yes | |
| 2026-06-11 17:56 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 381:34 | 5.37 | Yes | |
| 2026-06-11 17:32 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 381:10 | 2.89 | Yes | |
| 2026-06-11 17:18 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 380:56 | 2.45 | Yes | |
| 2026-06-11 16:17 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 379:55 | 6.67 | Yes | |
| 2026-06-11 16:16 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 379:54 | 2.79 | Yes | |
| 2026-06-11 16:04 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 379:42 | 3.01 | Yes | |
| 2026-06-11 15:00 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 378:38 | 2.67 | Yes | |
| 2026-06-11 14:40 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 378:18 | 5.32 | Yes | |
| 2026-06-11 14:17 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 377:55 | 3.05 | Yes | |
| 2026-06-11 13:20 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 376:58 | 5.03 | Yes | |
| 2026-06-11 13:18 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 376:56 | 2.96 | Yes | |
| 2026-06-11 12:46 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 376:24 | 2.67 | Yes | |
| 2026-06-11 11:52 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 375:30 | 4.16 | Yes | |
| 2026-06-11 11:45 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 375:23 | 2.65 | Yes | |
| 2026-06-11 10:51 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 374:29 | 4.32 | Yes | |
| 2026-06-11 10:48 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 374:26 | 3.02 | Yes | |
| 2026-06-11 10:03 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 373:41 | 3.33 | Yes | |
| 2026-06-11 09:20 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 372:58 | 4.09 | Yes | |
| 2026-06-11 08:56 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 372:34 | 2.89 | Yes | |
| 2026-06-11 08:19 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 371:57 | 2.56 | Yes | |
| 2026-06-11 07:43 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 371:21 | 4.77 | Yes | |
| 2026-06-11 07:01 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 370:39 | 2.93 | Yes | |
| 2026-06-11 06:57 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 370:35 | 2.86 | Yes | |
| 2026-06-11 05:52 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 369:30 | 4.81 | Yes | |
| 2026-06-11 05:28 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 369:06 | 2.89 | Yes | |
| 2026-06-11 05:00 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 368:38 | 3.21 | Yes | |
| 2026-06-11 04:45 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 368:23 | 4.29 | Yes | |
| 2026-06-11 04:21 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 367:59 | 2.32 | Yes | |
| 2026-06-11 03:56 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 367:34 | 3.23 | Yes | |
| 2026-06-11 03:15 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 366:53 | 5.60 | Yes | |
| 2026-06-11 02:41 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 366:19 | 2.82 | Yes | |
| 2026-06-11 02:40 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 366:18 | 2.93 | Yes | |
| 2026-06-11 01:39 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 365:17 | 2.91 | Yes | |
| 2026-06-11 01:18 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 364:56 | 4.44 | Yes | |
| 2026-06-11 00:53 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 364:31 | 2.63 | Yes | |
| 2026-06-11 00:16 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 363:54 | 2.90 | Yes | |
| 2026-06-11 00:02 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 363:40 | 3.80 | Yes | |
| 2026-06-10 22:54 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 362:32 | 4.65 | Yes | |
| 2026-06-10 22:54 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 362:32 | 2.92 | Yes | |
| 2026-06-10 22:28 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 362:06 | 3.01 | Yes | |
| 2026-06-10 21:29 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 361:07 | 3.73 | Yes | |
| 2026-06-10 21:17 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 360:55 | 3.19 | Yes | |
| 2026-06-10 21:12 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 360:50 | 2.38 | Yes | |
| 2026-06-10 20:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 359:49 | 4.62 | Yes | |
| 2026-06-10 19:43 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 359:21 | 3.03 | Yes | |
| 2026-06-10 19:19 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 358:57 | 2.87 | Yes | |
| 2026-06-10 18:48 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 358:26 | 3.88 | Yes | |
| 2026-06-10 18:37 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 358:15 | 2.49 | Yes | |
| 2026-06-10 18:00 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 357:38 | 2.90 | Yes | |
| 2026-06-10 17:05 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 356:43 | 5.19 | Yes | |
| 2026-06-10 17:00 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 356:38 | 2.81 | Yes | |
| 2026-06-10 16:09 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 355:47 | 3.04 | Yes | |
| 2026-06-10 15:27 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 355:05 | 2.51 | Yes | |
| 2026-06-10 15:12 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 354:50 | 3.89 | Yes | |
| 2026-06-10 14:57 | United Kingdom | 185.73.44.89 | 2026-05-26 20:22 | 354:35 | 2.88 | Yes | |
| 2026-06-10 14:11 | Sweden | 194.71.11.121 | 2026-05-26 20:22 | 353:49 | 5.86 | Yes | |
| 2026-06-10 14:08 | Germany | 78.46.209.220 | 2026-05-26 20:22 | 353:46 | 3.00 | Yes | |
| 2026-06-10 13:08 | United Kingdom | 185.73.44.89 | 3.30 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 12:46 | Germany | 78.46.209.220 | 1.84 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 12:21 | Sweden | 194.71.11.121 | 1.09 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 11:09 | United Kingdom | 185.73.44.89 | 3.79 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 10:57 | Germany | 78.46.209.220 | 2.16 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 10:46 | Sweden | 194.71.11.121 | 1.84 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 09:46 | Germany | 78.46.209.220 | 2.55 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 09:44 | Sweden | 194.71.11.121 | 1.95 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 09:38 | United Kingdom | 185.73.44.89 | 2.41 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 08:36 | United Kingdom | 185.73.44.89 | 0.61 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 08:12 | Sweden | 194.71.11.121 | 3.89 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 08:11 | Germany | 78.46.209.220 | 1.26 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 07:25 | United Kingdom | 185.73.44.89 | 2.69 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 06:58 | Sweden | 194.71.11.121 | 1.10 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 06:11 | Germany | 78.46.209.220 | 4.60 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 05:39 | Sweden | 194.71.11.121 | 1.11 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 05:34 | United Kingdom | 185.73.44.89 | 3.75 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 04:27 | United Kingdom | 185.73.44.89 | 0.81 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 04:23 | Sweden | 194.71.11.121 | 0.55 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 04:17 | Germany | 78.46.209.220 | 1.65 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 03:21 | Sweden | 194.71.11.121 | 1.10 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 03:04 | United Kingdom | 185.73.44.89 | 2.83 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 02:41 | Germany | 78.46.209.220 | 0.21 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 01:52 | United Kingdom | 185.73.44.89 | 3.07 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 01:29 | Sweden | 194.71.11.121 | 2.48 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 01:12 | Germany | 78.46.209.220 | 2.49 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 00:25 | Sweden | 194.71.11.121 | 3.47 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 00:20 | United Kingdom | 185.73.44.89 | 2.11 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-10 00:10 | Germany | 78.46.209.220 | 3.34 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 22:55 | Sweden | 194.71.11.121 | 2.57 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 22:29 | United Kingdom | 185.73.44.89 | 3.23 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 22:29 | Germany | 78.46.209.220 | 1.36 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 21:26 | Germany | 78.46.209.220 | 2.03 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 20:57 | Sweden | 194.71.11.121 | 4.61 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 20:31 | United Kingdom | 185.73.44.89 | 2.41 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 19:44 | Germany | 78.46.209.220 | 3.26 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 19:32 | Sweden | 194.71.11.121 | 1.96 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 19:20 | United Kingdom | 185.73.44.89 | 3.29 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 18:09 | Sweden | 194.71.11.121 | 2.56 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 18:08 | Germany | 78.46.209.220 | 0.31 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 17:29 | United Kingdom | 185.73.44.89 | 5.35 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 16:24 | United Kingdom | 185.73.44.89 | 3.33 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 16:23 | Germany | 78.46.209.220 | 2.05 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 16:18 | Sweden | 194.71.11.121 | 1.44 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 15:15 | Germany | 78.46.209.220 | 4.21 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 14:45 | United Kingdom | 185.73.44.89 | 2.88 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 14:19 | Sweden | 194.71.11.121 | 4.23 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 13:51 | Germany | 78.46.209.220 | 6.40 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 13:32 | United Kingdom | 185.73.44.89 | 0.53 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 13:11 | Sweden | 194.71.11.121 | 1.61 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 12:41 | Germany | 78.46.209.220 | 3.30 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 11:58 | United Kingdom | 185.73.44.89 | 0.98 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 11:51 | Sweden | 194.71.11.121 | 4.10 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 11:07 | Germany | 78.46.209.220 | 5.20 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 10:34 | Sweden | 194.71.11.121 | 3.59 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 10:28 | United Kingdom | 185.73.44.89 | 3.39 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 09:28 | Germany | 78.46.209.220 | 0.94 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 08:43 | Sweden | 194.71.11.121 | 3.39 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 08:40 | United Kingdom | 185.73.44.89 | 1.95 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 07:43 | Germany | 78.46.209.220 | 2.60 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 07:34 | United Kingdom | 185.73.44.89 | 2.75 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 07:15 | Sweden | 194.71.11.121 | 1.02 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 06:05 | Germany | 78.46.209.220 | 2.36 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 05:48 | Sweden | 194.71.11.121 | 3.40 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 05:35 | United Kingdom | 185.73.44.89 | 2.39 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 04:49 | Germany | 78.46.209.220 | 5.34 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 04:31 | United Kingdom | 185.73.44.89 | 5.72 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 03:48 | Sweden | 194.71.11.121 | 1.39 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 03:41 | Germany | 78.46.209.220 | 2.97 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 03:17 | United Kingdom | 185.73.44.89 | 1.67 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 02:46 | Sweden | 194.71.11.121 | 3.44 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 02:33 | Germany | 78.46.209.220 | 3.29 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 02:04 | United Kingdom | 185.73.44.89 | 3.99 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 01:03 | Sweden | 194.71.11.121 | 1.37 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 00:57 | Germany | 78.46.209.220 | 3.64 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-09 00:27 | United Kingdom | 185.73.44.89 | 0.44 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 23:50 | Germany | 78.46.209.220 | 2.20 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 23:29 | Sweden | 194.71.11.121 | 3.38 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 23:08 | United Kingdom | 185.73.44.89 | 3.27 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 21:58 | Germany | 78.46.209.220 | 2.56 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 21:56 | United Kingdom | 185.73.44.89 | 3.02 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 21:40 | Sweden | 194.71.11.121 | 2.45 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 20:47 | Germany | 78.46.209.220 | 3.68 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 20:10 | United Kingdom | 185.73.44.89 | 3.98 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 19:58 | Sweden | 194.71.11.121 | 3.42 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 19:07 | Germany | 78.46.209.220 | 1.75 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 18:28 | United Kingdom | 185.73.44.89 | 2.75 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 18:15 | Sweden | 194.71.11.121 | 3.46 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 17:25 | Germany | 78.46.209.220 | 0.93 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 17:00 | United Kingdom | 185.73.44.89 | 1.37 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 16:22 | Sweden | 194.71.11.121 | 0.87 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 15:47 | United Kingdom | 185.73.44.89 | 1.35 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 15:47 | Germany | 78.46.209.220 | 5.91 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 14:43 | Sweden | 194.71.11.121 | 3.46 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 14:37 | United Kingdom | 185.73.44.89 | 3.32 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 14:22 | Germany | 78.46.209.220 | 2.78 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 13:08 | United Kingdom | 185.73.44.89 | 3.32 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 13:04 | Sweden | 194.71.11.121 | 2.40 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 13:00 | Germany | 78.46.209.220 | 2.80 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 11:57 | United Kingdom | 185.73.44.89 | 4.28 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 11:21 | Sweden | 194.71.11.121 | 3.37 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 11:21 | Germany | 78.46.209.220 | 2.39 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 10:17 | Sweden | 194.71.11.121 | 4.75 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 10:08 | Germany | 78.46.209.220 | 2.29 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 09:57 | United Kingdom | 185.73.44.89 | 3.26 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 09:11 | Sweden | 194.71.11.121 | 2.04 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 08:51 | United Kingdom | 185.73.44.89 | 2.67 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 08:33 | Germany | 78.46.209.220 | 3.32 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 07:56 | Sweden | 194.71.11.121 | 5.90 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 07:16 | United Kingdom | 185.73.44.89 | 2.46 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 06:47 | Germany | 78.46.209.220 | 3.82 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 06:18 | Sweden | 194.71.11.121 | 1.28 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 05:29 | United Kingdom | 185.73.44.89 | 3.26 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 04:58 | Germany | 78.46.209.220 | 5.22 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 04:30 | Sweden | 194.71.11.121 | 5.21 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 04:03 | United Kingdom | 185.73.44.89 | 3.03 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 03:01 | Germany | 78.46.209.220 | 3.31 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 02:56 | Sweden | 194.71.11.121 | 1.14 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 02:52 | United Kingdom | 185.73.44.89 | 3.34 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 01:42 | Germany | 78.46.209.220 | 1.74 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 01:03 | United Kingdom | 185.73.44.89 | 6.40 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-08 00:56 | Sweden | 194.71.11.121 | 0.54 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 23:50 | United Kingdom | 185.73.44.89 | 2.85 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 23:42 | Germany | 78.46.209.220 | 3.37 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 23:38 | Sweden | 194.71.11.121 | 1.41 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 22:24 | Sweden | 194.71.11.121 | 2.15 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 22:14 | Germany | 78.46.209.220 | 0.29 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 22:10 | United Kingdom | 185.73.44.89 | 3.83 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 21:05 | United Kingdom | 185.73.44.89 | 6.38 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 20:53 | Sweden | 194.71.11.121 | 3.36 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |
||
| 2026-06-07 20:34 | Germany | 78.46.209.220 | 3.85 | No | rsync: [Receiver] failed to connect to mirror.jingk.ai (101.100.183.42): No route to host (113) rsync error: error in socket IO (code 10) at clientserver.c(141) [Receiver=3.4.3] |