Skip to service status
FinanlySystem status
SERVICE HEALTH, IN THE OPEN

A clear view of
what’s running.

Current health, hourly availability and observed incidents across Finanly. Measured from our infrastructure, with gaps shown openly.

Checking service health

Current availability cannot be confirmed. Missing or stale measurements are never shown as healthy.

Awaiting the first probe cycleChecks every 30 seconds · times in UTC
Successful recorded checksSome failed checksAll recorded samples failedMissing or incomplete coverage

Loading measured service status…

OBSERVATION LOG

Incidents in the last 24 hours

Automatically detected · 1-minute resolution

These reports describe failed health checks. They do not establish a root cause or a customer-wide impact. A recovery requires a successful observation.

Incident history is unavailable.

HOW TO READ THIS PAGE

Evidence first.
No guessed uptime.

Availability is successful recorded samples divided by all recorded samples. Coverage is the percentage of expected samples that were recorded. Read both: 100% availability with low coverage does not mean an hour was fully monitored.

History includes UTC hours up to the latest recorded samples, up to 14 days. The current hour uses only elapsed time. New monitoring appears immediately; earlier unobserved hours stay unknown. Missing checks stay unknown. Current observations expire after 90 seconds.

Probes run from Finanly infrastructure and check service readiness, not every customer connection, financial operation, model answer or third-party network. This page shares infrastructure with Finanly; it is not an independent global measurement.

Read the public JSON report