Status and incidents

Service status, maintenance, and incidents

Limowo should give users and partners a clear place to understand marketplace availability, planned maintenance, incidents, and how to report production problems.

Last updated: 1 July 2026

Contact support

Scope

Marketplace, auth, payments, agents

Contact

support@limowo.com

Launch gate

Monitoring, SLAs, incident process

Current status surface

This page is the public status and incident communication surface for Limowo. It is not yet a live automated uptime dashboard, and it should not be used to claim formal availability targets until monitoring and operations coverage are finalized.

Services covered

Status communication should cover the public website, marketplace search and listings, accounts and authentication, messages, media uploads, producer tools, payments and billing, admin operations, public agent/API routes, and future MCP surfaces.

Incident communication

Material incidents should explain affected services, start time, user impact, workaround if available, mitigation status, next update timing, resolution time, and any post-incident follow-up once facts are known.

Planned maintenance

Planned maintenance should be communicated with a Zurich/Switzerland time window, affected surfaces, expected user impact, rollback expectation, and whether users should avoid listings, payments, messages, uploads, or agent/API actions during the window.

Report a service problem

Useful reports include affected URL or endpoint, approximate time with timezone, browser or client, account/listing/message/order/producer/agent request reference, expected behavior, observed behavior, and safe screenshots. Do not send passwords, tokens, full payment data, or sensitive identity documents by email.

Agent and API incidents

Agent/API consumers should include request IDs, command IDs, idempotency keys, grant IDs, endpoint paths, and response codes where available. MCP incidents should remain internal release-gate work until MCP is production-enabled.

Launch-gate operations work

Before Limowo claims production operations maturity, monitoring, alerting, health checks, incident severity levels, on-call ownership, status update cadence, maintenance process, post-incident review, support escalation, and any uptime/SLA wording must be finalized and tested.

Cookie notice

We use cookies for analytics so we can understand how you use limowo.ch. You can accept to help us improve, or reject if you prefer.

Service status, maintenance, and incidents | Limowo