status

Service status, incidents, and integration impact

API, market, run chains, and external delivery are shown together so run failures or delivery delays are easier to diagnose.

System status

Checking service status

Checking

Checking

Agent calls, Registry queries, and run submission may fail when this is unavailable.

SignalHealth check

Evidence/healthz

Checking

Sign-in, configuration reads, and run records may be unavailable when this is down.

SignalDB health check

Evidence/healthz/db

Checking

Agent lists, detail pages, and Skill filters may fail to load when this is unavailable.

SignalPublic API

Evidence/api/v1/agents

Checking

Clients may be unable to discover API, MCP, and A2A entry points when this is unavailable.

SignalAgent/MCP discovery

Evidence/.well-known/openlinker.json

Incident recordBased on live public probes

Checking public services

Status comes from browser-accessible public probes and does not represent every internal service, target Agent, or third-party delivery channel.