A
  • Status
  • Events
  • Monitors
Autoresearch
Live status for Autoresearch. GPU nodes and jobs for agents, over MCP.
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.

Nov 5, 2026
10 days ago
Some sandbox commands are failing on our side
Resolved · November 6 at 12:25 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 5 at 11:21 PM (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 5, 2026
10 days ago
Some sandbox commands are failing on our side
Resolved · November 5 at 5:07 PM (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 5 at 4:05 PM (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 4, 2026
11 days ago
Usage reporting is delayed
Resolved · November 4 at 11:15 PM (UTC) (1 hour)

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 4 at 11:06 PM (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.

Resolved · November 4 at 10:09 PM (UTC)

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 4 at 10:02 PM (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 2, 2026
13 days ago
Queued jobs are starting slowly
Resolved · November 4 at 12:21 AM (UTC) (1 day)

The job queue is draining normally again.

Investigating · November 2 at 1:46 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 3, 2026
13 days ago
Running jobs are being interrupted more than usual
Resolved · November 3 at 8:56 AM (UTC) (3 hours)

Job interruptions are back to normal levels.

Investigating · November 3 at 6:03 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 2, 2026
13 days ago
Running jobs are being interrupted more than usual
Resolved · November 2 at 7:21 PM (UTC) (10 minutes)

Job interruptions are back to normal levels.

Investigating · November 2 at 7:12 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 2, 2026
13 days ago
Some sandbox commands are failing on our side
Resolved · November 2 at 2:42 PM (UTC) (28 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 2 at 2:14 PM (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 1, 2026
14 days ago
Some sandbox commands are failing on our side
Resolved · November 1 at 2:46 PM (UTC) (37 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 1 at 2:09 PM (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 1, 2026
15 days ago
Running jobs are being interrupted more than usual
Resolved · November 1 at 1:24 PM (UTC) (1 hour)

Job interruptions are back to normal levels.

Investigating · November 1 at 12:09 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 1, 2026
15 days ago
Usage reporting is delayed
Resolved · November 1 at 8:04 AM (UTC) (23 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 1 at 7:42 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.

Oct 31, 2026
15 days ago
Command status is slow to update
Resolved · October 31 at 11:53 PM (UTC) (1 hour)

Command status is up to date again.

Investigating · October 31 at 11:48 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.

Resolved · October 31 at 10:48 PM (UTC)

Command status is up to date again.

Investigating · October 31 at 10:42 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.

Oct 31, 2026
16 days ago
Running jobs are being interrupted more than usual
Resolved · October 31 at 9:44 PM (UTC) (19 hours)

Job interruptions are back to normal levels.

Investigating · October 31 at 4:39 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 · October 31 at 3:53 AM (UTC)

Job interruptions are back to normal levels.

Investigating · October 31 at 2:39 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.

Oct 30, 2026
16 days ago
Queued jobs are starting slowly
Resolved · October 31 at 5:45 PM (UTC) (22 hours)

The job queue is draining normally again.

Investigating · October 30 at 7:55 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.

Oct 31, 2026
15 days ago
Some sandbox commands are failing on our side
Resolved · October 31 at 2:41 PM (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 · October 31 at 1:40 PM (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.

Oct 31, 2026
16 days ago
Command status is slow to update
Resolved · October 31 at 7:38 AM (UTC) (6 minutes)

Command status is up to date again.

Investigating · October 31 at 7:33 AM (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.

Oct 30, 2026
16 days ago
Some sandbox commands are failing on our side
Resolved · October 30 at 7:31 PM (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 · October 30 at 7:00 PM (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.

Oct 30, 2026
16 days ago
Some sandbox commands are failing on our side
Resolved · October 30 at 3:32 PM (UTC) (2 hours)

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

Investigating · October 30 at 1:08 PM (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.

Oct 30, 2026
17 days ago
Our CPU node check is failing
Resolved · October 30 at 7:21 AM (UTC) (7 minutes)

Our CPU node check is passing again: CPU nodes create, stop, and wake normally with their files intact.

Investigating · October 30 at 7:14 AM (UTC)

Our continuous check of CPU nodes - creating a real cpu-2 node, stopping it, and waking it with its files intact - is failing, and we are investigating what it caught. Creating a new CPU node, or waking a stopped one, may be delayed or may fail while this is open. GPU nodes run on separate machines and are not affected, running CPU nodes keep running, and stopped CPU nodes' files remain safe in durable storage. If a create or wake fails, nothing is lost or charged: it is safe to try again once this is resolved.

Oct 30, 2026
17 days ago
Some sandbox commands are failing on our side
Resolved · October 30 at 4:02 AM (UTC) (10 minutes)

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

Investigating · October 30 at 3:52 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.

Oct 26, 2026
20 days ago
Our large-upload and long-build check is failing
Resolved · October 30 at 2:55 AM (UTC) (4 days)

Our large-upload and long-build check is passing again: multi-part uploads finalize and long image builds complete normally.

Investigating · October 26 at 12:46 PM (UTC)

Our continuous check of the large-input path - uploading a multi-part input and building an image whose build runs for many minutes - is failing, and we are investigating what it caught. Small jobs and already-running workloads are not affected. While this is open, uploading a large input may fail partway or need to be retried, and a long image build may fail near the end. Nothing is lost either way: uploaded parts stay put and can be finalized again, and a job whose build fails is not charged for compute it never received.

Oct 26, 2026
20 days ago
Our CPU node check is failing
Resolved · October 30 at 2:08 AM (UTC) (3 days)

Our CPU node check is passing again: CPU nodes create, stop, and wake normally with their files intact.

Investigating · October 26 at 3:20 PM (UTC)

Our continuous check of CPU nodes - creating a real cpu-2 node, stopping it, and waking it with its files intact - is failing, and we are investigating what it caught. Creating a new CPU node, or waking a stopped one, may be delayed or may fail while this is open. GPU nodes run on separate machines and are not affected, running CPU nodes keep running, and stopped CPU nodes' files remain safe in durable storage. If a create or wake fails, nothing is lost or charged: it is safe to try again once this is resolved.

Oct 26, 2026
21 days ago
Our stopped-node wake check is failing
Resolved · October 30 at 2:03 AM (UTC) (4 days)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 26 at 11:04 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 26, 2026
20 days ago
Our end-to-end job check is failing
Resolved · October 30 at 1:52 AM (UTC) (4 days)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · October 26 at 12:48 PM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Oct 29, 2026
17 days ago
Some sandbox commands are failing on our side
Resolved · October 29 at 8:04 PM (UTC) (59 minutes)

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

Investigating · October 29 at 7:04 PM (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.

Oct 29, 2026
17 days ago
Some sandbox commands are failing on our side
Resolved · October 29 at 2:45 PM (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 · October 29 at 2:18 PM (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.

Resolved · October 29 at 2:13 PM (UTC)

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

Investigating · October 29 at 1:35 PM (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.

Oct 28, 2026
18 days ago
Some sandbox commands are failing on our side
Resolved · October 28 at 3:24 PM (UTC) (2 hours)

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

Investigating · October 28 at 1:09 PM (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.

Oct 26, 2026
20 days ago
Some sandbox commands are failing on our side
Resolved · October 26 at 4:03 PM (UTC) (2 hours)

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

Investigating · October 26 at 3:02 PM (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.

Resolved · October 26 at 2:52 PM (UTC)

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

Investigating · October 26 at 1:52 PM (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.

Oct 25, 2026
21 days ago
Some sandbox commands are failing on our side
Resolved · October 25 at 3:15 PM (UTC) (2 hours)

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

Investigating · October 25 at 1:35 PM (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.

Oct 23, 2026
23 days ago
Running jobs are being interrupted more than usual
Resolved · October 25 at 1:39 AM (UTC) (1 day)

Job interruptions are back to normal levels.

Investigating · October 23 at 6:25 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.

Oct 24, 2026
22 days ago
Some sandbox commands are failing on our side
Resolved · October 24 at 3:13 PM (UTC) (2 hours)

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

Investigating · October 24 at 1:10 PM (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.

Oct 24, 2026
23 days ago
New nodes are slow to become ready
Resolved · October 24 at 10:02 AM (UTC) (11 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · October 24 at 9:51 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Oct 24, 2026
23 days ago
Some sandbox commands are failing on our side
Resolved · October 24 at 10:00 AM (UTC) (3 hours)

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

Investigating · October 24 at 8:58 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.

Resolved · October 24 at 7:57 AM (UTC)

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

Investigating · October 24 at 7:23 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.

Oct 23, 2026
23 days ago
Some sandbox commands are failing on our side
Resolved · October 23 at 3:14 PM (UTC) (2 hours)

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

Investigating · October 23 at 1:07 PM (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.

Oct 23, 2026
24 days ago
Running jobs are being interrupted more than usual
Resolved · October 23 at 2:07 PM (UTC) (8 hours)

Job interruptions are back to normal levels.

Investigating · October 23 at 5:59 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.

Oct 23, 2026
24 days ago
Command status is slow to update
Resolved · October 23 at 12:12 AM (UTC) (5 minutes)

Command status is up to date again.

Investigating · October 23 at 12:07 AM (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.

Oct 22, 2026
25 days ago
Running jobs are being interrupted more than usual
Resolved · October 22 at 11:19 PM (UTC) (18 hours)

Job interruptions are back to normal levels.

Investigating · October 22 at 5:01 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.

Oct 22, 2026
24 days ago
Some sandbox commands are failing on our side
Resolved · October 22 at 3:17 PM (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 · October 22 at 1:54 PM (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.

Oct 21, 2026
25 days ago
The website is having problems
Resolved · October 21 at 7:10 PM (UTC) (8 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 21 at 7:02 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Oct 21, 2026
25 days ago
The website is having problems
Resolved · October 21 at 5:39 PM (UTC) (36 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 21 at 5:33 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Resolved · October 21 at 5:12 PM (UTC)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 21 at 5:03 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Oct 21, 2026
25 days ago
Some sandbox commands are failing on our side
Resolved · October 21 at 5:29 PM (UTC) (54 minutes)

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

Investigating · October 21 at 4:35 PM (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.

Oct 20, 2026
27 days ago
Our stopped-node wake check is failing
Resolved · October 20 at 8:55 AM (UTC) (2 hours)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 20 at 6:32 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 18, 2026
28 days ago
Our stopped-node wake check is failing
Resolved · October 18 at 11:59 PM (UTC) (1 hour)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 18 at 10:39 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 18, 2026
28 days ago
Some running nodes were interrupted
Resolved · October 18 at 9:51 PM (UTC) (7 minutes)

All affected nodes have been recovered, and interruption credits were applied automatically.

Investigating · October 18 at 9:44 PM (UTC)

A capacity provider issue interrupted some running nodes. We are recovering the affected nodes now. If one of your nodes was interrupted, the interrupted time is credited to your account automatically - you do not need to file anything.

Oct 17, 2026
30 days ago
New nodes are slow to become ready
Resolved · October 17 at 8:13 AM (UTC) (3 hours)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · October 17 at 8:08 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · October 17 at 7:36 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · October 17 at 7:25 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · October 17 at 6:43 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · October 17 at 6:13 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · October 17 at 5:11 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · October 17 at 5:00 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Oct 17, 2026
30 days ago
Our CPU node check is failing
Resolved · October 17 at 6:45 AM (UTC) (35 minutes)

Our CPU node check is passing again: CPU nodes create, stop, and wake normally with their files intact.

Investigating · October 17 at 6:10 AM (UTC)

Our continuous check of CPU nodes - creating a real cpu-2 node, stopping it, and waking it with its files intact - is failing, and we are investigating what it caught. Creating a new CPU node, or waking a stopped one, may be delayed or may fail while this is open. GPU nodes run on separate machines and are not affected, running CPU nodes keep running, and stopped CPU nodes' files remain safe in durable storage. If a create or wake fails, nothing is lost or charged: it is safe to try again once this is resolved.

Oct 17, 2026
30 days ago
Some running nodes were interrupted
Resolved · October 17 at 5:37 AM (UTC) (7 minutes)

All affected nodes have been recovered, and interruption credits were applied automatically.

Investigating · October 17 at 5:30 AM (UTC)

A capacity provider issue interrupted some running nodes. We are recovering the affected nodes now. If one of your nodes was interrupted, the interrupted time is credited to your account automatically - you do not need to file anything.

Oct 16, 2026
1 month ago
The website is having problems
Resolved · October 16 at 10:52 AM (UTC) (30 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 16 at 10:41 AM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Resolved · October 16 at 10:31 AM (UTC)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 16 at 10:22 AM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Oct 16, 2026
1 month ago
The website is having problems
Resolved · October 16 at 8:25 AM (UTC) (14 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 16 at 8:11 AM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Oct 16, 2026
1 month ago
Our stopped-node wake check is failing
Resolved · October 16 at 7:15 AM (UTC) (34 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 16 at 6:41 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 16, 2026
1 month ago
The website is having problems
Resolved · October 16 at 4:04 AM (UTC) (10 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 16 at 3:54 AM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Oct 12, 2026
1 month ago
Usage reporting is delayed
Resolved · October 12 at 4:58 PM (UTC) (2 hours)

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 · October 12 at 2:58 PM (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.

Oct 11, 2026
1 month ago
Usage reporting is delayed
Resolved · October 11 at 6:03 PM (UTC) (2 hours)

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 · October 11 at 4:00 PM (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.

Oct 11, 2026
1 month ago
Our CPU node check is failing
Resolved · October 11 at 9:06 AM (UTC) (7 minutes)

Our CPU node check is passing again: CPU nodes create, stop, and wake normally with their files intact.

Investigating · October 11 at 8:59 AM (UTC)

Our continuous check of CPU nodes - creating a real cpu-2 node, stopping it, and waking it with its files intact - is failing, and we are investigating what it caught. Creating a new CPU node, or waking a stopped one, may be delayed or may fail while this is open. GPU nodes run on separate machines and are not affected, running CPU nodes keep running, and stopped CPU nodes' files remain safe in durable storage. If a create or wake fails, nothing is lost or charged: it is safe to try again once this is resolved.

Oct 9, 2026
1 month ago
Running jobs are being interrupted more than usual
Resolved · October 9 at 2:38 PM (UTC) (7 hours)

Job interruptions are back to normal levels.

Investigating · October 9 at 7:47 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.

Oct 9, 2026
1 month ago
Queued jobs are starting slowly
Resolved · October 9 at 6:58 AM (UTC) (5 minutes)

The job queue is draining normally again.

Investigating · October 9 at 6:53 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.

Oct 9, 2026
1 month ago
The website is having problems
Resolved · October 9 at 4:25 AM (UTC) (7 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · October 9 at 4:18 AM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Oct 8, 2026
1 month ago
Some running nodes were interrupted
Resolved · October 8 at 7:10 PM (UTC) (8 minutes)

All affected nodes have been recovered, and interruption credits were applied automatically.

Investigating · October 8 at 7:02 PM (UTC)

A capacity provider issue interrupted some running nodes. We are recovering the affected nodes now. If one of your nodes was interrupted, the interrupted time is credited to your account automatically - you do not need to file anything.

Oct 8, 2026
1 month ago
Usage reporting is delayed
Resolved · October 8 at 7:32 AM (UTC) (14 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 · October 8 at 7:18 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.

Oct 6, 2026
1 month ago
Queued jobs are starting slowly
Resolved · October 7 at 6:09 AM (UTC) (6 hours)

The job queue is draining normally again.

Investigating · October 6 at 11:53 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.

Oct 5, 2026
1 month ago
Our stopped-node wake check is failing
Resolved · October 5 at 8:00 PM (UTC) (15 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 5 at 7:45 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 5, 2026
1 month ago
Our stopped-node wake check is failing
Resolved · October 5 at 1:10 PM (UTC) (9 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 5 at 1:01 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 5, 2026
1 month ago
Running jobs are being interrupted more than usual
Resolved · October 5 at 8:06 AM (UTC) (1 hour)

Job interruptions are back to normal levels.

Investigating · October 5 at 6:44 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.

Oct 4, 2026
1 month ago
Queued jobs are starting slowly
Resolved · October 4 at 7:26 PM (UTC) (5 hours)

The job queue is draining normally again.

Investigating · October 4 at 2:04 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.

Oct 4, 2026
1 month ago
Our stopped-node wake check is failing
Resolved · October 4 at 12:36 AM (UTC) (8 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · October 4 at 12:28 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Oct 2, 2026
1 month ago
Running jobs are being interrupted more than usual
Resolved · October 2 at 3:13 PM (UTC) (1 hour)

Job interruptions are back to normal levels.

Investigating · October 2 at 1:56 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.

Oct 1, 2026
2 months ago
Some sandbox commands are failing on our side
Resolved · October 1 at 9:48 PM (UTC) (27 minutes)

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

Investigating · October 1 at 9:21 PM (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.

Sep 30, 2026
2 months ago
Some nodes lost access to a GPU
Resolved · September 30 at 10:45 PM (UTC) (8 hours)

The affected hosts have been repaired or replaced, and GPU availability is back to normal.

Investigating · September 30 at 2:50 PM (UTC)

A GPU on a small number of hosts has become unavailable, so a node or job running there may see CUDA errors or fewer GPUs than expected. We are repairing or replacing the affected hosts. If your workload is on one, checkpoint what you can and recreate the node - new nodes land on healthy hosts.

Sep 29, 2026
2 months ago
Some submitted jobs are failing
Resolved · September 29 at 5:39 PM (UTC) (2 hours)

Job submissions are working normally again. If one of your jobs failed during this incident, it is safe to resubmit it now.

Investigating · September 29 at 3:39 PM (UTC)

Some jobs are failing during image preparation because of an internal issue on our side - not because of anything in the job itself. We are investigating. Jobs that are already running are not affected. If a job of yours failed with an image-related error, it is safe to resubmit it once this is resolved.

Aug 27, 2026
3 months ago
Some sandbox commands are failing on our side
Resolved · August 27 at 5:04 PM (UTC) (14 minutes)

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

Investigating · August 27 at 4:50 PM (UTC)

An elevated share of commands running in rollout 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.

Aug 26, 2026
3 months ago
Some running nodes were interrupted
Resolved · August 26 at 11:00 PM (UTC) (7 minutes)

All affected nodes have been recovered, and interruption credits were applied automatically.

Investigating · August 26 at 10:53 PM (UTC)

A capacity provider issue interrupted some running nodes. We are recovering the affected nodes now. If one of your nodes was interrupted, the interrupted time is credited to your account automatically - you do not need to file anything.

Aug 26, 2026
3 months ago
Our sandbox check is failing
Resolved · August 26 at 6:02 PM (UTC) (1 hour)

Our sandbox check is passing again: environments prepare, forks start, and commands run normally.

Investigating · August 26 at 4:37 PM (UTC)

Our continuous check of rollout sandboxes - preparing a real environment, forking a sandbox from it, and running a command inside the fork - is failing, and we are investigating what it caught. Creating environments, forking sandboxes, or running commands in them may be delayed or may fail while this is open. Nodes and jobs run on separate machines and are not affected, and sandbox work that fails on our side is not billed: it is safe to retry once this is resolved.

Aug 26, 2026
3 months ago
Our sandbox check is failing
Resolved · August 26 at 2:51 PM (UTC) (7 hours)

Our sandbox check is passing again: environments prepare, forks start, and commands run normally.

Investigating · August 26 at 8:07 AM (UTC)

Our continuous check of rollout sandboxes - preparing a real environment, forking a sandbox from it, and running a command inside the fork - is failing, and we are investigating what it caught. Creating environments, forking sandboxes, or running commands in them may be delayed or may fail while this is open. Nodes and jobs run on separate machines and are not affected, and sandbox work that fails on our side is not billed: it is safe to retry once this is resolved.

Aug 26, 2026
3 months ago
Our sandbox check is failing
Resolved · August 26 at 5:47 AM (UTC) (2 hours)

Our sandbox check is passing again: environments prepare, forks start, and commands run normally.

Investigating · August 26 at 4:15 AM (UTC)

Our continuous check of rollout sandboxes - preparing a real environment, forking a sandbox from it, and running a command inside the fork - is failing, and we are investigating what it caught. Creating environments, forking sandboxes, or running commands in them may be delayed or may fail while this is open. Nodes and jobs run on separate machines and are not affected, and sandbox work that fails on our side is not billed: it is safe to retry once this is resolved.

Aug 26, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 26 at 4:47 AM (UTC) (46 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 26 at 4:01 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 26, 2026
3 months ago
Our sandbox check is failing
Resolved · August 26 at 3:10 AM (UTC) (34 minutes)

Our sandbox check is passing again: environments prepare, forks start, and commands run normally.

Investigating · August 26 at 2:36 AM (UTC)

Our continuous check of rollout sandboxes - preparing a real environment, forking a sandbox from it, and running a command inside the fork - is failing, and we are investigating what it caught. Creating environments, forking sandboxes, or running commands in them may be delayed or may fail while this is open. Nodes and jobs run on separate machines and are not affected, and sandbox work that fails on our side is not billed: it is safe to retry once this is resolved.

Aug 25, 2026
3 months ago
Some submitted jobs are failing
Resolved · August 25 at 6:25 PM (UTC) (2 hours)

Job submissions are working normally again. If one of your jobs failed during this incident, it is safe to resubmit it now.

Investigating · August 25 at 4:24 PM (UTC)

Some jobs are failing during image preparation because of an internal issue on our side - not because of anything in the job itself. We are investigating. Jobs that are already running are not affected. If a job of yours failed with an image-related error, it is safe to resubmit it once this is resolved.

Aug 25, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 25 at 9:55 AM (UTC) (5 minutes)

Job interruptions are back to normal levels.

Investigating · August 25 at 9:50 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.

Aug 25, 2026
3 months ago
The website is having problems
Resolved · August 25 at 2:36 AM (UTC) (10 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 25 at 2:26 AM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Aug 23, 2026
3 months ago
Some sandbox commands are failing on our side
Resolved · August 23 at 11:18 PM (UTC) (10 minutes)

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

Investigating · August 23 at 11:09 PM (UTC)

An elevated share of commands running in rollout 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.

Aug 23, 2026
3 months ago
Some sandbox commands are failing on our side
Resolved · August 23 at 8:10 PM (UTC) (2 hours)

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

Investigating · August 23 at 6:08 PM (UTC)

An elevated share of commands running in rollout 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.

Aug 23, 2026
3 months ago
Some sandbox commands are failing on our side
Resolved · August 23 at 4:58 PM (UTC) (52 minutes)

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

Investigating · August 23 at 4:06 PM (UTC)

An elevated share of commands running in rollout 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.

Aug 23, 2026
3 months ago
Some sandbox commands are failing on our side
Resolved · August 23 at 11:01 AM (UTC) (8 hours)

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

Investigating · August 23 at 10:46 AM (UTC)

An elevated share of commands running in rollout 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.

Resolved · August 23 at 10:35 AM (UTC)

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

Investigating · August 23 at 4:12 AM (UTC)

An elevated share of commands running in rollout 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.

Resolved · August 23 at 4:02 AM (UTC)

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

Investigating · August 23 at 3:27 AM (UTC)

An elevated share of commands running in rollout 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.

Aug 22, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 22 at 9:08 AM (UTC) (4 hours)

Job interruptions are back to normal levels.

Investigating · August 22 at 5:13 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.

Aug 20, 2026
3 months ago
Some sandbox commands are failing on our side
Resolved · August 20 at 4:49 PM (UTC) (58 minutes)

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

Investigating · August 20 at 3:51 PM (UTC)

An elevated share of commands running in rollout 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.

Aug 19, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 19 at 9:24 PM (UTC) (12 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 19 at 9:12 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 19, 2026
3 months ago
Our end-to-end job check is failing
Resolved · August 19 at 9:23 PM (UTC) (7 minutes)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 19 at 9:15 PM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Aug 19, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 19 at 9:09 PM (UTC) (28 minutes)

Job interruptions are back to normal levels.

Investigating · August 19 at 8:41 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.

Aug 18, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 18 at 10:28 PM (UTC) (25 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 18 at 10:02 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 16, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 16 at 2:59 PM (UTC) (41 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 16 at 2:49 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 16 at 2:29 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 16 at 2:18 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 16, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 16 at 11:55 AM (UTC) (12 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 16 at 11:43 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 16, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 16 at 7:44 AM (UTC) (6 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 16 at 7:38 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 15, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 15 at 12:39 PM (UTC) (8 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 15 at 12:31 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 14, 2026
3 months ago
The website is having problems
Resolved · August 14 at 5:44 PM (UTC) (1 hour)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 14 at 5:34 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Resolved · August 14 at 4:45 PM (UTC)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 14 at 4:34 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Aug 13, 2026
3 months ago
Usage reporting is delayed
Resolved · August 13 at 8:14 PM (UTC) (1 hour)

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 · August 13 at 7:08 PM (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.

Aug 13, 2026
3 months ago
The website is having problems
Resolved · August 13 at 8:05 PM (UTC) (11 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 13 at 7:54 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Aug 13, 2026
3 months ago
The website is having problems
Resolved · August 13 at 4:17 PM (UTC) (13 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 13 at 4:04 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Aug 13, 2026
3 months ago
The website is having problems
Resolved · August 13 at 1:38 PM (UTC) (11 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 13 at 1:27 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Aug 13, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 13 at 8:34 AM (UTC) (5 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 13 at 8:30 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 13, 2026
3 months ago
Usage reporting is delayed
Resolved · August 13 at 4:46 AM (UTC) (10 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 · August 13 at 4:35 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.

Aug 12, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 12 at 9:27 PM (UTC) (4 hours)

Job interruptions are back to normal levels.

Investigating · August 12 at 7:29 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.

Resolved · August 12 at 6:42 PM (UTC)

Job interruptions are back to normal levels.

Investigating · August 12 at 5:26 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.

Aug 12, 2026
3 months ago
Some submitted jobs are failing
Resolved · August 12 at 4:40 PM (UTC) (2 hours)

Job submissions are working normally again. If one of your jobs failed during this incident, it is safe to resubmit it now.

Investigating · August 12 at 2:39 PM (UTC)

Some jobs are failing during image preparation because of an internal issue on our side - not because of anything in the job itself. We are investigating. Jobs that are already running are not affected. If a job of yours failed with an image-related error, it is safe to resubmit it once this is resolved.

Aug 12, 2026
3 months ago
Our end-to-end job check is failing
Resolved · August 12 at 5:46 AM (UTC) (7 minutes)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 12 at 5:38 AM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Aug 11, 2026
3 months ago
Our end-to-end job check is failing
Resolved · August 11 at 11:30 PM (UTC) (1 hour)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 11 at 10:27 PM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Aug 10, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 10 at 2:23 AM (UTC) (9 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 10 at 2:14 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 9, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 9 at 4:54 PM (UTC) (9 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 9 at 4:45 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 7, 2026
3 months ago
Usage reporting is delayed
Resolved · August 7 at 10:36 PM (UTC) (2 hours)

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 · August 7 at 8:34 PM (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.

Aug 6, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 6 at 6:21 AM (UTC) (10 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 6 at 6:11 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 5, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 6 at 1:25 AM (UTC) (3 hours)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 6 at 1:16 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 6 at 12:51 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 6 at 12:24 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 6 at 12:15 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 6 at 12:05 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 5 at 11:27 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 5 at 11:08 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 5 at 11:01 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 5 at 10:20 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 4, 2026
3 months ago
Usage reporting is delayed
Resolved · August 5 at 11:50 PM (UTC) (2 days)

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 · August 4 at 5:04 AM (UTC)

Usage and billing data is updating more slowly than usual, so recent activity may not appear on your usage page yet. Your workloads are not affected and no usage records are lost; the numbers will catch up on their own.

Aug 4, 2026
3 months ago
Some running nodes were interrupted
Resolved · August 5 at 11:50 PM (UTC) (1 day)

All affected nodes have been recovered, and interruption credits were applied automatically.

Investigating · August 4 at 10:03 PM (UTC)

A capacity provider issue interrupted some running nodes. We are recovering the affected nodes now. If one of your nodes was interrupted, the interrupted time is credited to your account automatically - you do not need to file anything.

Aug 5, 2026
3 months ago
The website is having problems
Resolved · August 5 at 3:56 PM (UTC) (11 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 5 at 3:45 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Aug 5, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 5 at 4:27 AM (UTC) (4 hours)

Job interruptions are back to normal levels.

Investigating · August 5 at 12:28 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.

Aug 5, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 5 at 1:20 AM (UTC) (15 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 5 at 1:05 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 5, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 5 at 12:34 AM (UTC) (18 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 5 at 12:16 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 4, 2026
3 months ago
Our large-upload and long-build check is failing
Resolved · August 5 at 12:29 AM (UTC) (1 hour)

Our large-upload and long-build check is passing again: multi-part uploads finalize and long image builds complete normally.

Investigating · August 4 at 11:11 PM (UTC)

Our continuous check of the large-input path - uploading a multi-part input and building an image whose build runs for many minutes - is failing, and we are investigating what it caught. Small jobs and already-running workloads are not affected. While this is open, uploading a large input may fail partway or need to be retried, and a long image build may fail near the end. Nothing is lost either way: uploaded parts stay put and can be finalized again, and a job whose build fails is not charged for compute it never received.

Aug 4, 2026
3 months ago
Our end-to-end job check is failing
Resolved · August 4 at 11:52 PM (UTC) (2 hours)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 4 at 10:03 PM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Aug 4, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 4 at 7:05 PM (UTC) (10 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 4 at 6:55 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 4, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 4 at 9:34 AM (UTC) (7 minutes)

Job interruptions are back to normal levels.

Investigating · August 4 at 9:28 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.

Aug 3, 2026
3 months ago
Running jobs are being interrupted more than usual
Resolved · August 4 at 4:19 AM (UTC) (5 hours)

Job interruptions are back to normal levels.

Investigating · August 3 at 11:38 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.

Aug 4, 2026
3 months ago
Our stopped-node wake check is failing
Resolved · August 4 at 2:00 AM (UTC) (38 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 4 at 1:22 AM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 4, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 4 at 1:54 AM (UTC) (23 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 4 at 1:31 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 3, 2026
3 months ago
New nodes are slow to become ready
Resolved · August 4 at 12:16 AM (UTC) (1 hour)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 4 at 12:10 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 4 at 12:06 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 3 at 11:54 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · August 3 at 11:14 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · August 3 at 11:02 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Aug 3, 2026
3 months ago
Usage reporting is delayed
Resolved · August 3 at 1:35 AM (UTC) (11 minutes)

Usage reporting has caught up and is current again.

Investigating · August 3 at 1:24 AM (UTC)

Usage and billing data is updating more slowly than usual, so recent activity may not appear on your usage page yet. Your workloads are not affected and no usage records are lost; the numbers will catch up on their own.

Aug 2, 2026
4 months ago
Running jobs are being interrupted more than usual
Resolved · August 2 at 7:41 PM (UTC) (5 hours)

Job interruptions are back to normal levels.

Investigating · August 2 at 2:37 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.

Aug 2, 2026
4 months ago
Some submitted jobs are failing
Resolved · August 2 at 7:13 PM (UTC) (3 hours)

Job submissions are working normally again. If one of your jobs failed during this incident, it is safe to resubmit it now.

Investigating · August 2 at 4:41 PM (UTC)

Some jobs are failing during image preparation because of an internal issue on our side - not because of anything in the job itself. We are investigating. Jobs that are already running are not affected. If a job of yours failed with an image-related error, it is safe to resubmit it once this is resolved.

Aug 2, 2026
4 months ago
Our stopped-node wake check is failing
Resolved · August 2 at 7:03 PM (UTC) (47 minutes)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Investigating · August 2 at 6:16 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Aug 2, 2026
4 months ago
Our end-to-end job check is failing
Resolved · August 2 at 5:31 PM (UTC) (40 minutes)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 2 at 5:19 PM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Resolved · August 2 at 5:01 PM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Resolved · August 2 at 5:00 PM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 2 at 4:51 PM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Aug 2, 2026
4 months ago
Some submitted jobs are failing
Resolved · August 2 at 5:30 AM (UTC) (2 hours)

Job submissions are working normally again. If one of your jobs failed during this incident, it is safe to resubmit it now.

Investigating · August 2 at 3:29 AM (UTC)

Some jobs are failing during image preparation because of an internal issue on our side - not because of anything in the job itself. We are investigating. Jobs that are already running are not affected. If a job of yours failed with an image-related error, it is safe to resubmit it once this is resolved.

Aug 2, 2026
4 months ago
Our end-to-end job check is failing
Resolved · August 2 at 4:17 AM (UTC) (21 minutes)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · August 2 at 3:55 AM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Aug 1, 2026
4 months ago
The website is having problems
Resolved · August 1 at 7:30 PM (UTC) (50 minutes)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 1 at 7:22 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Resolved · August 1 at 7:17 PM (UTC)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Investigating · August 1 at 6:41 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Jul 31, 2026
4 months ago
Our stopped-node wake check is failing
Investigating · July 31 at 12:54 PM (UTC)

Our continuous check that a stopped node wakes with its files intact is failing, and we are investigating what it caught. Running nodes are not affected, and stopped nodes' files remain safe in durable storage - but waking a stopped node may be slower than usual or fail while this is open. If a wake fails, nothing is lost: it is safe to try again once this is resolved.

Resolved · July 31 at 12:54 PM (UTC)

Our stopped-node wake check is passing again: stopped nodes wake normally with their files intact.

Jul 31, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 31 at 12:54 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 31 at 12:54 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 30, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 30 at 3:31 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 30 at 3:31 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 30, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 30 at 3:31 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 30 at 3:31 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · July 30 at 3:31 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 30 at 3:31 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 30, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 30 at 3:31 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 30 at 3:31 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 29, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 29 at 1:51 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 29 at 1:51 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 29, 2026
4 months ago
The website is having problems
Investigating · July 29 at 1:51 PM (UTC)

Some pages on givemeanode.com are failing to load or are showing an error page. We are investigating. Your nodes and jobs are not affected: everything that is running keeps running, and the API, CLI, and MCP interfaces remain available.

Resolved · July 29 at 1:51 PM (UTC)

The website is loading normally again. Nodes, jobs, and the API were not affected.

Jul 29, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 29 at 1:51 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 29 at 1:51 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · July 29 at 1:51 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 29 at 1:51 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 28, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 28 at 10:43 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 28 at 10:43 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 28, 2026
4 months ago
Our end-to-end job check is failing
Investigating · July 28 at 10:43 AM (UTC)

Our continuous end-to-end check - a small real job submitted through the same pipeline as customer jobs - is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Resolved · July 28 at 10:43 AM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Jul 28, 2026
4 months ago
Some submitted jobs are failing
Investigating · July 28 at 10:43 AM (UTC)

Some jobs are failing during image preparation because of an internal issue on our side - not because of anything in the job itself. We are investigating. Jobs that are already running are not affected. If a job of yours failed with an image-related error, it is safe to resubmit it once this is resolved.

Resolved · July 28 at 10:43 AM (UTC)

Job submissions are working normally again. If one of your jobs failed during this incident, it is safe to resubmit it now.

Jul 27, 2026
4 months ago
Usage reporting is delayed
Investigating · July 27 at 7:29 PM (UTC)

Usage and billing data is updating more slowly than usual, so recent activity may not appear on your usage page yet. Your workloads are not affected and no usage records are lost; the numbers will catch up on their own.

Resolved · July 27 at 7:29 PM (UTC)

Usage reporting has caught up and is current again.

Jul 27, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 27 at 6:00 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 27 at 6:00 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · July 27 at 1:38 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 27 at 1:38 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 25, 2026
4 months ago
Our end-to-end job check is failing
Resolved · July 26 at 3:39 AM (UTC) (8 hours)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Resolved · July 26 at 3:39 AM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Resolved · July 26 at 3:39 AM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Resolved · July 26 at 3:39 AM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Resolved · July 26 at 3:39 AM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · July 25 at 7:19 PM (UTC)

Our continuous end-to-end check — a small real job submitted through the same pipeline as customer jobs — is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Resolved · July 25 at 7:19 PM (UTC)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Jul 26, 2026
4 months ago
Our end-to-end job check is failing
Resolved · July 26 at 2:09 AM (UTC) (23 minutes)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · July 26 at 1:46 AM (UTC)

Our continuous end-to-end check — a small real job submitted through the same pipeline as customer jobs — is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Jul 25, 2026
4 months ago
Our end-to-end job check is failing
Resolved · July 26 at 2:09 AM (UTC) (7 hours)

Our end-to-end check is passing again: jobs are building and running normally through the whole pipeline.

Investigating · July 25 at 7:19 PM (UTC)

Our continuous end-to-end check — a small real job submitted through the same pipeline as customer jobs — is failing, and we are investigating what it caught. Jobs you submit may be delayed or may fail while this is open. Queued jobs keep their place in line, and jobs that cannot run are not charged for compute they never received.

Jul 25, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 25 at 7:16 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 25 at 7:16 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 25, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 25 at 7:16 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 25 at 7:16 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 25, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 25 at 7:16 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 25 at 7:16 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 25, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 25 at 7:16 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 25 at 7:16 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 25, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 25 at 8:30 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 25 at 8:30 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 25, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 25 at 8:30 AM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 25 at 8:30 AM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 24, 2026
4 months ago
New nodes are slow to become ready
Investigating · July 24 at 2:53 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Resolved · July 24 at 2:53 PM (UTC)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Jul 23, 2026
4 months ago
New nodes are slow to become ready
Resolved · July 23 at 8:02 PM (UTC) (19 minutes)

Node provisioning is back to normal. New nodes are becoming ready at the usual speed.

Investigating · July 23 at 7:43 PM (UTC)

Some new nodes are taking longer than usual to become ready. We are investigating. Nodes that are already running are not affected, and pending nodes will come up without any action on your part.

Jul 23, 2026
4 months ago
Some running nodes were interrupted
Resolved · July 23 at 8:00 PM (UTC) (17 minutes)

All affected nodes have been recovered, and interruption credits were applied automatically.

Investigating · July 23 at 7:43 PM (UTC)

A capacity provider issue interrupted some running nodes. We are recovering the affected nodes now. If one of your nodes was interrupted, the interrupted time is credited to your account automatically — you do not need to file anything.

Jul 22, 2026
4 months ago
Usage reporting is delayed
Investigating · July 22 at 8:58 AM (UTC)

Usage and billing data is updating more slowly than usual, so recent activity may not appear on your usage page yet. Your workloads are not affected and no usage records are lost; the numbers will catch up on their own.

Resolved · July 22 at 8:58 AM (UTC)

Usage reporting has caught up and is current again.

powered by openstatus.dev

UTC