Thinking about this a little more, taking a timeline view of things,

<< < @ >

is the wrong way round. It's more normal to see

past — present — future

so I suggest an alternative placement of the arrows. To begin with, matching the current feature set,

< @ > >>

then if you choose to add a jump to earliest feature,

earliest < @ > current
or
oldest < @ > current

(The table/listings are fine. Most recent sessions at top is expected behaviour.)

Incidentally, what's the clickable '@'?
If it's refresh, you might spell it out. No shortage of width in this UI.

Thanks
Graham