Minds / Service status
Current public checks, with the details behind each result. For your dedicated Mind, the workspace remains the place to inspect its own health.
Public service checks
Four observations. A clearly defined scope.
Checks refresh every minute while this page is visible.
Public website delivery
The public endpoint responded successfully from this observation point.
Duration includes this server’s network request. It is not a product latency benchmark.
Sign-in page delivery; does not test authentication
The public endpoint responded successfully from this observation point.
Duration includes this server’s network request. It is not a product latency benchmark.
Web application process liveness; does not test its dependencies
The web application reported its process as live. Account services and instances are outside this check.
Duration includes this server’s network request. It is not a product latency benchmark.
Public documentation delivery
The public endpoint responded successfully from this observation point.
Duration includes this server’s network request. It is not a product latency benchmark.
Public page delivery is one part of the service. These account-specific functions are not measured by this page.
Account-specific
Compute, memory services, storage, startup, and readiness are specific to each Akasha instance. Check the selected instance in your workspace; a green website check does not certify its health.
Account-specific
Conversations depend on your session, instance context, model provider, and tools. The public application check does not complete a chat or make a model request.
Account-specific
These checks do not sign into an account, provision a Mind, perform an upgrade, or process a payment. Use the workspace for the status of your own operation.
Results are observations from the Minds website server. They are not a global outage declaration or a contractual service-level report.
Each check has its own UTC timestamp and a six-second deadline. Results are cached for up to a minute. A failed check may reflect the observation point’s network or DNS.
A verified historical incident feed is not connected to this page. It does not publish an uptime percentage or imply an incident-free history. Contact support for information about a particular event.
The same bounded public snapshot is available as JSON. It contains no account identifiers or private instance health.
Open status JSON ↗Send support@minds.sh the affected feature, UTC time, request or instance reference, and the visible error. Include the steps that reproduce it. Keep passwords, API keys, and private customer content out of the report.
For a suspected vulnerability, use security@minds.sh. Review the Trust center ↗