Service status, told honestly.
Solves is at pilot stage, so we do not yet publish an automated real-time status page. We watch the service ourselves while the pilot runs, and we will stand up a public status page before public paid launch. Until then, here is how to reach us if something looks wrong.
No automated uptime widget yet, on purpose. We would rather say so plainly than fake one.
The short answer
Where Solves status stands today
We do not yet publish a live, automated status page or a real-time monitoring widget. Solves is in pilot, and we would rather tell you that than show a green tick that means nothing. We do monitor the service ourselves, and a public status page is one thing we are building before public paid launch.
In the meantime, the reliable way to tell us something is wrong is the contact route. If you think the service is down, slow or behaving oddly, get in touch.
How we monitor the service during the pilot
Behind the scenes we instrument every request, error and timing so problems are visible to us before most users would notice them. Those logs are metadata-only: route families, status codes, durations and a correlation id, never message bodies, email addresses, secrets or payloads. So we can spot a spike in errors or a slow path and investigate without ever reading your customers' email.
Because this watching is internal for now, it is not something you can open in a browser and read. That is why a public status page is on the list: when it is live, you will be able to check the service yourself rather than ask us.
What we commit to
During UK business hours we aim to acknowledge a reported issue promptly and start looking straight away. Outside those hours, a report is picked up the next working morning. When an incident is cleared we will tell you, and where useful we will give a short, plain-English account of what happened. We are not promising a contractual uptime figure during the pilot, because a published uptime SLA is coming rather than in place.
Automated public status is coming
We are building a public status page for before public paid launch. For now there is no live widget to check, so if something looks wrong, please report it through the contact route.
What to expect
How we handle an incident at pilot stage
You tell us
Report a suspected outage through the contact route, with what you were doing and roughly when it started. A correlation id from any error screen speeds things up.
We investigate
We trace the request through metadata-only logs: route, status, timing and correlation id, never your message bodies or customer addresses.
We follow up
We acknowledge promptly during UK business hours, confirm when it is cleared, and where it helps summarise what happened.
Being straight about it
What we are not claiming
We are not showing an uptime percentage, because we will not publish a number we have not earned and measured over time. We are not running a live status widget, because we have not built one yet. And we are not claiming a contractual uptime SLA, because that is coming rather than already agreed.
When the public status page and a published uptime SLA are ready, this page will say so clearly. Until then, the honest position is simple: we watch the service, you can reach us quickly, and we tell you the truth.
FAQ
Status and uptime questions
Does Solves have an uptime SLA?
Not yet. A published uptime service level agreement is coming, but during the pilot we do not commit to a contractual uptime figure. We would rather under-promise here than print a number we cannot stand behind. When we set a formal SLA, before public paid launch, we will publish it here and on the relevant plan.
How do I report a suspected outage?
Use the contact route. Tell us what you were doing, roughly when it started, and whether it affects one brand or everything. A correlation id from any error screen helps us trace it quickly. During UK business hours we aim to acknowledge promptly; outside those hours we pick it up the next working morning.
Where can I see whether the problem is you or me?
For now there is no automated dashboard to check, so the quickest path is to contact us and describe what you are seeing. Our logs are metadata-only, so we can investigate timing and error patterns without reading your message bodies or customer email addresses.
Will you tell me when an incident is resolved?
Yes. If you reported an issue, we will follow up to confirm when it is cleared and, where useful, give a short plain-English summary of what happened. Once the public status page is live, incidents and their updates will appear there too.
When will the public status page be ready?
We are building it as part of getting ready for public paid launch. We will not put a fake date on it here. Until it is live, the contact route is the reliable way to report and track an issue.
Seeing something that looks wrong?
There is no live status widget yet, so the quickest way to flag an outage is to tell us directly.