DownForAI

Coze status: API, auth, latency & outage reports

Coze is operational right now. DownForAI checks Coze every ~75 minutes across 1 monitored surface, with 0 community reports in the last 24 hours.

Operational
Last probe 1h ago·1 surface
Probe-monitoredLow confidence
📚 Docs →
100.0%
24h Uptime
903ms
p50 Network Latencyⓘ
1501ms
p95 Network Latencyⓘ
0
Incidents (30d)

DownForAI monitors Coze via a single endpoint — Coze Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 903 ms; p95: 1501 ms.

No incidents have been logged for Coze, and no community reports were received in the last 24 hours. Probes run continuously across the configured surfaces.

Data confidence: LowLast checked 1h 53m ago · 1 monitored surface · 1 with 24 h latency data

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 943ms
Verified 1h ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if Coze is not working for you.

0reports in the last 24 hours

Surface Health

Coze WebOperational
HTTP 200p50 903ms1h ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Coze

No confirmed provider-side issue detected
DownForAI currently sees Coze as operational based on available monitoring signals.
Signal source: public surface check · Monitoring confidence: Low
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

✓No incidents recorded in the past 30 days.

Reported symptoms

No user reports for Coze in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Coze is ByteDance's no-code platform for building AI bots and agents with plugins, workflows and knowledge bases, deployable to Discord, Telegram, Slack and web. The international site (coze.com) and the Chinese one (coze.cn) are separate deployments.

What we monitor
coze.com studio — Bot builder
Published bots and API — Runtime for deployed bots
Channel integrations — Discord / Telegram / Slack connectors
Ecosystem dependencies
Third-party model providersDiscord / Telegram / Slack APIs

Fallback alternatives

What to use if this service is down

Coze is down
Dify, Botpress or Voiceflow (monitored on DownForAI) build comparable bots and agents
Major migration

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Coze statusEmbed this status badgeREADME · docs ▾
Markdown
[![Coze status](https://downforai.com/api/badge/coze.svg)](https://downforai.com/coze)
HTML
<a href="https://downforai.com/coze"><img src="https://downforai.com/api/badge/coze.svg" alt="Coze status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Coze?

Let the community know and help others experiencing the same problem.