HoverBot™

System Status

All systems operational

Live availability of HoverBot production services, and the public record of incidents that affected customers.

Last checked 05 Oct 2026, 21:17 UTC

Services

Current service state

Chat API

Serves live conversations for every embedded assistant, including retrieval and human escalation.

Operational772 ms

Widget delivery

Delivers the embed script that loads the assistant on a customer website.

Operational146 ms

Dashboard

The workspace where teams configure assistants, review conversations, and manage users.

Operational757 ms

Configuration API

Backs the dashboard and the public configuration endpoints used during assistant setup.

Operational763 ms

Response times are a single measurement taken from one region at the moment of the check. They indicate reachability, not the speed a given customer experiences.

Incidents

Incident history

MajorResolved

Embedded assistants unable to start conversations

19 Sep 2026, 00:15 UTC · lasted 3 h 10 min · Chat API

Embedded assistants loaded correctly but were unable to generate greetings or respond to messages. The issue was caused by a missing internal service authentication key following a deployment, which prevented the chat service from retrieving bot configuration. All services were restored after the key was provisioned and containers were recreated. No customer data was lost or exposed.

  1. 19 Sep 2026, 03:18 UTC · investigating

    Reports of embedded assistants showing "temporarily unavailable" after loading.

  2. 19 Sep 2026, 03:20 UTC · identified

    Root cause identified: a missing internal API key prevented service-to-service communication.

  3. 19 Sep 2026, 03:25 UTC · resolved

    Key provisioned and both services recreated. Greeting and chat endpoints verified operational.

MajorResolved

Embedded assistants unable to load or respond

17 Sep 2026, 02:30 UTC · lasted 55 min · Configuration API, Chat API

Embedded assistants were unable to load configuration or start conversations for approximately 55 minutes. The issue was caused by a service routing misconfiguration following a deployment. All services were restored and verified. No customer data was lost or exposed.

  1. 17 Sep 2026, 02:45 UTC · investigating

    Widget loading failures reported across all embedded assistants.

  2. 17 Sep 2026, 03:00 UTC · identified

    Root cause traced to a service routing issue. Fix in progress.

  3. 17 Sep 2026, 03:25 UTC · resolved

    All services restored and verified operational.

Methodology

How this page is produced

Service state is measured by an unauthenticated request to each public surface, made from the website infrastructure, which runs separately from the production services it checks. A surface is marked operational when it answers as expected, degraded when it answers unexpectedly, and not reachable when it does not answer within eight seconds.

These checks confirm that a service is responding. They do not assert that every dependency behind it is healthy, and no uptime percentage is derived from them, because a point-in-time check cannot support one. Inside the production environment, container health checks and deployment health gates run on every release. Any incident that affects customers is published below, whichever check surfaced it.

Incidents are written by the HoverBot team and kept in version control, so each entry carries an author, a timestamp, and a reviewable change history. Updates are appended rather than rewritten. The same data is available as JSON at /api/status.

HoverBot targets a 99.9% monthly availability objective for production services. Enterprise SLA terms are available through contractual agreements. For security controls, retention, and compliance progress, see the Trust Center.

To report a problem you are seeing that is not listed here, email hi@hoverbot.ai or use the contact form.