Incident history
Incident history will list factual timestamps, affected components, customer impact and resolution notes after real incidents are confirmed.
Public operational status for the Limvero platform. This page uses a conservative manual format until monitoring, incident history and customer update subscriptions are connected.
No public incident history is shown until real monitoring and incident automation are connected. Maintenance notices and incidents include factual timestamps, affected components and customer impact.
No active public incident is currently posted for the launch environment.
Last checked: 2026-06-14 17:25 Europe/Kiev
Public API, restaurant backend and authentication endpoints.
Dashboard, menu, inventory, customers, reports and settings.
Web terminals, kitchen queue, expo handoff and offline-aware workflows.
Signed event delivery, retries and destination validation.
Webhook delivery, report export, print and tenant lifecycle workers.
PostgreSQL tenant data, indexes, backups and restore readiness.
SSE updates for POS, kitchen and expo screens.
PostgreSQL and Redis backup scripts plus rollback preparation.
Incident history will list factual timestamps, affected components, customer impact and resolution notes after real incidents are confirmed.
Planned maintenance notices will include start time, expected duration, affected modules and rollback/communication expectations.
Until automated subscriptions are connected, restaurants can request operational updates through onboarding or the public contact form. Status updates must include affected modules, timestamps, current impact and the next update expectation.
Request status updates