ChatBot logo

Is ChatBot Down?

SaaSLive status, outages, and incident history

No. ChatBot is up right now.

Every monitored ChatBot system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 6m agoLive · 60s while moving1 active incident

Know the moment ChatBot breaks

ChatBot is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official ChatBot status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

ChatBot Component Status

The main ChatBot systems on this page. All 5 are operational right now.

5operational
API
Operational
Chat widget
Operational
Integrations
Operational

2 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Support chat on www.chatbot.com, Web Application.

See all of them free

Component statuses may change independently during partial outages.

Recent ChatBot Outages & Incidents

Incident history from the official ChatBot status page, including resolution updates.

Scheduled maintenanceScheduled for Sep 25, 2026Scheduled

We will be performing platform maintenance affecting both the US and EU data centers on September 30th from 2:30 AM to 2:40 AM (ETD). During this ten-minute maintenance window, some agents may experience brief errors. The overall impact should take less than one minute. No customer action is required. We will provide updates as necessary.

ChatBot Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a ChatBot incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 2 days with incidentsSep 25

Live ChatBot Outage Reports

Problems reported by engineers using ChatBot. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No ChatBot problems reported yet.

Something wrong with ChatBot on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About ChatBot

ChatBot publishes a public status page at status.chatbot.com covering 5 components, including API, Support chat on www.chatbot.com and Chat widget. PulsAPI tracks ChatBot outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured ChatBot uptime at 100.00%. Response times, incident history, and SLA tracking for ChatBot are available on the PulsAPI dashboard.

ChatBot Status FAQ

Is ChatBot down right now?

The verdict at the top of this page comes from the latest poll of the official ChatBot status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if ChatBot is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until ChatBot recovers.

How do I check ChatBot uptime history?

PulsAPI tracks ChatBot uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever ChatBot changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect ChatBot outages?

PulsAPI reads the official ChatBot status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual ChatBot components?

Yes. PulsAPI monitors 5 individual ChatBot components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when ChatBot goes down?

Yes. Create a free account and subscribe to ChatBot: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with ChatBot to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot ChatBot problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor ChatBot?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so ChatBot plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track ChatBot with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services