Skip to content

Securing a Lost Device

Account & Security 8 min read
On this page

If a phone or laptop with your Uptimia session on it is lost or stolen, or you think someone else has reached your account, work through the steps below in order. Start with the password. Changing it signs out every other device and breaks every saved "remember me" login at the same time, which is most of the job. Then revoke the API keys the device held, turn on two-factor authentication, handle a team member's device, and check the recent sign-ins and the audit log for activity while the device was gone. If you cannot sign in at all, Account and Login Recovery is the article you want.

Step 1: Change Your Password #

  1. Open Settings → Security from the avatar menu (top right).
  2. In the Change Password card, enter your current password in Current Password. Enter the new one in New Password, then again in Confirm New Password. The minimum is 8 characters.
  3. Click Update Password.

Saving takes effect at once:

  • The old password stops working.
  • Every other active session is deleted. From the account owner's seat, that covers the whole account: a browser still signed in on the lost device is signed out on its next request, and your team members each have to sign in again. The session you are using stays signed in.
  • The remember-me token is rotated. A saved "remember me" login on that device, and any direct-access link in an old Uptimia email, stops working.
The Change Password card on the Settings Security tab, with the current, new and confirm password fields and the Update Password button.Enlarge

Which sessions get cleared depends on the seat and the route:

  • On a team-member seat, only that member's sessions are cleared. A member changing their password never signs the account owner out, and never signs out other members.
  • On the account owner's login, a password reset by email clears every session, including the one that started it, then signs you in fresh. Use that route if you cannot sign in to reach the Security tab. See Signing In and Resetting Your Password.

Step 2: Revoke API Keys the Device Held #

A password change does not switch API keys off. A key stored in a terminal, a script or a mobile app on the lost device keeps working until you delete it.

  1. Open Settings → API Keys.
  2. Find the key in the table. The Last Used column tells you which keys are live.
  3. Open the row's ⋮ (three-dot) menu and click Delete, then confirm with Delete in the Delete API Key window.

The key stops working the next time anything tries to use it. Whatever else was built on that key stops working too, so replace it wherever it was legitimately in use.

The API Keys tab is visible to the account Owner and to Admin members only. If the key belonged to a limited seat you created for a script, deleting the seat removes its keys with it. See Read-Only and Group-Limited API Keys.

The API Keys table with a row's action menu open on Delete, and the Last Used column showing a recent date against each key so you can tell which ones are still in use.Enlarge

Step 3: Turn On Two-Factor Authentication #

With a second factor on, a password recovered from the lost device is no longer enough to sign in. In the Two-Factor Authentication card on the same Security tab, click Set up authenticator app to get 6-digit codes from an app such as Google Authenticator, Authy or 1Password, or Use email codes instead to get the code by email.

When you confirm an authenticator app and the account still has API keys, the setup offers Also revoke the keys, ticked by default. API keys never ask for a code, so leave it ticked unless you have already dealt with them in Step 2. The setup also gives you recovery codes. Store them away from the phone: each one signs you in once if the phone is lost.

If the lost device was the phone with your authenticator app, sign in with one of your recovery codes, then click Move to a new phone on the Security tab. It sets the app up on the new phone and issues a new set of recovery codes. Codes from the old phone and the old recovery codes stop working.

The factor is per seat. It protects only the identity that enabled it, so on a team account every member turns it on in their own Settings → Security. Turning email codes off later asks for your current password, which is what stops someone who has your session from quietly removing it. Two-Factor Authentication covers the code step, the 5-attempt cap, recovery codes and the recovery path.

If It Was a Team Member's Device #

The account Owner and any Admin can act from People → Users without waiting for the member:

  • Reset two-factor auth on the member's ⋮ (three-dot) menu, for a member who lost the phone with their authenticator app or can no longer receive their own codes. Uptimia clears the factor, deletes their authenticator app and recovery codes, and emails them.
  • Remove from account on the same menu. The seat loses access outright, and its API keys go with it.
A team member's row action menu on the Users roster, open on Edit access & profile, Reset two-factor auth and Remove from account, with each user's Last sign-in and 2FA on/off status beside it.Enlarge

Both are written to the Recent access changes card on that page and to the audit log. Ask the member to change their own password as well: only they can do that, and only their own password change clears their sessions.

Check Recent Sign-Ins and the Audit Log #

Uptimia records every sign-in and every failed sign-in attempt, for the account owner and for each team member, with the IP address, location and browser. These records are kept for 90 days. You can read them in three places:

  • Settings → Security, Recent sign-ins card: your own last 10 sign-ins and failed attempts, each with the browser, location, IP address and how you signed in. The session you are using is marked This device. Every seat sees its own list. The card is read-only: if a row is not you, change your password (Step 1).
  • People → Audit Log, Sign-in & 2FA tab (Owner and Admin only): every seat's sign-ins and failed attempts, plus two-factor changes such as an authenticator app turned on, moved or removed, and recovery codes used or replaced.
  • People → Users, Last sign-in column (Owner and Admin only): each seat's latest sign-in with the country flag and IP address. Hover it for the location, browser, sign-in method and exact time. The Status column shows Active with 2FA on or 2FA off, so you can see who still has no second factor.
The Recent sign-ins card on Settings → Security: the current session marked This device, a failed attempt marked Failed: Wrong password, and earlier sign-ins, each with the browser, location, IP address and sign-in method.Enlarge

The rest of the audit log records configuration changes with the person's name and the exact time: monitors created, edited, deleted, paused and resumed, maintenance windows, alerting teams, monitor templates, incident acknowledgements, and on the Access tab team invites, role changes, removals and API keys created or deleted. Integrations, branding themes and the account time zone are recorded too. Read it to see whether anything was changed while the device was out of your hands. It does not record contacts or status pages. The Account Activity Log covers what the page holds and how to export it.

The Emails That Tell You Something Changed #

Uptimia sends a security email on each of these events:

SubjectSent when
Your password was changedA password is changed from the Security tab
Two-factor authentication enabledEmail codes are turned on
Two-factor authentication disabledThe second factor is turned off (email codes)
Authenticator app two-factor authentication turned onAn authenticator app is set up
Your authenticator app was replacedMove to a new phone is completed
Authenticator app removed from your accountThe authenticator app is removed
New recovery codes createdRecovery codes are regenerated
A recovery code was used to sign inSomeone signs in with one of your recovery codes
Several incorrect sign-in codesToo many wrong two-factor codes are entered at sign-in, and code entry is paused for 15 minutes
A new API key was createdA key is generated in Settings → API Keys
Your account email is being changedAn email change is requested. This one goes to the old address

Warning: One of these arriving when you did not do it is the signal to change your password immediately. It means someone else is acting inside your account.

There Is No Per-Device Sign-Out List #

Uptimia has no active-sessions screen and no per-device revoke button. The Recent sign-ins card lists sign-ins but cannot end one. Changing your password is the control that ends other sessions, and it ends all of them at once.

Was this helpful?

Your answer helps the team improve this article.

Still need help?

Uptimia Bot answers right away and passes you to the team when it can't.

Source: https://help.uptimia.com/help/a/securing-account-after-lost-device