Data ingestion completed.

Data ingestion is still in progress. We continue to monitor the backfill and will notify once it has fully completed.

We are currently experiencing a delay in analytics and reporting data. The last successful sync completed at 5:39 PM on July 20. Our team has identified and applied a fix — data ingestion is now actively in progress. Full data backfill is expected to complete within the next couple of hours. We will provide an update once everything is caught up.

Resolved: Scheduled maintenance on our analytics data pipeline is complete. All analytics dashboards and reporting have been fully rebuilt and are now current.

Live call handling, ordering, and all customer-facing voice services were unaffected throughout. Thank you for your patience.

Update: Our analytics data pipeline maintenance is taking longer than initially estimated. The dashboard rebuild is currently queued behind other routine pipeline operations on the same data source and will proceed automatically once those complete.

Live call handling, ordering, and all customer-facing voice services remain fully unaffected. This continues to be limited to internal reporting and analytics dashboards, which may be temporarily unavailable or display stale data during this window.

We now expect analytics reporting to be fully restored within approximately the next hour. No action is needed; dashboards will refresh automatically once the rebuild finishes. We will post a final update when maintenance is complete, and we apologize for the extended window.

We are currently performing scheduled maintenance on our analytics data pipeline. During this window, analytics dashboards and related reporting may be temporarily unavailable or display stale data.

Live call handling, ordering, and all customer-facing voice services are fully unaffected. This is limited to internal reporting and analytics only.

We expect the rebuild to complete within approximately 30–60 minutes (note: this is an estimate, as it involves a full scan of a large data source). No action is needed — dashboards will refresh automatically once the rebuild finishes. We will post an update when the maintenance is complete.

The ordering issue has been resolved. Callers are now able to place orders normally.

A fix has been applied for the ordering issue that prevented callers from placing orders. We are actively monitoring performance to confirm the issue is fully resolved and that ordering is functioning normally again.

Ordering is currently experiencing degraded performance, and callers are temporarily unable to place orders. We identified the issue and we are working on a fix.

This issue has been resolved. Reporting displays in the Kea Portal are back to normal — all order data has been resynced and is now populated correctly. No data was lost at any point. Thank you for your patience!

We have identified an issue affecting reporting displays in the Kea Portal. Some order data may appear incomplete or missing within reports. No data has been lost, and this does not affect calls or any core systems. Our team is actively working on a fix — once deployed, data will be resynced and populated correctly.

Between 23:35 and 23:45 UTC on June 9, phone call requests failed due to a database migration conflict during a deployment. A migration operation queued behind a long-running query, causing an exclusive lock that blocked all queries on the calls table for approximately 10 minutes.

The migration was stopped and rolled back cleanly with no data loss. Production remained on the previous image and is now fully operational.

We've implemented a lock timeout safeguard to prevent similar stalls in future deployments.

This incident has been resolved. Incoming phone calls are no longer being forwarded to stores and are connecting to the AI assistant normally again. Service has been restored.

We have identified the root cause as an outage affecting our third-party phone service provider. We are in direct contact with them and working to resolve the issue as soon as possible. We will continue to provide updates as the situation progresses.

We are currently investigating an issue affecting incoming phone calls. Calls are being forwarded to stores, but they are not connecting to the AI assistant at this time. Our team is working to restore normal service and will share updates as we learn more.

The service degradation has been resolved. The issue was caused by an upstream provider incident, which also impacted our primary fallback path and temporarily reduced the effectiveness of our redundancy plan. Our team monitored the incident closely and confirmed that service has returned to normal. We have also prepared an improvement plan to add an additional fallback layer, reducing the potential impact if a similar provider issue occurs again.

We are currently investigating an issue affecting incoming phone calls. Calls are being forwarded to stores, but they are not connecting to the AI assistant at this time. Our team is working to restore normal service and will share updates as we learn more.

The issue affecting incoming phone calls has been resolved. Incoming calls are now connecting to the AI assistant normally again. We will continue monitoring to ensure stability.

We are currently investigating an issue affecting incoming phone calls. Calls are being forwarded to stores, but they are not connecting to the AI assistant at this time. Our team is working to restore normal service and will share updates as we learn more.

The issue has been fully resolved. Our telephony provider's fix has been successful and all phone calls are now reaching our AI system normally. All services are operating as expected.

Our telephony provider has identified and rolled back the problematic deployment. They are seeing recovery in their systems. We are disabling automatic call forwarding to stores and monitoring to ensure calls are reaching our AI system normally.

We have identified the root cause as a degraded third-party telephony service. Our team is in contact with the service provider to resolve the issue. Calls continue to be forwarded to stores as a temporary workaround.

We are currently investigating an issue where phone calls are not reaching our AI system. As a temporary measure, calls are being forwarded directly to stores. Our team is actively working to identify the root cause and restore normal service.

This incident has been resolved. The issue was caused by WebSocket connection timeouts between two of our external telephony providers, which prevented proper communication. Service has been fully restored and all systems are operating normally.

We are observing signs of recovery. However, we continue to monitor intermittent WebSocket connection timeouts occurring between two of our providers that are affecting some calls.

We have disabled the automatic forwarding to stores and are now allowing calls to attempt connection with the AI assistant. Our team is actively monitoring the situation to ensure service stability.

We are continuing to investigate the issue with our external provider. All incoming calls are being forwarded normally to stores, but the AI assistant is currently not responsive. We are working to restore full functionality.

We are currently investigating degraded performance affecting Kea Voice AI and Kea Phone Calls due to issues with external providers. Our team is actively working to restore full service. Updates will be provided as we learn more.