Farpy status

Public status

Health checks

• Public API health
• Public API capabilities

These endpoints are machine-readable operational checks. A successful HTTP response means the endpoint answered; read its returned state before assuming the associated render or worker path is available.

How to read this status page

Green means the listed public function is available according to the current published status model. Limited visibility means the function exists, but the public page does not expose complete operational detail for every worker and queue.

Capacity is separate from general website availability. The website can be reachable while GPUs are busy, fleet data is stale, or estimated availability is temporarily unavailable.

Capacity and queue signals

The capacity panel reads the live GPU capability response. It lists each workload lane from that response. An unavailable lane stays unavailable, and provider adapters are not shown as capacity.

Capacity can change after this page loads. Check again immediately before submitting time-sensitive work, especially when a project contains many frames or depends on a narrow completion window.

Status does not guarantee a job result

Public operational status is not a guarantee that a specific Blender project will render successfully. Scene compatibility, missing assets, memory use, unsupported configuration, upload validity, and job lifecycle state can still affect an individual submission.

Use the workspace or public API job-status response for the authoritative state of a submitted job. Download, receipt, and proof availability depend on that job reaching the relevant lifecycle state.

Where to check a specific problem

• Use the workspace for browser-submitted job state and available output.
• Use the public API status operation for API-submitted jobs.
• Use the receipt route for completed job and charge records.
• Use the files guide for output ZIP, private-link, and retention guidance.
• Use the proof index for public verification examples.

Open the workspace, review the API quickstart, read the files guide, inspect receipt guidance, or browse the proof index.

Limitations

This page is an operational summary, not a historical uptime report or service-level agreement. It does not publish an uptime percentage, incident archive, recovery-time promise, or permanent-capacity guarantee.

The current status model intentionally distinguishes known green functions from areas with limited public visibility. It does not turn missing telemetry into a green result.

Status questions

Does a green website status mean a GPU is immediately available?

No. Website availability and GPU capacity are separate signals.

Does HTTP 200 from a health endpoint mean everything is healthy?

No. It means the endpoint answered. Read the returned operational state.

Where should I check my submitted render?

Use the workspace or the public API job-status operation for that specific job.

Does this page provide an uptime guarantee?

No. This status page is not a service-level agreement or historical uptime report.

Are private job files exposed here?

No. The public status links are not intended to expose private files, account secrets, or internal paths.