L3s still not finding prohash

[hashingpro]

now 2 machines on the rack see the site as UP and are connected and hashing.
Others see it as DEAD, rebooted some, they still see PH site as DEAD.

And another minute later the 2 connected dropped off also.

[matthewlane2009]

I am having the same problem. My Miner is just going to the 2nd pool aimed at Litecoin pool. I took the miner off pro hash about a week ago the day you said the pool was going to be experiencing some down time, and have been unable to reconnect.

Is creating a new account the way to go about it?

Thanks!

[Steve Sokolowski]

Unfortunately, we can't reproduce this issue and haven't been able to figure out anything more about it.

We're continuing to investigate these network difficulties, but still have no idea what is causing them or how to go about resolving them.

[matthewlane2009]

I tried creating a new account and the pool still shows dead.

[DrIsk]

While this is happening, go to your miners control panel, then to the network tab, then to the diagnostics tab.

Then throw in prohashing.com into the middle box and hit 'Traceroute' - then paste the results here if you need help deciphering them.

Just an idea... maybe we'll find that you cant actually reach prohashing due to a network condition?

[matthewlane2009]

Here were the results.

Thanks a ton for any advice on how to fix.

Thanks

traceroute prohashing.com
traceroute to prohashing.com (167.88.15.87), 30 hops max, 38 byte packets
1 192.168.1.1 (192.168.1.1) 0.267 ms 0.350 ms 0.212 ms
2 96.120.8.145 (96.120.8.145) 9.646 ms 9.861 ms 8.703 ms
3 te-0-1-0-4-sur02.scranton.pa.pitt.comcast.net (68.85.53.217) 9.004 ms 9.137 ms 8.625 ms
4 162.151.220.218 (162.151.220.218) 10.402 ms 8.956 ms 8.908 ms
5 96.108.4.237 (96.108.4.237) 14.129 ms 14.183 ms 14.299 ms
6 hu-0-15-0-0-ar01.mckeesport.pa.pitt.comcast.net (69.139.168.141) 21.885 ms 21.930 ms 23.110 ms
7 be-7016-cr02.ashburn.va.ibone.comcast.net (68.86.91.25) 44.771 ms 28.241 ms 28.492 ms
8 hu-0-10-0-1-pe04.ashburn.va.ibone.comcast.net (68.86.82.210) 27.460 ms 29.607 ms 29.696 ms
9 23.30.206.206 (23.30.206.206) 27.337 ms 27.321 ms 28.552 ms
10 89.149.141.245 (89.149.141.245) 68.678 ms xe-4-0-5.cr1-chi1.ip4.gtt.net (89.149.141.173) 58.822 ms 89.149.141.245 (89.149.141.245) 56.981 ms
11 427.xe2-0-0.br1.ch2.newcontinuum.net (173.205.36.74) 66.835 ms 56.525 ms 69.621 ms
12 xe2-0-3.br0.newcontinuum.net (173.243.122.246) 65.880 ms 60.630 ms 57.934 ms
13 29-96-79-64.as20278.net (64.79.96.29) 57.249 ms 64.362 ms 56.855 ms
14 87-15-88-167.reverse-dns (167.88.15.87) 57.526 ms 56.160 ms 56.265 ms

[DuncanBoaz]

Any update or resolution to this?

New to PH and experiencing this same issue.

[hashingpro]

Yeah the pool is down currently, no one is connected.