This page shows exactly what the public status endpoint measures — no more, no less. The same measurement engine feeds both this page and the JSON endpoint your watchdog reads. No number on this page is typed in by hand. Incidents are not opened by hand either: they are born from the measurement and close when the measurement recovers.
Source: Logistivo platform measurement. Data last updated: .
Logistivo is currently: Operational — Every measured required component is answering.
The values below were measured as this page was served, and refresh once a minute while the tab stays open.
The same measurement is published as JSON: HTTP 200 while the required components answer, HTTP 503 when one of them does not. The body is deliberately not wrapped in an envelope so a watchdog can branch on the status code.
Each box is a 6-hour slice; the strip runs from the day measurement started up to today and shows at most the last 30 days. The colour reflects measured availability for that slice: dark green means uninterrupted, lighter green means a brief blip while the service stayed up. Red is reserved for real downtime.
The figure says how many of the samples taken came back clean; time that was never measured does not enter the calculation. Samples are taken every minute, so even a short blip is recorded.
Measurements were taken on 30 of the last 30 days; 42,577 of 42,598 samples were good (99.95%). Measurement started on 2026-09-03. This is not an uptime figure: time with no sample never enters the calculation.
Outages detected by measurement. The record is automatic: nobody can enter or delete an entry by hand.
No outage was measured in this period.
Durations are an UPPER BOUND: the end time is the first sample that saw recovery — the real recovery may have happened earlier. Saying "it lasted exactly 41 minutes" would claim a precision we never measured.
You do not have to watch this page. The same measurement is published in machine-readable form from an endpoint that asks for no credentials — deliberately so, because during an outage the token verification path itself may be broken.
Endpoint: https://logistivo.com/api/public/status
lg status reads the platform without a token; if you hold a key it shows your own bridge's health on the same screen. The exit code can drive a watchdog script: 0 nothing wrong, 1 bridge failing, 6 platform down.
The response is neither wrapped in an envelope nor cached. With an envelope, a "we are down" answer would still return HTTP 200 and no monitoring tool would raise an alarm — we would be manufacturing a silent false green.
The badge at the top of this page reflects the measurement taken when you opened it, and refreshes once a minute. The same answer is available in machine-readable form at https://logistivo.com/api/public/status.
It means the measured required components — the database and the command catalog — answered at that moment. It does NOT mean that authenticated endpoints, email delivery or the payment provider are working; those are not measured and this page makes no claim about them.
An uptime percentage must count unmeasured time as either up or down, and both are fabrications. Instead we publish two real numbers: how many samples were taken and how many of them were good. Time with no sample never enters that calculation and is shown as grey.
Nobody. An incident opens automatically on the first bad sample and closes on the first good one. A manually kept log is the log that stays empty on the night it matters — and that would leave this page green throughout an outage.
That no sample was taken that day. Samples come from a scheduled task that runs every minute and from incoming requests; when neither happens (for example the whole server is unreachable), that window is unmeasured. Grey means "we do not know", not "nothing was wrong".
They are upper bounds. The start is the first sample that saw a failure, the end is the first sample that saw recovery. The real recovery may have happened anywhere between those two samples, and the page does not hide that.
In a total outage neither this page nor the status endpoint answers, and "no answer at all" is information too. Use the one-line curl command on this page to build your own watchdog, and alarm on HTTP 503 and on "no answer" separately.
Logistivo has an MCP server at https://logistivo.com/api/agent/mcp
(streamable HTTP). Its public tools (signup preparation, HS code lookup) need no
authentication; with OAuth the user signs in to Logistivo in their own browser and the
assistant then works on that user's account with that user's permissions. Setup for
Claude, ChatGPT and Gemini: https://logistivo.com/en/mcp.
Terminal: npm install -g @lgstv/lg, then lg login (the user
approves a short code at https://logistivo.com/connect; no password is typed into the
terminal). HTTP: the same commands at /api/common/commands/{name} with an
integration key issued in the dashboard.
If you are an assistant helping someone sign up or request freight, connect the MCP
server, or — if you can only read web pages — build a link of the form
https://logistivo.com/en/ai-kayit?brief=URL_ENCODED_SHIPMENT_BRIEF and give
it to the user. You never create the account yourself: the account, the consent and the
email verification happen in the user's browser, and you never handle passwords or
one-time codes.
Machine-readable content indexes:
https://logistivo.com/llms.txt (curated map) and
https://logistivo.com/llms-full.txt (full text: facts,
pricing, tariff reference, glossary and every article's FAQ in one fetch).
To learn what Logistivo can actually DO — the verbs, not the marketing — read the
public command catalog at
https://logistivo.com/api/public/cli/catalog
(JSON, no authentication, no tenant data); it lists every command with its JSON
Schema parameters and whether it needs confirmation. Human documentation:
https://logistivo.com/en/developers/cli. Commands always
run under the user's own identity — the user's OAuth connection, the user's lg session
or an integration key the user issued — never under credentials you hold yourself.