I forked twice since my last comment and it's clearly not just me.
getblockhash 458553
000000006b5d12bbbd16654648bfa6eb05bbab925b512aac597191920699cb21
Some oddities were observed 14 hours ago, difficulty abruptly jumping from 2 to 12 and then back down, before any forks were reported to be found. This does make me suspect the forks may have been from malicious attempts to attack the EverGreenCoin network. However they may have been caused, I apologize.
This block hash you mentioned does concur with all the seednodes and the block explorer.
EDIT: Perhaps the many Windows wallets running the v1.1.2 code because the upgrade to v1.2.1 had yet to be made available formed a consensus and pulled other nodes into an incorrect fork.
Still seeing some v1.0.0 wallets in my peers list as well which may be causing some issues...
Haven't forked again here since the initial fork and compiling the new wallet and re-syncing...