Quote from: dooglus on May 05, 2015, 05:35:13 PM

Quote from: akeetlebeetle on May 05, 2015, 02:46:14 PM

Quote from: cloverme on May 05, 2015, 02:42:42 PM

Quote from: Joecker on May 05, 2015, 01:41:54 PM

Any info on the current network situation ? Khashier showing old data. Transactions not getting through.

I'm curious as well, I have a transaction that's not showing up on the network and a deposit address at poloniex that's not receiving this morning. None of my transaction is showing up at Khashier either. My own clam client is showing 0 network connections... Seems like something is not working somewhere in the clam universe.

I'm having problems as well. Tried to send from Poloniex to JD and 8 hours later I'm still waiting.

Edit: Apparently, the node went down and has been brought back up. I got my coins and everything's fixed.

Can you imagine what the reaction would've been if bitcoin was out of service for 8 hours

From what I understand, both khashier (the block explorer) and poloniex's CLAM wallet (the biggest CLAM exchange) were down for hours overnight. I haven't yet been able to get in touch with the poloniex wallet manager to find out whether the two events were related. I can't imagine why poloniex would have a dependency on khashier. I guess it's possible that some weird transaction triggered a bug that affected both khashier and poloniex and brought them both down.

Just-Dice and the CLAM network as a whole both stayed up and working fully throughout. But with the only block explorer and the only significant exchange both out of action for hours, it would have looked to an outsider as if "CLAM is down". That wasn't the case.

Edit: I spoke with polo's wallet manager. He was unaware that there had been a problem, but when he checked his their CLAM wallet it was showing that it was only connected to a single peer. It's likely that the single peer went down for a while, leaving polo's wallet disconnected from the network.

We really need more people to run their own CLAM wallet, and open a port (31174/TCP is the default p2p port for CLAM) on their firewall to allow incoming connections. Of course, if poloniex themselves didn't have a "no open ports" policy, they wouldn't have this problem...

Edit2:

Quote

18:43 Does clam support addnode in the conf?
18:46 yes
18:46 cool
18:46 i'm adding them now
18:50 ok, it's restarting with lots of nodes
18:54 "connections": 11,

I'm running the client on 2 boxes. Linux and windows. Windows has 16 connections and linux has 74. Both have been running fine for weeks. Strange problem, someone else above mentioned not having peers.