System status
Is it us?
A live check, run when you loaded this page. The marketing site you are reading runs as a separate service from the application, so this page can still tell you the application is down — which is the only arrangement under which a status page means anything.
Responding normally
The application answered this check without error and within the expected time.
- Checked
- Response
- 55 ms · HTTP 200
- Endpoint
- https://app.meridianhdx.com/api/public/site-config
What this check actually covers
What it tells you
- Whether the application is reachable from outside our network right now
- Whether it answered without an error status
- How long it took to answer
What it does not tell you
- Historical uptime — we do not publish a percentage, because we are not yet measuring one continuously
- Incident history, for the same reason
- Whether any individual feature is working; this is one request to one endpoint
- Whether a background job, an email, or a payment provider is healthy
Continuous monitoring with a real incident log is work we have not done. Until it exists, this page tells you exactly as much as one live request can, and says so.
What we owe you when something is wrong
Response targets are published per edition rather than described as fast, so they are checkable. These are the same figures on the pricing page — one source, so they cannot drift apart.
| Edition | Response target |
|---|---|
| Shop | 1 business day |
| Mobile | 4 business hours |
| Parts & Service | 4 business hours |
| Enterprise | 1 hour + named CSM |
A response target is a commitment to answer, not a commitment to have fixed it. We would rather publish the number we hit than the number that sounds better.
Something wrong that this page does not show?
That is likely, given what it covers. Tell us what you were doing and what happened — a report from someone using the product beats a green tick from a script every time.