Status

Status

All systems operational — as of the date above

This page is a plain statement of what's up, what we're targeting, and what's actually watching the service today — not a marketing claim dressed up as a dashboard. Where something is manual rather than automated, we say so, because a due-diligence reviewer or a customer during an incident finds the gap either way.

Current status

All systems operational, confirmed manually as of the "last updated" date above. This status is reviewed and republished by hand today — it is not yet a live feed. Treat the date at the top of this page as the freshness of the information, the same way you would with any status page that hasn't moved to real-time yet.

Separately, the in-app apps hub shows an "All systems live" indicator inside the product. That indicator is today a fixed label, not wired to any check — it is not a live signal and should not be read as one; this page is the only place we make an actual status statement.

Availability target (SLO)

We target 99.5% monthly uptime for the hosted app at app.artifinance.io, measured against a successful response from the health endpoint. This is a target we're holding ourselves to going forward, not a historical average — we don't yet have an automated uptime history to report a real measured number against, and we'd rather state that plainly than publish a percentage we can't back with data. As the monitoring described below moves from configured-but-unapplied to live, this section will report real, measured numbers instead of a target.

Incident severities we use internally:

What's monitored today

All of the above are real, reviewable configuration in this repository's monitoring/ directory. Honestly, as of this page's last update, none of it is applied yet — it is not yet applied to the live Google Cloud project, and no alert is yet wired to a paging channel (email/SMS/Slack) — so today, a real outage is first noticed by a human checking, or by a customer reporting it, not by an automated page. Applying that configuration and wiring a paging channel are the two concrete steps that would make this page's "as of" caveats above go away.

Incident history

No incidents have been recorded on this page since it was published (2026-08-13). This is a fresh page, not a claim of a long clean track record — check back as it accumulates real history.

Report an issue

If something looks down or slow, email hello@artifinance.io with what you're seeing and when — we'll investigate and update this page.