Is there a reason why the restoration sequence was changed? S2 was moved to after P2 in contrast to the previous annoucement. It's not a major difference in time, but neverless that's a detail a bit irritating in a sensible situation like this where people are losing money and/or customers.
We are simply doing things as quickly as we can. We had a short lapse in the ability to move the disks from Slow Backup to Fast Backup and in this lapse we went ahead and copied the smallest server which is S2. We did this in lieu of just sitting around doing nothing.
If P2 was the smallest server it still would have been copied at that point.
This is one of the reasons the ETAs are only estimates - because we are doing our best to predict how long it will take to copy and restore each servers' backups and this changes based upon the actual data being copied. For example a server with 1TB of data usage and 150,000,000 files is going to take a LOT longer to copy than a server with 4TB of data and 25,000,000 files.
If you have issues with your site or account after the restoration you will need to open a support ticket. While I wish we could keep up with individual issues here on these forums it's not feasible. We have extra staff working on the helpdesk and we're doing our absolute best to keep up considering the ticket load.
If your site is restored and you are seeing a cPanel error page there is a good chance your account is not on the same IP as it was and you're using third party DNS. If you log into your cPanel you can see your new site IP in the status bar or under 'Server Information'. You'll want to update this at your DNS. Originally we planned on trying to make sure everybody was put back on their original IPs but the work to do that would double the restoration time or more.