# See where you are logged in and recent activity

> Check your active panel sessions, sign out a lost device or everywhere else at once, and read the activity log of logins and security changes.

Source: https://rack4.io/help/sessions-and-activity · Updated: 2026-10-21

Every browser signed in to your Rack4 login is listed under **Where you're signed in** in the [security center](https://my.rack4.io/account/security), with its address and when it was last seen, and you can sign any of them out. The **activity log** lists your last 50 sign-in and security events. Worth a glance now and then, and definitely after you've used a computer that isn't yours.

## What you need

- A Rack4 login. Sessions and the activity log are about your own login, whichever team account you have open.

## Who's logged in

Open **Account → Security** (the Account overview's **sessions** line links there too). Each signed-in browser has a row: the **device** (something like "Firefox 131 on Linux", with an icon for computer or phone), the **address** it last came from, when it was **last seen**, and when it **signed in**. Yours is marked **this session**.

[Screenshot: The Where you're signed in table: this session in Chrome 130 on Windows, Firefox 131 on Linux and Safari 18 on iPhone, each with address, last seen, signed in, and log out or sign out] We show addresses as we saw them and don't look up locations.

Sessions end on their own after 14 days without use, and after 30 days at most, however often you use them. Then you just log in again.

To sign out a device:

- **sign out** on its row signs out that one browser. It finds out the next time it loads a page.
- **sign out everywhere else** signs out every browser except the one you're using.
- **log out** on your own row, or **Log out** at the top of any page, ends your current session.

### Check it worked

The row disappears from the list, and a **Session signed out** (or **Signed out everywhere else**) line appears in the activity log.

Changing your password signs out every other session too, but leaves your API tokens working. Resetting a forgotten one signs out all of them and revokes every API token.

## New sign-in emails

When your login is used from a browser it hasn't seen before, we email you the browser, address and time, and it shows in the panel's bell. A sign-in from a browser you've used before but from a new address gets one notice too ("Login from a new address"), never both for the same sign-in. We send at most three new-browser emails an hour; the bell shows every one. Clearing your cookies makes a browser new again, so expect one after that.

If it was you, there's nothing to do. If it wasn't, follow [Something you don't recognise](#something-you-don-t-recognise) below.

## The activity log

Choose **activity log** on the Account overview, or **full activity log** under the security center's timeline, to see the last 50 sign-in and security events, newest first, each with the time, address and device.

[Screenshot: The activity log table: logins, logins from a new browser, two failed logins, API tokens created, an SSH key added and a password change, with time, address and device] Failed logins from addresses you don't know are usually bots. A login you didn't make is not.

That covers:

- logins, failed logins, and logins blocked after too many failures;
- wrong 2FA codes, and recovery codes used;
- password changes and reset requests;
- 2FA turned on or off, and sessions signed out;
- SSH keys added or deleted, API tokens created or revoked;
- passkeys added, removed or refused, recovery codes made, email changes, and downloads of your data.

On a [team](https://rack4.io/help/teams), changes made on the account itself (servers, billing, the team) are in the team's **account activity**, with who made each one.

## Something you don't recognise

A few **Failed login** lines from addresses you don't know are usually just bots trying common passwords. With a decent password and 2FA, they get nowhere, and you can ignore them.

A **Logged in** you didn't do, or a change you didn't make, is different. Then:

1. Choose **sign out everywhere else**.
2. [Change your password](https://rack4.io/help/reset-password).
3. Turn on [two-factor authentication](https://rack4.io/help/two-factor-authentication) if it's off.
4. Revoke any [API token](https://rack4.io/help/api-tokens) you didn't create, and delete any SSH key you don't recognise.
5. [Open a support ticket](https://my.rack4.io/support/new?category=account) and tell us what you saw, even if it turns out to be nothing.

## When support looks at your panel

To answer a [support ticket](https://rack4.io/help/support-tickets), a member of our staff can sometimes look at your panel the way you see it. They can only look: nothing they click there changes anything, and pages like the serial console, 2FA setup and ordering stay closed to them. A view lasts at most 30 minutes, they have to give a reason, and every page they open is written to our internal audit log. They never use or see your password, your sessions or your 2FA codes, so a staff view doesn't show up in your sessions list.

## Next steps

- [Check your account in the security center](https://rack4.io/help/security-center)
- [Turn on two-factor authentication](https://rack4.io/help/two-factor-authentication)
- [What to do if your server is compromised](https://rack4.io/help/what-to-do-if-compromised)