Status

Farpy status

Check rendering, delivery, receipt, wallet, and website signals. Public health endpoints expose operational state without exposing private job files, account secrets, or internal filesystem paths.

Checking

Checking availability

Loading the live status.

Technical details
Live availability feed
/node/v1/blender52/availability
Frames per job
—
Jobs at a time
—
Jobs left in this release
—

Public status

Website

Green

Public pages, docs, and this status page are served. Sign-in and signup depend on the account service, which this page does not check.

Wallet

Not live-checked

Balance, card and Lightning top-ups, charges, and refunds depend on the wallet and payment services, which this page does not check. If the account or wallet cannot be reached, the top-up page shows an error instead of opening checkout.

Rendering

Limited public ordering

Website ordering runs as a limited release: Blender 5.2.2 Cycles CUDA, 1–10 frames per job, one job at a time, while release slots remain. The live availability card shows whether new orders are open right now. Admission closes automatically when slots are used or capacity is not qualified. This is not a capacity or SLA claim.

GPU capacity

Unknown

No live customer-availability feed is published. Service health and installed provider adapters are not customer capacity.

Downloads

Not live-checked

A private ZIP is the verified artifact. A progress state of complete is not the same as financial capture. Each job's workspace page shows whether its download is available.

Receipts

Not live-checked

Delivery receipts include SHA-256, cost, renderer, and frame count. A receipt link shows that the receipt is unavailable when the receipt service cannot be reached.

Health checks

These endpoints are machine-readable operational checks. A successful HTTP response means the endpoint answered; it does not mean renders are admitted. The capabilities endpoint describes the API contract, not current customer admission.

How to read this status page

Green means the listed public function is available according to the current published status model. Not live-checked means this page does not test the function; use the health checks, your workspace, or the receipt link for its current state.

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

FARPY does not publish a live customer-availability feed, so this page shows availability as unknown. Provider adapters and service health 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.