At the official mining pool of the NYC http://nyc.mypool.club/index.php there are no problems with the blocks.

Blocks are being investigated. http://nyc-block.mypool.club/

The miners are successfully mined.

Support NYC and make money by mining. Moreover, the complexity is now minimal.

But with the pool https://hobbyistpool.ddns.net/nyc/index.php the second day of the big problem.

Who has problems or is suspected - go to the official pool without FEE http://nyc.mypool.club/index.php

Yes ! Yes sir! ///Since (most probably) ProHashing re-enabled their mining pool towards our network, after updating their coin daemon to v1.3.0, it seems like we are suffering from network segmentation.
Probably due to the fact that when they started mining, their own coin daemon did not have connections to older nodes (v1.3 rejects nodes older than 1.2.0.x), they didnt broadcast to those older nodes.
Also miners on the older nodes didnt connect back to the 'new network' via an intermediate 1.2.0.x.
The issues, as far as we've seen, fix themselves in time, as nodes reconnect to other nodes all time. This means that they also sync up, doing a reorganize.
It seems the more 1.3 nodes that came into being and the fewer 1.2 nodes available the pre 1.2 nodes monopolize the connections to the remaining 1.2 nodes.///