Performance-issues with AI-matching causing messaging delivery issues and increased fallback rates
Performance is stable and the incident is resolved.
Home
/
Status
/
Service
AI chatbot platform for enterprise communication.
Source
auto
Category
AI
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 17m ago
20
Components
0
Active incidents
0
Maintenance
16.67%
90d uptime
Performance-issues with AI-matching causing messaging delivery issues and increased fallback rates
Jun 11, 3:25 PM
Normalized official status-page data for incidents, maintenance, components, and history.
16.67%
Known uptime
6 known history days
20
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
17
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Analytics dashboard
Operational
Application API
Operational
Bot message delivery
Operational
Chat log API
Operational
Data capture ingest
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
1
operational days
0
degraded days
4
outage days
1
maintenance days
84
unknown days
Latest outages and degradations detected from the official status page.
Performance is stable and the incident is resolved.
Performance are restored and stable.
This incident has been resolved.
This incident has been resolved.
The incident have been resolved. Platform is back up and stable. There will be an internal post-mortem incident report.
On Sunday March 8, some analytics data in Kindly was not updating as expected. This meant dashboards and reporting could show older information than normal during that period. This issue did **not** affect chatbot availability or customer conversations, and no data was lost. Once identified, we restored the sync and updated the delayed analytics data. All systems are now operating normally.
Incident resolved
This incident has been resolved.
This incident has been resolved.
The issue was resolved by the vendor at 21:40 6th of January
Scheduled and completed maintenance windows are separated from incidents.
Database maintenance preparing for Markets is complete. All delayed analytics dashboards and events looks fully synced, and systems are operating normally. No data was lost. Thank you for your patience.
Scheduled maintenance is completed and all statistics tables are fully re-synced. Thank you for the patience.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The domain switch is now complete and you can now reach us at support@kindly.ai (or even at support@convertelligence.no for a while longer)
The scheduled maintenance has been completed.
Uptimus tracks the official Kindly status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.kindly.ai
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 20 of 20 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Platform | Operational | Group | Not recorded |
Messaging channels and integrations | Operational | Group | Not recorded |
Public APIs | Operational | Group | Not recorded |
Onsite and data capture | Operational | Group | Not recorded |
Analytics dashboard Dashboards inside the platform for viewing metrics | Operational | Component | Not recorded |
Bot message delivery General status of bot responsiveness | Operational | Component | Not recorded |
Facebook Messenger integration Bot messaging channel on Facebook Messenger | Operational | Component | Not recorded |
KPI dashboard | Operational | Component | Not recorded |
Statistics API Status for statistics service API | Operational | Component | Not recorded |
Email services | Operational | Component | Not recorded |
Handover to human chat | Operational | Component | Not recorded |
Platform app Status of the bot building platform, including Inbox and Build | Operational | Component | Not recorded |
Plugin integrations Build plugin integration status | Operational | Component | Not recorded |
Application API API for sending and receiving messages | Operational | Component | Not recorded |
Chat log API API for retrieving chat logs | Operational | Component | Not recorded |
Data capture ingest | Operational | Component | Not recorded |
Kindly Chat messaging client Status of the Kindly Chat chat client for web and loading of kindly-chat.js from CDN. | Operational | Component | Not recorded |
Handover API | Operational | Component | Not recorded |
Spinnaker Data capture and onsight JS | Operational | Component | Not recorded |
Dialogue webhooks Dialogue webhook delivery | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Kindly is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.