Skip to content
Forticia
Research
Quantitative FinanceEquities, FX, futures. Factors and backtests, every run replayable.Computational BiologySequence, folding, simulation. Versioned, reproducible labs.Cultural IntelligencePhilosophy, governance, ethics. How institutions decide and answer for it.AI InstrumentationPrivate models. Multi-agent orchestration. Guardrails on write.View all research
Quantitative Finance
  • Equities, FX, futures
  • Factors and backtests
  • Every run logged and replayable
InfrastructurePapersPolarisLink™About
Sign inRequest access
Request access

Research

Quantitative FinanceEquities, FX, futures. Factors and backtests, every run replayable.Computational BiologySequence, folding, simulation. Versioned, reproducible labs.Cultural IntelligencePhilosophy, governance, ethics. How institutions decide and answer for it.AI InstrumentationPrivate models. Multi-agent orchestration. Guardrails on write.

Platform

InfrastructurePapersPolarisLink™About
Request accessSign in
Forticia

A private institute for computational research. It publishes original research and runs a governed environment where every run is logged and replayable.

Sign inSystem status

Research

Quantitative FinanceComputational BiologyCultural IntelligenceAI Instrumentation

Infrastructure

WorkspacesHelper planeGoverned AIPapersStatus

PolarisLink™

SpecificationQuickstartClientsChangelogGitHub repository

Institute

AboutFAQRequest accessContactSign inForticia on GitHub

Forticia publishes research and simulations. Nothing on this site is investment advice.

Official channels: forticia.uk and github.com/Forticia

© 2026 ForticiaPrivacyTerms
  1. Home
  2. Status

System status

Measuring now

The first round of checks is running.

Waiting for the first resultNext check in 15 s

Rechecks every 15 s while this tab is visible. Nothing here is estimated: a check that cannot be measured says unknown.

–/7checks operational

Services

  • Operational
  • Degraded
  • Down
  • Unknown

Reachability

Requests your own browser makes right now. If these fail, the problem is between you and us, or with us.

  • Latest result
    Waiting for the first measurement.
    Measured by
    Your browser
    This visit
    No samples yet
    Method
    Your browser requests the site root without cache and reads the response headers.
    Operational when
    An HTML document is returned with HTTP 200 in under 1.2 s.
    Degraded when
    The round trip takes longer than 1.2 s, or a non-200 success code is returned.
    Down when
    No response, no answer within 6 s, or an HTTP 5xx error.
  • Latest result
    Waiting for the first measurement.
    Measured by
    Your browser
    This visit
    No samples yet
    Method
    Your browser requests GET /api/health and checks the body.
    Operational when
    HTTP 200 with {"ok":true} in under 1.2 s.
    Degraded when
    The answer takes longer than 1.2 s, or the body is not what the endpoint documents.
    Down when
    No response, no answer within 6 s, or an HTTP 5xx error.
  • Latest result
    Waiting for the first measurement.
    Measured by
    Your browser
    This visit
    No samples yet
    Method
    Your browser requests GET /api/polarislink/spec and checks that a JSON document naming the protocol comes back.
    Operational when
    HTTP 200 and a JSON document with a protocol field, in under 1.2 s.
    Degraded when
    HTTP 429, a slower answer than 1.2 s, or a body without the expected field.
    Down when
    No response, no answer within 6 s, an HTTP 5xx error, or the route is missing (HTTP 404).

Dependencies

