App
Web application at console.lepsto.com
Lepsto Status
Components
API
Public API gateway
Auth
Sign-in and token issuance
MCP
Model Context Protocol endpoint
Billing
Metering and invoicing
Toolkits
11/11 operational
App (lessly.com)
Legacy app.lessly.com redirect to the console
API (lessly.com)
Legacy API gateway at api.lessly.com
Auth (lessly.com)
Legacy sign-in and token issuance at auth.lessly.com
MCP (lessly.com)
Legacy Model Context Protocol endpoint at mcp.lessly.com
Past incidents
No incidents recorded.
Past maintenance
lepsto.com domain cutover
We moved the platform to lepsto.com. The web application is now served at console.lepsto.com, and the API, Auth and MCP hosts moved alongside it. The old lessly.com addresses answer redirects, so bookmarks, saved links and configured endpoints keep working.
Impact
Sign-in sessions on app.lessly.com were interrupted for the length of the window and had to be re-established on console.lepsto.com. This record names App alone because App is the only row that recorded a failure: over the same 30 days API and MCP each logged a single unrelated failed probe and Auth none at all. We do not file an interruption we did not observe.
The red bar on the App row runs well past the window. After the move the probe went on asking app.lessly.com for a 200 and read the redirect it now answers as a failure, until the probe was pointed at the new address at about 23:40 UTC. The application was serving that whole time. We are leaving the bar alone: it records what we measured, and the measurement was wrong, not the service.
This status page itself moved at the same time: it is served at status.lepsto.com, and status.lessly.com now answers a permanent redirect to it, path and query intact.