API Gateway
CheckingAgent calls, Registry queries, and run submission may fail when this is unavailable.
SignalHealth check
Evidence/healthz
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
Database
CheckingSign-in, configuration reads, and run records may be unavailable when this is down.
SignalDB health check
Evidence/healthz/db
Registry
CheckingAgent lists, detail pages, and Skill filters may fail to load when this is unavailable.
SignalPublic API
Evidence/api/v1/agents
Discovery
CheckingClients may be unable to discover API, MCP, and A2A entry points when this is unavailable.
SignalAgent/MCP discovery
Evidence/.well-known/openlinker.json
Core Readiness
CheckingCore dependencies or the internal Runtime cluster may not be ready to receive traffic.
SignalDependencies and Runtime cluster
Evidence/readyz
Public Runtime ingress
CheckingExternal Runtime Workers may be unable to reach the ingress advertised by discovery.
SignalDiscovery endpoint reachability
Evidencebase_urls.runtime
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.