First let me say that I'm very happy with the new backend! Great work on that!
@kersing Agree with you! Although I must say that not having the old API / Croft environment available is at the moment is quite a nuisance. I guess many people have built their first prototypes on this. Not supporting it anymore (with an effective result of shutting it down it seems the last few days) will urge people to switch over to the new backend. Although it probably will take people some time to get their demo's / pilots converted to the new backend.
Also the issues that occur because of checking the counters of the nodes don't help getting current demo's / applications alive again using the new backend.
So w.r.t.
I volunteer to help, keeping the old infrastructure up & running so people can have a more smooth transition to the new backend so they are not loosing their demo projects. I propose to do this only for an announced fixed period of time after which the old backend will be retired. This keeps the pressure on people to convert to the new backend.
I also wonder about the great dynamic gateway maps we used to have several of. Will the required information be available again or do we have any plans to again open this data to the public from the new router component (I think that is where the info is gathered in the new infrastructure?).
I think the old gateway status pages were a great way to help build the community as anyone could see where active gateways were available. I was able to get into contact with several gateway owners using this info (and was not considered a stalker 
). I'm available to help on this part too.
Let me again state I'm grateful for the new backend, just trying to help out with a smooth transistion from the old to the new backend.