Jump to content

SaSaSushi

Member
  • Posts

    5
  • Joined

  • Last visited

SaSaSushi's Achievements

Helping Hand

Helping Hand (3/5)

0

Reputation

  1. 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!
  2. And just to update, traceroute tried 64 hops and finished with none after number 12, the same GTT server where Kiwi's died too.
  3. 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.
  4. Same here and unable to directly download the update from the Alfred site either.
  5. Thank you very much for the quick reply, Tyler. I accidentally deleted my initial post. That indeed took care of the problem! As I mentioned, I am used to just entering my searches and hitting enter in the V1 extension. It seems the workflow requires the parsing of the search to be complete before hitting enter in order for the proper results to appear in the growl notification. Is there any way around that?
×
×
  • Create New...