Where does this status come from?

From AssemblyAI's own status page API at https://status.assemblyai.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are AssemblyAI's words.

How can my agent or app check AssemblyAI status?

Fetch https://upbutler.com/status/assemblyai/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"assemblyai"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or AssemblyAI's?

Add "assemblyai" to the dependencies of your UpButler workspace. When one of your monitors fails while AssemblyAI has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is AssemblyAI down?

Right now

No. AssemblyAI is operational.

No incidents reported.

Read from status.assemblyai.com 2 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/assemblyai/status.agent.json

MCP: upstream_status {"service":"assemblyai"}

Speech to text and audio intelligence.

What AssemblyAI reports

Operational

Taken as is from AssemblyAI's own status page API. Incident titles and component names below are theirs.

Open status.assemblyai.com

UpButler's independent probe

There is no keyless endpoint of AssemblyAI that says anything useful, so UpButler does not probe it. To check your own AssemblyAI account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

AssemblyAI components

16 operational

APIs

Asynchronous APIOperational
Streaming APIOperational
LLM GatewayOperational

AWS Cloud

Transcription QueueOperational
Container RegistryOperational
Compute InstancesOperational
Container Control PlaneOperational
Load BalancersOperational
DatabaseOperational
Usage Statistics DatabaseOperational
Object StorageOperational
Usage Statistics BusOperational

Web

WebsiteOperational
PlaygroundOperational
DashboardOperational

BillingOperational

AssemblyAI incidents, last 90 days

5 finished incidents seen since UpButler started tracking on 2026-10-10, 2 of them rated major or critical by AssemblyAI. A typical one lasted 25 min; the longest 1 h 18 min.

Started (UTC)	Incident	Impact	Lasted
2026-10-06 15:44	Increased Processing Times and Errors on EU Endpoint for Universal-3 Pro Async model	minor	19 min
2026-10-06 14:00	Increased Processing Times and Errors on US Endpoint for Universal-3.5 Pro Async model	major	25 min
2026-10-06 10:30	Rejected Sessions on US Endpoint for Universal-3.6 Pro Realtime Model	minor	under a minute
2026-10-05 10:21	Increased processing times and errors for Universal-3.5 Pro on the EU async endpoint	major	1 h 18 min
2026-09-28 17:27	Increased turnaround times for Async Universal-3 model	minor	31 min

Tell your outage from AssemblyAI's

Declare that your project depends on AssemblyAI. When one of your monitors fails while AssemblyAI has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - assemblyai

Ask before you retry

curl -s https://upbutler.com/status/assemblyai/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "assemblyai",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is AssemblyAI down right now?: No. As of 2026-10-10 05:10 UTC, AssemblyAI is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From AssemblyAI's own status page API at https://status.assemblyai.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are AssemblyAI's words.
How can my agent or app check AssemblyAI status?: Fetch https://upbutler.com/status/assemblyai/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"assemblyai"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or AssemblyAI's?: Add "assemblyai" to the dependencies of your UpButler workspace. When one of your monitors fails while AssemblyAI has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in ai models and tooling

UpButler is not affiliated with AssemblyAI. Status and incident text belong to AssemblyAI and are read from their public status source; the probe result is UpButler's own measurement.