---
title: "Status | Spatial Compiler"
description: "Live status of the Spatial Compiler website, console, API, hosted MCP and bake service, with 90 days of check history and the incidents list."
canonical: https://appliedmanifold.com/status/
site: "Applied Manifold: The spatial compute cloud for 3D reality"
---

1.  [Home](https://appliedmanifold.com/)
2.  Status

STATUS // SPATIAL.COMPILER

# Status

The current state of each Spatial Compiler service, checked every 5 minutes, with 90 days of history. Times are in UTC.

## Services

Status loads in your browser from the status service. If nothing appears, open the [status service page](https://am-status.eyal-bbf.workers.dev/).

## Incidents

## How each service is checked

A check runs every 5 minutes. A service counts as operational when its latest check passes.

-   **Website:** the home page at appliedmanifold.com loads.
-   **Console:** the console health check at console.appliedmanifold.com answers OK.
-   **API:** the API health check at api.spatialcompiler.dev answers OK.
-   **Hosted MCP:** the hosted MCP health check at mcp.spatialcompiler.dev answers OK.
-   **Compile service:** the API lists hosted pyrofx compiles. This check does not ping an individual compile worker.

Each day in the history bar sums that day's checks, from midnight to midnight UTC. A day with no checks shows as no data. The raw data is at [`https://am-status.eyal-bbf.workers.dev/api/status`](https://am-status.eyal-bbf.workers.dev/api/status).

For how your data is stored and who can see it, read [Security and data](https://appliedmanifold.com/security/).
