Status

System status

Live health of every FeedPlumb service, checked from your browser against each service's own health endpoint.

Checking services…

20 FeedPlumb checks + 2 XDC ecosystem checks · running · refreshes every 60 s

Core

Website · FeedExplorer
serving pages
FeedExplorer →19 msOperational
Feeds API · FeedExplorer

FeedExplorer →Checking…
Feed snapshots (freshness) · FeedExplorer

FeedExplorer →Checking…
MCP endpoint · AgentGateway

AgentGateway →Checking…

APIs

Subscriber workspace · DataQuery
HTTP 200
DataQuery →20 msDown
Pay-per-call settlement · DataQuery
HTTP 200
DataQuery →20 msDown
Webhooks API · EventHook

EventHook →Checking…
Data API · DataQuery

DataQuery →Checking…
Route-quote API · RouteQuote

RouteQuote →Checking…
Supply API · ListingReady

ListingReady →Checking…
Document proof API · DocAnchor

DocAnchor →Checking…
Validator statements · RewardStatement

RewardStatement →Checking…
Source-verification check · AuditReady

AuditReady →Checking…
Masternode pre-flight · MasternodeSetup

MasternodeSetup →Checking…
Attestation API · AttestHub

AttestHub →Checking…

Monitors & jobs

Ecosystem analytics · MetricsDesk

MetricsDesk →Checking…
Node checks · NodeAlert

NodeAlert →Checking…
White-label feed health · FeedHealth

FeedHealth →Checking…
Reserve feeds hourly check · ReserveProof

ReserveProof →Checking…
Security alert feed · ProtocolAlert

ProtocolAlert →Checking…

XDC ecosystem

Services run by other XDC projects that FeedPlumb reads data from. They are not FeedPlumb services and are not counted in the overall status above. Your browser does not contact them: the FeedPlumb server checks them once an hour, and each row shows its last result with the time it was checked, in Amsterdam time. Figures: StorX (SRX) statistics. StorX is an independent project; FeedPlumb is not affiliated with it.

StorX S3 gateway
S3 endpoint answers (HTTP 401) · last result kept · Last updated 23 Oct 2026, 12:19 CEST (250.5 h ago) · older than 90 minutes
External ecosystem1549 msReachable
StorX farmer API
aggregate stats answer (HTTP 200) · last result kept · Last updated 23 Oct 2026, 12:19 CEST (250.5 h ago) · older than 90 minutes
External ecosystem683 msReachable

Feed network

Loading feed snapshot…

How this works: your browser calls the health endpoints listed above on this same domain. Nothing is stored and no third party is contacted. Latency includes your own connection; for the XDC ecosystem rows it is the FeedPlumb server's request time at its last hourly check.