no they're not - look at the block time and how they come in chunks. -the wallet has problems, because the nodes are unreliable - go ahead and tail the debug.log file and you'll see. I have over 16 other wallets installed and this wallet's block chain is sporadic at best.
i just did that.. nothing special mate.
also the "nodes".. everyone is a "node" every wallet, every pool.. everyone that is running the coin. so there are no nodes that can be "turned on or off" by the dev which make the network "sporadic" or unreliable. look at the connections your wallet has ( do a ./quatloo getpeerinfo), ALL those connections must be shut off AT ONCE to get the network to the behaviour you mention.
I suspect your server, your connectivity or your pool wallet has a problem, not the network.
look here:
https://qtl.suprnova.cc/index.php?page=dashboard
and refresh every 2-3 mins.. you'll see the blocks come in as usual and expected
actually - I have been comparing dashboards and I am right - often it does not refresh every two to three minutes - sometime it can be 10 to 15 minutes or longer because a new block is released into the block chain.
http://qtl.lifeforce.info/index.php?page=dashboard
same mpos software - same block chain - the block chain freezes from time to time....and then all of a sudden a bunch of blocks are released.
46501, 502, 503, 504 and 505 were all released into the chain within 1 minute of each other.
these two blocks were 9 seconds apart
2014-09-11 22:04:20 received block b9c88b91d00f478a38d35ffe53268b20f72b143a56a197403f85aacad8d86d88
2014-09-11 22:04:20 Committing 1 changed transactions to coin database...
2014-09-11 22:04:20 SetBestChain: new best=b9c88b91d00f478a38d35ffe53268b20f72b143a56a197403f85aacad8d86d88 height=46503 log2_work=53.199544 tx=59785 date=2014-09-11 22:03:38 progress=0.999992
2014-09-11 22:04:20 ProcessBlock: ACCEPTED
2014-09-11 22:04:20 CreateNewBlock(): total size 1000
2014-09-11 22:04:38 ThreadRPCServer method=getblockhash
2014-09-11 22:04:42 AcceptToMemoryPool: 192.99.167.159:17012 /Satoshi:0.1.1.2/ : accepted e01ab890d9e636efded7d3ff0c7fb21b3b045d5e3ce2939093207fcc8466cb3d (poolsz 1)
2014-09-11 22:04:42 CreateNewBlock(): total size 1193
2014-09-11 22:04:42 received getdata for: tx e01ab890d9e636efded7d3ff0c7fb21b3b045d5e3ce2939093207fcc8466cb3d
2014-09-11 22:04:55 AcceptToMemoryPool: 72.78.100.12:17012 /Satoshi:0.1.1.2/ : accepted 2a84cb58b45ca9cda1d0b839791d9284af90518992980f72aea715fbbdd08343 (poolsz 2)
2014-09-11 22:04:55 CreateNewBlock(): total size 1385
2014-09-11 22:05:01 ThreadRPCServer method=getinfo
2014-09-11 22:05:01 keypool reserve 2
2014-09-11 22:05:01 keypool return 2
2014-09-11 22:05:01 ThreadRPCServer method=listsinceblock
2014-09-11 22:05:02 ThreadRPCServer method=help
2014-09-11 22:05:02 ThreadRPCServer method=listaccounts
2014-09-11 22:05:02 ThreadRPCServer method=getbalance
2014-09-11 22:05:02 ThreadRPCServer method=listaccounts
2014-09-11 22:05:02 ThreadRPCServer method=getbalance
2014-09-11 22:05:10 received block c4ecde1f809648d5cb1402f6380b492da613dcc85bc59aa2cfe7fcaa4a76bcbd
2014-09-11 22:05:10 Committing 3 changed transactions to coin database...
2014-09-11 22:05:10 SetBestChain: new best=c4ecde1f809648d5cb1402f6380b492da613dcc85bc59aa2cfe7fcaa4a76bcbd height=46504 log2_work=53.199598 tx=59786 date=2014-09-11 22:03:47 progress=0.999984
2014-09-11 22:05:10 ProcessBlock: ACCEPTED
2014-09-11 22:05:10 CreateNewBlock(): total size 1385
2014-09-11 22:05:10 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:05:17 getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
2014-09-11 22:05:32 received block 018f32f6ab2aad1ab432eab4615b5005439c562da7da3ac46414fd9e8eac3ec6