Checks our API runs on itself and reports. Each is cached for a few seconds and carries its own timestamp.

  • Latest result
    Waiting for the first measurement.
    Measured by
    Our servers
    This visit
    No samples yet
    Method
    The API runs a trivial query over its own database connection and times it.
    Operational when
    The query returns in under 750 ms.
    Degraded when
    The query succeeds but takes longer than 750 ms.
    Down when
    The query fails or does not return within 2.5 s.
  • Latest result
    Waiting for the first measurement.
    Measured by
    Our servers
    This visit
    No samples yet
    Method
    The API opens the archive root and reads its first entry, then times it.
    Operational when
    The root is readable, not empty, and answers in under 1 s.
    Degraded when
    The root is readable but empty, or answers slower than 1 s.
    Down when
    The root is missing or unreadable, or does not answer within 2.5 s.
  • Latest result
    Waiting for the first measurement.
    Measured by
    Our servers
    This visit
    No samples yet
    Method
    The API opens a TCP connection to the listener and reads its SMTP greeting. No message is sent.
    Operational when
    A greeting starting with 220 arrives in under 1 s.
    Degraded when
    A greeting arrives but is unexpected or slower than 1 s.
    Down when
    The connection is refused, or no greeting arrives within 2.5 s.
  • Latest result
    Waiting for the first measurement.
    Measured by
    Our servers
    This visit
    No samples yet
    Method
    The API counts heartbeat records from non-human nodes received in the last 5 minutes.
    Operational when
    At least one agent heartbeat arrived in the last 5 minutes.
    Degraded when
    Not used. Silence cannot be told apart from idleness.
    Down when
    Not used. With no recent heartbeat the row shows as unknown instead.

Pulse lines plot the latency of this visit’s own samples, newest on the right, on a fixed 0 to 1.5 s scale. Red ticks are failed checks, hollow dots are unknowns. Nothing is drawn for time before you opened the page.

How we measure this

Two kinds of evidence appear on this page, and each row says which it is. Browser checks are requests your own device makes. Dependency checks are run by the API on its own host and handed to you. Open any row above to see exactly how it is judged.

The checks use real timeouts and real responses. When a check cannot run, for example because the API is unreachable, its row reads unknown. It is never defaulted to green.

What is not covered: the authenticated real-time event stream needs credentials, so it is not probed from a public page. The protocol gateway row shows that the router answers, not that stream events are flowing.

Run it yourself

curl -s https://www.forticia.uk/api/health
curl -s https://www.forticia.uk/api/status/checks

The second endpoint is public, read only and cached for a few seconds. It reports a state, a timestamp and a latency for each dependency, and nothing about the host.

How each check is performed and judged
CheckMeasured byMethodOperationalDegradedDown
Web applicationYour browserYour browser requests the site root without cache and reads the response headers.An HTML document is returned with HTTP 200 in under 1.2 s.The round trip takes longer than 1.2 s, or a non-200 success code is returned.No response, no answer within 6 s, or an HTTP 5xx error.
API gatewayYour browserYour browser requests GET /api/health and checks the body.HTTP 200 with {"ok":true} in under 1.2 s.The answer takes longer than 1.2 s, or the body is not what the endpoint documents.No response, no answer within 6 s, or an HTTP 5xx error.
PolarisLink protocol gatewayYour browserYour browser requests GET /api/polarislink/spec and checks that a JSON document naming the protocol comes back.HTTP 200 and a JSON document with a protocol field, in under 1.2 s.HTTP 429, a slower answer than 1.2 s, or a body without the expected field.No response, no answer within 6 s, an HTTP 5xx error, or the route is missing (HTTP 404).
DatabaseOur serversThe API runs a trivial query over its own database connection and times it.The query returns in under 750 ms.The query succeeds but takes longer than 750 ms.The query fails or does not return within 2.5 s.
Data archiveOur serversThe API opens the archive root and reads its first entry, then times it.The root is readable, not empty, and answers in under 1 s.The root is readable but empty, or answers slower than 1 s.The root is missing or unreadable, or does not answer within 2.5 s.
Mail intakeOur serversThe API opens a TCP connection to the listener and reads its SMTP greeting. No message is sent.A greeting starting with 220 arrives in under 1 s.A greeting arrives but is unexpected or slower than 1 s.The connection is refused, or no greeting arrives within 2.5 s.
Agent heartbeatsOur serversThe API counts heartbeat records from non-human nodes received in the last 5 minutes.At least one agent heartbeat arrived in the last 5 minutes.Not used. Silence cannot be told apart from idleness.Not used. With no recent heartbeat the row shows as unknown instead.

Incidents and uptime

No incident history is recorded yet.

This page shows what can be measured at this moment. Past incidents, 30 day and 90 day uptime figures are not displayed because nothing stores the results of earlier checks. We would rather leave the space empty than publish a percentage we cannot back.

If something looks wrong while this page is green, tell us through the contact page. A check we do not run cannot show up here.