ResOlio service status

●All checks passed

Everything we can check is working.

Checked 2026-10-07 20:58:01 UTC, when you loaded this page. Nothing here is cached — reload for a fresh check.

What we checked

• Website

  ●Operational

  This page was built and served by the web app, just now.

• Bookings database

  ●Operational77 ms

  A live read answered normally.

• Guest booking pages

  ●Operational· derived

  The pages your guests book on are served by the website and read the database; both answered.

• Restaurant office

  ●Operational· derived

  The screens your team works on are served by the website and read the database; both answered.

• Email notifications

  ●Operational

  An email provider is switched on. This says confirmations and reminders can be sent — not that a particular message arrived.

Rows marked derived were not checked on their own — they are made of the rows above them, and take the worse of the two. Rows marked recorded are facts we have written down rather than measured just now.

Incidents

No incidents recorded. Nothing has been written here — when something affects your restaurant, we add it by hand and it appears in this list. Nothing is watching the product on your behalf, so usually we find out when you tell us.

For monitors and assistants

GET /service-status/api returns these same checks as JSON, uncached, readable from any origin. Read the top-level status field: anything other than operational means there may be a problem, and unknown means we could not establish that there is not.

These checks are shallow on purpose: they tell you whether our service is answering, not whether a particular booking saved. If this page says everything passed and something is still wrong for you, that is worth telling us — get in touch.