I'm suck on the battle part of the tutorial. It wants me to (and I'll quote it just in case I am reading it oddly) "Select Lvl 1 Nameless (Keeper Tutorial) opponent and click Accept Challenge. Fight him and win!"

The problem is that there is no lvl 1 Nameless with a Keeper called Tutorial. And the refresh button doesn't seem to do anything.

Edit- Here is a screenshot of what I see on the first page.

There may be two things happening. 

It's on another page, not page 1.

Or the server snafu happening right now has prevented the tutorial pet from functioning properly, in which case you get to sit and wait with the rest of us in the sad boat. 

It's dropped down to one page and still no tutorial pet. Ah, well, I guess I can just keep on checking in on it to see if it decides to pop up at some point.

Thank you for the feedback, Monues!

Please try again, it must be working fine now.

You registered on a very unlucky day - we had a botnet attack on the servers of our provider, and something went wrong because the servers were extremely overloaded. Everything seems to be fine now, but we had to fix manually some collisions including the one that affected your account.

We're very sorry for the inconvenience!

Oh I see them now! Thank you for the update!

I registered three days ago and still don't see this Lvl 1 Nameless (Keeper Tutorial). I've been checking constantly.

Finally popped up, but that was frikin' annoying.

Rumour13, we fixed your tutorial challenge. We're very sorry for the inconvenience.

Please report to Bugs thread at once for quicker resolution when encountering an obvious bug. 

This is a very rare bug which happens with no obvious reason. We had only a few cases since the game launch. We digged through all the relevant code with each of the three reports we've got, but everything is perfect there. It looks more like an exception when a database fails to resolve several simultaneous queries properly or something like that. In other words, we can't prevent it but only catch and fix when it already hapenned. It wasn't a systematic error before but now when we got a third report it seems to be such. We added an autofixer for such cases. 

Thank you for that. Should I still add a bug report or is that a moot point now?

Rumour13, no need for an additional bug report, we've already seen your post here :)