Mirror Details: funami.tech
Name: |
funami.tech |
Tier: |
Tier 1 |
Has ISOs: |
Yes |
Available URLs
Mirror URL |
Protocol |
Country |
IPv4 |
IPv6 |
Last Sync |
Completion % |
μ Delay (hh:mm) |
μ Duration (s) |
σ Duration (s) |
Score |
Details |
http://mirror.funami.tech/arch/ |
http |
South Korea |
Yes |
Yes |
2024-04-26 02:49 |
99.0% |
0:03 |
0.55 |
0.27 |
0.9 |
Details |
https://mirror.funami.tech/arch/ |
https |
South Korea |
Yes |
Yes |
2024-04-26 02:59 |
100.0% |
0:02 |
0.78 |
0.31 |
1.1 |
Details |
rsync://mirror.funami.tech/arch/ |
rsync |
South Korea |
Yes |
Yes |
2024-04-26 02:59 |
100.0% |
0:02 |
4.60 |
1.96 |
6.6 |
Details |
Error Log
Mirror URL |
Protocol |
Country |
Error Message |
Last Occurred |
Occurrences (last 168 hours) |
|
http://mirror.funami.tech/arch/ |
http |
South Korea |
Connection timed out. |
2024-04-26 03:02 |
15 |
details |
rsync://mirror.funami.tech/arch/ |
rsync |
South Korea |
rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.3.0] |
2024-04-25 00:23 |
6 |
details |
https://mirror.funami.tech/arch/ |
https |
South Korea |
Connection timed out. |
2024-04-24 13:41 |
7 |
details |
https://mirror.funami.tech/arch/ |
https |
South Korea |
Could not parse time from lastsync |
2024-04-24 04:32 |
1 |
details |
rsync://mirror.funami.tech/arch/ |
rsync |
South Korea |
Could not parse time from lastsync |
2024-04-24 04:31 |
1 |
details |
http://mirror.funami.tech/arch/ |
http |
South Korea |
Could not parse time from lastsync |
2024-04-24 04:31 |
1 |
details |
rsync://mirror.funami.tech/arch/ |
rsync |
South Korea |
rsync error: timeout waiting for daemon connection (code 35) at socket.c(278) [Receiver=3.2.7] |
2024-04-22 08:02 |
4 |
details |
rsync://mirror.funami.tech/arch/ |
rsync |
South Korea |
[Receiver] io timeout after 10 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [Receiver=3.2.7] |
2024-04-20 23:48 |
1 |
details |
Mirror Status Charts
Periodic checks of the mirrors are done from various geographic
locations, IP addresses, and using IPv4 or IPv6. These results are
summarized in graphical form below.