---
title: "System status · Specoria"
description: "What our own systems measure right now: internal counters, planned maintenance and what we can’t measure yet, read live from our status.json file."
source_url: "https://specoria.com/status/"
lang: "en"
---

STATUS

# System status

What our own systems measure right now: internal counters, planned maintenance and what we can’t measure yet, read live from our status.json file.

status.json

## Live status

This box reads status.json when the page opens and shows the components, planned maintenance and our internal measurements. If JavaScript is off, open the file directly: [/status.json](https://specoria.com/status.json)

- There is no independent external monitor yet, so no component is shown as working. What we can’t measure is written as unknown.

- Numbers come only from our own records. Rates are not written below 20 samples.

- No domain, IP address or customer detail is published; only totals.

Machine-readable version: [/status.json](https://specoria.com/status.json) (also at /.well-known/status.json).

Components

## What each group covers

The live box sorts components into six groups. Each line below says what a group contains and what its numbers are based on.

- Scanning: the free test, the Scan API and the MCP server with its read API. The MCP line counts read calls answered and not finished.

- Real-browser jobs: the agent simulator and the deep audit, which open your store in a real browser. Completed and failed runs are counted.

- Panel and reports: the customer panel, PDF generation (audits that stopped at the PDF step are counted) and Agent Showcase publishing, with how many showcases were health-checked.

- Monitoring: the hourly scheduled run and the daily store checks. The time of the last run is shown, not a promise about the next one.

- Measurement services: AI visibility measurement (complete, partial and failed runs) and log ingest (batches received, rows kept, lines skipped).

- External providers: the AI model providers we call. Their own status pages are the source for outages on their side.

Maintenance

## How we announce maintenance

We schedule planned maintenance at low-traffic hours where possible and announce it to affected customers by email at least 48 hours in advance. Every scheduled maintenance is also listed here and in the maintenance field of status.json. Urgent security updates may be applied without notice. [Service level agreement](https://specoria.com/service-level-agreement/)

Contact

## Seeing a problem?

If something on our side looks broken and this page doesn’t show it yet, write to [contact@specoria.com](mailto:contact@specoria.com) with the time, the page or store address and what you saw. We answer from the same address and, if it affected you, say what we changed.