Platform status

Is Gbooks up?

Every component of the platform was operating normally when this page was published. Operations run on this platform around the clock, so we publish what we see rather than making you ask.

All Systems OperationalAs of 1 August 2026

Components

Web application

Browser access to every industry suite and module

Operational

Core API

The shared data layer every module reads and writes through

Operational

Mobile apps

Admin Plus and Lead Plus on iOS and Android

Operational

Payments

Payment gateway connections and settlement callbacks

Operational

Messaging & notifications

Meta-verified WhatsApp, SMS, email and in-app alerts

Operational

Reporting & analytics

Dashboards, scheduled reports and exports

Operational

Background jobs & integrations

Syncs, imports, webhooks and scheduled automations

Operational

Customer portals

Patient, guest, student and customer self-service portals

Operational

Scheduled maintenance

No maintenance windows are scheduled. When one is planned, it is listed here and emailed to affected customers in advance.

Incident history

No incidents have been reported in the last 90 days. Past incidents stay listed here for 12 months, with the post-incident review linked once it is published.

This page reflects the platform as of 1 August 2026 and is updated when status changes — it is not a live monitor. If you are seeing a problem that is not listed, treat it as unreported and contact support so we can confirm and post an update.

How we operate

Uptime is a habit, not a promise

Availability commitments and any service credits are set out in your agreement. These are the operating practices behind them.

Monitored around the clock

Infrastructure and application health, error rates and authentication anomalies are monitored continuously, with alerts routed to an on-call engineer.

Told before you notice

Planned maintenance is announced in advance to affected customers, and incident updates go out by email and in-product notice as they develop.

Reviewed afterwards

Every material incident gets a written post-incident review with root cause and follow-up actions tracked to completion.

Something not working right now?

Reach our support team directly — real engineers, defined response targets, and a named escalation path if it needs one.