DocsBot AI - Notice history

All systems operational

Website - Operational

100% - uptime
Apr 2025 · 99.79%May · 100.0%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

Chatbots - Operational

100% - uptime
Apr 2025 · 99.87%May · 99.90%Jun · 100.0%

Previous page

Next page

Apr 2025
May 2025
Jun 2025

OpenAI → API - Operational

Notice history

Jun 2025

No notices reported this month

May 2025

DDoS Against our Chat APIs
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We implemented blocks and are currently monitoring the result.

  • Investigating
    Investigating
    Our chat API is currently being attacked with a DDoS. We are working on mitigating this traffic. It is causing slow or timeout responses primarily for our Agent API.

Apr 2025

Chat API outage
  • Resolved
    Resolved

    This incident has been resolved. We apologize for the short outage that was due to an incomplete weekend automatic software update. We are putting in place additional automated checks to detect this kind of issue more quickly in the future.

  • Investigating
    Investigating

    We are currently investigating this incident affecting chatting with your bots.

Bot Training DB Errors
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    The reboot seems to have solved the DB issues. A small number of new bots created during the outage may be broken, we are recreating those now.

  • Update
    Update

    Our cloud provider is having trouble finding the root cause, but they are rebooting the DB for now as a temporary fix (this worked last week for the same issue).

  • Identified
    Identified

    The incident seems to have recurred, impacting training sources. We are communicating with our cloud provider.

  • Update
    Update

    Note, if any sources were added or refreshed during the outage, they may be temporarily stuck in a failed or queued state. You can simply click Retry if available, wait a bit for stuck sources to timeout, or simply add the same source again and delete the old one.

  • Resolved
    Resolved

    We triggered a restart and minor update of the DB cluster, and that seems to have fixed the write issues. We are currently monitoring the result, and awaiting a full postmortem from our cloud provider.

  • Investigating
    Investigating

    We have reports and our monitoring is showing problems with our vector database provider when creating or updating sources.

    This may show as timeouts, or strange errors like: class TenantDocument has multi-tenancy enabled, but request was without tenant

    We are currently investigating this incident and are in contact with our cloud provider.

Apr 2025 to Jun 2025

Next