Taxmo Service Status
The status page shows the live health of the Taxmo service: database connectivity, the schema the application depends on, the main read paths, and the connected providers. Every line is a probe run at the moment the page loads, not a cached figure or a manually updated banner.
What the page reports
At the top is the overall state, either all systems operational or a count of failing checks, together with how long the service process has been up and the time the checks were run. The page refreshes itself while it is open.
If the page cannot read a status at all, it says so. That is itself a signal: the service did not answer.
What is checked
Checks are grouped into four sets. Core covers database connectivity. Schema confirms that the tables the application relies on are present, including the chart of accounts, journal entries and lines, invoice templates, the tax calendar and bank transactions.
Read paths run actual queries behind the invoice list and the income entries list, so a failure means the page a user would open is broken, not just that a table exists.
Providers covers the outbound integrations: the bank import provider and the HMRC connection. Each check reports how long it took in milliseconds, so a slow dependency is visible before it fails outright.
How to read a failing provider
A provider showing as failing usually means its credentials are not configured in that environment. That is expected on a preview deploy and does not indicate an outage of the live service.
A failing core or schema check is different. It means the application cannot reach its database or is missing structure it depends on, and the user-facing effect is immediate.