Unfortunately, there was a problem with the Resolver during the last few days. It reacted very slowly to any kind of request. As a matter of fact, those things always seems to pop up when you are out of town and it got proven this time again. It is fixed by now, so we apologize for any inconveniences this might have created.
On an additional note: we have some scheduled database updates the next few days, so the service might react a little bit slower again – however, not even close to the degree it has been the previous days (which was a software bug combined with a network problem – and both worked “perfectly” together)