A little peace of mind.
See how Axiom is running, check your backups and find out what needs attention.
Use your existing Axiom password. Access is limited to the administrator. This browser has its own session.
Connecting securely…
Your Axiom, at a glance.
A clear view of the services that keep your apps connected.
Unknown
Needs your attention
Services
Every minuteEach check covers a different part of your system.
Your backups
Daily · 03:00 UKEncrypted copies, stored privately away from your server.
Unknown
Storage
Cloud totals every 6 hoursRoom on your server, and the space your private cloud copies use.
1 GiB = 1,073,741,824 bytes. Databases are included in server use. B2 has usage-based storage, with no fixed capacity limit.
Connected devices
Server observationsA sleeping phone can be perfectly fine. Contact times tell us when the server last heard from a device.
“Last server contact” records a successful workspace request, rounded by up to a minute. It does not measure completed sync or pending local edits.
When the whole server goes offline
Something doesn’t look right?
Keep your local app libraries and any queued edits. Start with the symptom below.
Only one app or device cannot connect
Check its internet connection and open the app again. Check the connection message inside the app. If other apps work and this page shows current healthy services, it may be a device connection or sign-in problem. An old contact time alone is not a fault. Preserve pending edits; do not reset the app or its library.
All Axiom apps cannot connect
Check your internet connection first. If the Core or Workspace service is unavailable, the server may need attention. Your local copies remain available, and queued edits can wait. Contact the administrator. If this dashboard also fails to load, whole-server availability has to be checked from elsewhere.
Mail cannot send or receive, but other apps work
Mail providers are separate from Axiom. Check your provider’s status and the account connection inside Mail. Healthy Axiom services do not prove your mailbox is connected. Keep drafts and queued messages. Do not change unrelated Axiom credentials.
A backup is late or its email is missing
Look at the last verified backup and latest attempt separately. A later failure does not remove the earlier successful copy. If the backup was verified but email was not accepted, ask the administrator to check the sender’s provider. If it was accepted, check Junk and the provider’s mailbox. Do not delete backup copies or share the recovery key.
Storage is low or a certificate is near expiry
Ask the administrator to review safe cleanup or more server capacity. Keep local copies and backups. Cloud version totals are estimates measured at the displayed time. For certificate problems, ask the administrator to check DNS and automatic renewal. Never bypass a browser security warning.
What these indicators can and cannot tell you
Service and disk checks run every minute and become Unknown after three minutes. B2 object and version inventories refresh every six hours and become Unknown after twelve hours. Public HTTPS checks validate trusted certificates from this server. Private storage checks use listings and metadata, without reading private file content or repeatedly uploading tests. An independently verified restore is recorded separately. The dashboard cannot see unsent edits on devices, mailbox delivery or a whole-server outage from its own host.