Talko AI system status — live engine health and incidents
A live look at the engine behind every automated reply, broadcast and channel.
This page reports one thing, measured directly: whether the background engine that runs every automated action has checked in recently. That engine wakes every five minutes, and records a heartbeat each time it finishes a pass. A pass completed within the last 20 minutes reads as operational; longer than that is delayed; over an hour is down.
It is for customers checking whether a delay is on our side or theirs. If this page says operational but your messages are not sending, the cause is almost always channel-side — an expired Meta token, an unapproved template, or a send outside WhatsApp's 24-hour customer service window. The troubleshooting guide covers those by symptom.
Last updated
Current status
All systems operational
Background engine last ran 17 minutes ago, at Sep 18, 2026, 1:12 AM UTC.
Every automated feature below runs on the same background engine, checked every few minutes — so they share one status rather than being monitored independently. This page checks that engine's own heartbeat directly; it isn't a marketing claim.
What this status covers
These five are jobs run by the same worker, which is why they share a single state rather than reporting independently.
- WhatsApp, Instagram & Messenger message delivery Operational
- AI auto-replies Operational
- YouTube comment automation Operational
- Google Business Profile review replies Operational
- Broadcasts & drip sequences Operational
How to read this page
Operational
- The engine completed a pass within the last 20 minutes. Queued work is being processed on schedule.
Delayed
- The last completed pass was more than 20 minutes but less than an hour ago. Nothing is lost — automated replies, broadcasts and comment responses are running behind and will catch up in order.
Down
- No completed pass for over an hour. Automated work is queuing and not being processed; we treat this as an incident and post one below.
Unknown
- No heartbeat has been recorded at all, so there is nothing to measure yet. This is what a brand-new deployment shows before its first pass.
Incident history
No incidents reported. We post here as soon as something customer-visible breaks.
Questions about platform status
What does this page actually measure?
- One thing, directly: whether the background engine that runs every automated action has checked in recently. That engine wakes on a fixed schedule and records a heartbeat each time it completes a pass, and this page reads that heartbeat. It is a live measurement of our own infrastructure, not a hand-updated status badge.
Why do all the systems share one status?
- Because they share one engine. AI replies, broadcasts, drip sequences, comment automation and review replies are all jobs run by the same background worker. If it is healthy they are all being processed; if it has stalled they all queue together. Reporting them separately would imply independent monitoring that does not exist.
It says operational, but my messages are not sending. What now?
- That points at the channel rather than the platform: an expired or revoked Meta token, a WhatsApp number that has not been subscribed to webhooks, a template still awaiting approval, or a message outside the 24-hour customer service window. The troubleshooting guide is organised by exactly these symptoms.
What does 'delayed' mean for my customers?
- Queued work is running behind, not lost. Automated replies, broadcasts and comment responses are processed in order once the engine catches up, so a delay shows up as slower responses rather than missing ones. Live Chat messages your team sends by hand are unaffected — they go out immediately and do not wait on the engine.
Do you post incidents here?
- Yes. Anything customer-visible gets an entry in the incident history below with what broke, who it affected and how it was resolved. If the page shows a clean history, nothing customer-visible has been recorded — not that nothing has been written down.
Sources
- Meta — WhatsApp Cloud API documentation — message types, templates and the 24-hour customer service window
- Meta — Graph API webhooks — how inbound messages reach the platform
- Google Business Profile Help — review-reply rules for Google listings
Ready to transform your customer conversations?
- Connect a number and go live in under an hour
- Bring your own AI key — predictable, transparent costs