Kiwi Posted September 26, 2017 Share Posted September 26, 2017 Link to comment Share on other sites More sharing options...
SaSaSushi Posted September 26, 2017 Share Posted September 26, 2017 Same here and unable to directly download the update from the Alfred site either. Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 @Kiwi @SaSaSushi Thanks for letting us know. We've cleared the caches a few moments ago, so could you please try restarting your Mac and trying again? I'll keep an eye on this thread, so let me know how you get on. Cheers, Vero Link to comment Share on other sites More sharing options...
Andrew Posted September 26, 2017 Share Posted September 26, 2017 It looks like CacheFly had routing issues a few hours ago, but these should be resolved now. We'll contact them to let them know that users are still experiencing issues. http://status.cachefly.com Cheers, Andrew Link to comment Share on other sites More sharing options...
Kiwi Posted September 26, 2017 Author Share Posted September 26, 2017 8 minutes ago, Vero said: @Kiwi @SaSaSushi Thanks for letting us know. We've cleared the caches a few moments ago, so could you please try restarting your Mac and trying again? I'll keep an eye on this thread, so let me know how you get on. Cheers, Vero I tried but it doesn't work...... Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 We've spoken to CacheFly and they've asked for our help in resolving the residual issues following their intermittent outages from last night. If you're seeing "Unable to find zip" when updating, or are unable to download Alfred, please take a look at these two steps: First: please follow the link below and copy the output of the page into your forum reply: https://cachefly.alfredapp.com/CacheFlyDebug Second: please open the macOS Network Utility app, go to the Traceroute tab, and paste in "cachefly.alfredapp.com". The traceroute may take some time, then paste the results in your forum reply as well. We'll then be able to pass these reports to CacheFly to resolve the issue Cheers, Vero Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 @Kiwi @SaSaSushi In case you haven't seen these thread updates, we'd be grateful for your help with the above if you get a chance to run through those two steps and give us your results Cheers, Vero Link to comment Share on other sites More sharing options...
Kiwi Posted September 26, 2017 Author Share Posted September 26, 2017 42 minutes ago, Vero said: @Kiwi @SaSaSushi In case you haven't seen these thread updates, we'd be grateful for your help with the above if you get a chance to run through those two steps and give us your results Cheers, Vero It works through SOCK5 proxy...... The proxy server is in the USA. The network I used is experiencing a problem.Thanks for your help! Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 @Kiwi To help other users, and so that we can feed the information back to Cachefly, could you take a moment to go through the two steps above? I'd be really grateful for your help as it's an issue we're not experiencing here. Cheers, Vero Link to comment Share on other sites More sharing options...
SaSaSushi Posted September 26, 2017 Share Posted September 26, 2017 (edited) Hi, sorry to report I am still unable to access the update either in app nor from the website. The Cachefly debug page is equally inaccessible so I'm sorry I can't send you that data. Here is my traceroute: Traceroute has started… traceroute to vip1.g5.cachefly.net (204.93.150.152), 64 hops max, 72 byte packets 1 router.asus.com (192.168.1.1) 2553.635 ms 0.353 ms 0.241 ms 2 115.31.55.24 (115.31.55.24) 0.991 ms 2.036 ms 1.241 ms 3 115.31.55.61 (115.31.55.61) 1.651 ms 2.006 ms 1.200 ms 4 115.31.54.101 (115.31.54.101) 1.943 ms 2.515 ms 1.964 ms 5 113.157.231.1 (113.157.231.1) 17.742 ms 11.022 ms 10.329 ms 6 113.157.227.21 (113.157.227.21) 11.215 ms 10.715 ms 11.238 ms 7 pajbb002.int-gw.kddi.ne.jp (106.187.8.10) 116.622 ms 117.030 ms 146.956 ms 8 sjegcs002.int-gw.kddi.ne.jp (124.211.34.85) 117.804 ms 118.175 ms 117.750 ms 9 ix-sj6.int-gw.kddi.ne.jp (111.87.3.182) 123.462 ms 123.193 ms 123.650 ms 10 ae21.cr5-sjc1.ip4.gtt.net (173.205.44.237) 113.650 ms 114.795 ms 114.481 ms 11 et-4-1-0.cr2-sea2.ip4.gtt.net (89.149.136.85) 133.142 ms 149.209 ms 133.392 ms 12 ip4.gtt.net (69.174.7.234) 137.128 ms 134.584 ms 134.119 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * It's still in process. If it ever completes I will send an updated paste. Edited September 26, 2017 by SaSaSushi Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 @SaSaSushi Thanks - I've passed this on to CacheFly and will report on any progress on their part. We welcome input from other users who are still seeing this issue, as the more information we can pass back to CacheFly, the better. I'll update this thread with further info as well. Cheers, Vero Link to comment Share on other sites More sharing options...
Kiwi Posted September 26, 2017 Author Share Posted September 26, 2017 11 minutes ago, Vero said: @Kiwi To help other users, and so that we can feed the information back to Cachefly, could you take a moment to go through the two steps above? I'd be really grateful for your help as it's an issue we're not experiencing here. Cheers, Vero The CacheFlyDebug page is inaccessible without proxy. Here is my traceroute without proxy: traceroute to vip1.g5.cachefly.net (204.93.150.152), 64 hops max, 72 byte packets 1 bogon (192.168.0.1) 1.645 ms 2.366 ms 0.852 ms 2 102.14.15.254 (102.14.15.254) 1.469 ms 8.822 ms 11.012 ms 3 bogon (172.20.127.5) 2.478 ms 1.748 ms 2.635 ms 4 bogon (172.20.127.109) 1.435 ms 1.642 ms 1.529 ms 5 122.97.216.97 (122.97.216.97) 5.468 ms 46.209 ms 7.433 ms 6 111.208.14.141 (111.208.14.141) 3.239 ms 2.650 ms 12.176 ms 7 111.208.14.5 (111.208.14.5) 10.214 ms 3.909 ms 4.033 ms 8 * * * 9 111.208.54.137 (111.208.54.137) 7.916 ms 13.175 ms 9.950 ms 10 111.208.72.42 (111.208.72.42) 5.731 ms 5.853 ms 6.052 ms 11 112.80.4.77 (112.80.4.77) 5.457 ms 6.484 ms 6.521 ms 12 112.80.4.249 (112.80.4.249) 6.638 ms 8.838 ms 7.411 ms 13 * 219.158.17.17 (219.158.17.17) 12.655 ms 16.793 ms 14 219.158.113.102 (219.158.113.102) 13.365 ms 15.550 ms 16.466 ms 15 219.158.113.121 (219.158.113.121) 15.264 ms 15.774 ms 17.037 ms 16 219.158.116.242 (219.158.116.242) 146.979 ms 148.502 ms 154.885 ms 17 xe-1-0-0.cr4-sjc1.ip4.gtt.net (173.205.62.81) 150.861 ms 150.272 ms 160.578 ms 18 xe-11-1-1.cr2-sea2.ip4.gtt.net (89.149.187.6) 185.654 ms 170.611 ms 165.759 ms 19 ip4.gtt.net (69.174.7.234) 164.715 ms 164.661 ms 167.867 ms 20 * * * 21 * * * 22 * * * Link to comment Share on other sites More sharing options...
SaSaSushi Posted September 26, 2017 Share Posted September 26, 2017 (edited) And just to update, traceroute tried 64 hops and finished with none after number 12, the same GTT server where Kiwi's died too. Edited September 26, 2017 by SaSaSushi Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 @Kiwi Much appreciated, thanks! Passed this on to CacheFly as well. Link to comment Share on other sites More sharing options...
SaSaSushi Posted September 26, 2017 Share Posted September 26, 2017 Cachefly has apparently resolved the problems. I was able to download the update in app at the normal lightning speed. I tested the download on the website as well and all is working well. Thank you for your prompt assistance with this! Link to comment Share on other sites More sharing options...
Vero Posted September 26, 2017 Share Posted September 26, 2017 @SaSaSushi Thanks for the reply - we've had a message from CacheFly saying it should be resolved, so it's good to get your confirmation Cheers, Vero Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now