Well, it took longer than I anticipated, but [SteemDB.com](https://steemdb.com) is slowly coming back to life. The [data migration I started a couple days ago](/steemdev/@jesta/steemdb-migration-eta) completed earlier today and I'm bringing the services back online. If you still see the "DB Migration" message still (on every page), your DNS has not updated to the new server. The DNS should update in the coming hours and the site will then become available once more. If you're very impatient, you can always access the site via it's IP address: http://144.76.176.150 ## New Server The new server SteemDB is hosted on is now provided by @privex, and I've had great support from @someguy123 getting this all setup. SteemDB went from a 96gb RAM server with 8 cores to a 256gb RAM server with 12 cores. I've optimized and upgraded all of the software to the latest versions, configured the filesystem for high IO throughput, and should have plenty of room to grow over the next year or so. ## Current Issues and Status A few notes about this new deployment and issues surrounding the migration: - The database sync is currently catching up, as I write this it was processing block 18636474 (2018-01-02). So currently the 9 most recent days of data are missing from some sections. This new server is processing these blocks at a rate of about 3-6 blocks/second. We are currently at a height of 18892572, which means there's about 250k blocks that need to be processed. At a rate of 3 blocks per second (to be conservative), it will catch up to the current block height and finish processing in about 24 hours. - The witness pages and other sources that pull data live are unaffected by the sync process, but pages like an accounts transfers/votes will be impacted by the sync. - The account history module is disabled for the next 24 hours, so no new snapshots of accounts will be created until the sync is completed. - The apps page is missing data and somewhat broken, and I will investigate what's happening here. It's most likely due to the inactive history module, which also creates snapshots of app usage. - The homepage is no longer cached, so it's somewhat slow. I'll work on caching this again in the future. - Any missed blocks by witnesses during this migration were not recorded unfortunately. ## Where SteemDB goes from here Over the past month I've been doing a lot of thinking about the various projects I maintain in regards to the Steem ecosystem, and one reoccurring thought I have is that I have too many active projects. I am still in the planning phases, but one of my goals in 2018 is to shed or offload some of this workload so I can focus on the projects that actually matter to me, as well as the ecosystem as a whole. With that being said, SteemDB **isn't** one of the projects that I want to personally stop maintaining. For months now in casual conversations I've mentioned that I really want to rebuild SteemDB and create a v2 of my block explorer code, and I am hoping to find the time to do so this year. SteemDB was my 2nd Steem related project (created Aug 2016) and I've learned so much since it's creation. In 2018, I would very much like to take the time to sit down and rebuild SteemDB into something better. Improve the technology, the scalability, it's responsiveness, and usefulness. These foundational tools (wallets, blockexplorers, etc) are crucial to on-boarding new users and developers alike, while providing external transparency into the operations happening on the blockchain. Luckily, this new server has room to grow, and I can fit a v2 right alongside v1 until it's ready to replace it :)

RE: Ecency waves Apr 23