Skip to main content

​
Platform Status

Real-time status for all Bothive platform services.

For live, real-time status updates, visit status.bothive.cloud. This page shows our current service status snapshot.

​
Current status

​
Status legend

​
Incident history

Duration: 47 minutes (14:02 – 14:49 UTC) Impact: Telegram message delivery was delayed by 15–90 seconds for approximately 12% of bots. Root cause: Telegram’s infrastructure experienced a partial outage affecting webhook delivery in EU regions. Resolution: Our retry queue compensated for missed deliveries. All messages delivered. No data loss. Follow-up: Added a second webhook endpoint in a different region as a fallback.
Duration: 22 minutes (09:17 – 09:39 UTC) Impact: Tool call latency increased from ~300ms to ~2.1s for all integrations. Root cause: A memory leak in the integration gateway process caused gradual slowdown over 6 hours until auto-restart triggered. Resolution: Service auto-restarted. Latency returned to normal immediately. Follow-up: Added memory usage alerting with auto-restart at 85% threshold.
Duration: 35 minutes (03:00 – 03:35 UTC) Impact: Brief API unavailability during database migration. Bots running scheduled tasks were paused and resumed automatically post-maintenance. Type: Planned maintenance — announced 72 hours in advance. Outcome: Successful zero-data-loss migration. No rollback required.

​
Uptime SLAs

​
Subscribe to status updates

Get notified when incidents occur or maintenance is scheduled:

Email Alerts

Subscribe to status.bothive.cloud to get email notifications for incidents and maintenance windows.

RSS Feed

Subscribe to our RSS feed and get updates in your preferred RSS reader.

​
Report an issue

If you’re experiencing an issue not reflected here:
  1. Check status.bothive.cloud for the latest real-time data
  2. Search the Discord community — others may be experiencing the same thing
  3. Email support@bothive.cloud with your bot ID, run ID, and a description of the issue