A
  • Status
  • Events
  • Monitors
Autoresearch
Live status for Autoresearch. GPU nodes and jobs for agents, over MCP.
Investigating · November 14 at 7:15 AM (UTC)

Jobs are waiting in the queue longer than usual because capacity is tight. Queued jobs are safe: they keep their place in line and start as capacity frees up, and a job that cannot run by its deadline expires without being charged for compute it never received.

Web & API
today
MCP server
today
Nodes
today
CPU Nodes
today
Jobs
today
Storage
today
Networks
today
Sandboxes
today
Observability
today
Nov 15, 2026
16 hours ago
Usage reporting is delayed
Resolved · November 15 at 8:54 AM (UTC) (35 minutes)

Usage and billing data has caught up: your usage page is current again, and invoices, receipts, and credits are landing normally. If something you expected from this window is still missing, file a ticket and we will reconcile it.

Investigating · November 15 at 8:19 AM (UTC)

Usage and billing data is updating more slowly than usual. Recent activity may not appear on your usage page yet, and a new invoice, receipt, or credit may take longer than usual to show up. We are working on it now. Your nodes and jobs are not affected and keep running normally, and nothing is lost: the underlying usage, payments, and credits are all on record, and your pages fill in as we clear the backlog.

Nov 14, 2026
2 days ago
Queued jobs are starting slowly
Investigating · November 14 at 7:15 AM (UTC)

Jobs are waiting in the queue longer than usual because capacity is tight. Queued jobs are safe: they keep their place in line and start as capacity frees up, and a job that cannot run by its deadline expires without being charged for compute it never received.

Nov 13, 2026
3 days ago
Some sandbox commands are failing on our side
Resolved · November 13 at 7:16 AM (UTC) (31 minutes)

Sandbox command reliability is back to normal. Voided work was never billed; re-run anything you are missing on a fresh fork.

Investigating · November 13 at 6:45 AM (UTC)

An elevated share of commands running in sandboxes is being cut short by infrastructure failures on our side. Any result marked void was not billed and was excluded from its batch - it is a gap in your data, not a wrong answer - and retrying it on a fresh fork is safe. We are investigating the cause. Nodes and jobs run on separate machines and are not affected.

Nov 13, 2026
3 days ago
Queued jobs are starting slowly
Resolved · November 13 at 7:05 AM (UTC) (2 hours)

The job queue is draining normally again.

Investigating · November 13 at 4:48 AM (UTC)

Jobs are waiting in the queue longer than usual because capacity is tight. Queued jobs are safe: they keep their place in line and start as capacity frees up, and a job that cannot run by its deadline expires without being charged for compute it never received.

Nov 12, 2026
3 days ago
Queued jobs are starting slowly
Resolved · November 12 at 8:40 PM (UTC) (28 minutes)

The job queue is draining normally again.

Investigating · November 12 at 8:12 PM (UTC)

Jobs are waiting in the queue longer than usual because capacity is tight. Queued jobs are safe: they keep their place in line and start as capacity frees up, and a job that cannot run by its deadline expires without being charged for compute it never received.

Nov 12, 2026
4 days ago
Running jobs are being interrupted more than usual
Resolved · November 12 at 1:12 PM (UTC) (12 hours)

Job interruptions are back to normal levels.

Investigating · November 12 at 5:42 AM (UTC)

Some running jobs are being interrupted and returned to the queue more often than we consider acceptable. Interrupted jobs retry automatically - you do not need to resubmit - but affected jobs will take longer to finish than usual.

Resolved · November 12 at 4:57 AM (UTC)

Job interruptions are back to normal levels.

Investigating · November 12 at 1:22 AM (UTC)

Some running jobs are being interrupted and returned to the queue more often than we consider acceptable. Interrupted jobs retry automatically - you do not need to resubmit - but affected jobs will take longer to finish than usual.

Nov 11, 2026
4 days ago
Running jobs are being interrupted more than usual
Resolved · November 11 at 9:18 PM (UTC) (23 minutes)

Job interruptions are back to normal levels.

Investigating · November 11 at 8:55 PM (UTC)

Some running jobs are being interrupted and returned to the queue more often than we consider acceptable. Interrupted jobs retry automatically - you do not need to resubmit - but affected jobs will take longer to finish than usual.

Nov 11, 2026
5 days ago
Some sandbox commands are failing on our side
Resolved · November 11 at 7:18 AM (UTC) (1 hour)

Sandbox command reliability is back to normal. Voided work was never billed; re-run anything you are missing on a fresh fork.

Investigating · November 11 at 6:17 AM (UTC)

An elevated share of commands running in sandboxes is being cut short by infrastructure failures on our side. Any result marked void was not billed and was excluded from its batch - it is a gap in your data, not a wrong answer - and retrying it on a fresh fork is safe. We are investigating the cause. Nodes and jobs run on separate machines and are not affected.

Nov 10, 2026
5 days ago
Command status is slow to update
Resolved · November 10 at 7:09 PM (UTC) (6 minutes)

Command status is up to date again.

Investigating · November 10 at 7:04 PM (UTC)

The status of commands run on nodes is updating more slowly than usual: a command may show as still running after it has actually finished. The commands themselves and their output are not affected.

Nov 10, 2026
5 days ago
Command status is slow to update
Resolved · November 10 at 5:38 PM (UTC) (6 minutes)

Command status is up to date again.

Investigating · November 10 at 5:32 PM (UTC)

The status of commands run on nodes is updating more slowly than usual: a command may show as still running after it has actually finished. The commands themselves and their output are not affected.

Nov 10, 2026
5 days ago
Running jobs are being interrupted more than usual
Resolved · November 10 at 5:17 PM (UTC) (42 minutes)

Job interruptions are back to normal levels.

Investigating · November 10 at 4:35 PM (UTC)

Some running jobs are being interrupted and returned to the queue more often than we consider acceptable. Interrupted jobs retry automatically - you do not need to resubmit - but affected jobs will take longer to finish than usual.

View events history

powered by openstatus.dev

UTC