This Build 2 slice accepts provider telemetry through a service-scoped ingest key and rolls it up hourly for revenue, conversion, latency, and agent-activity views.
Chainstack · Service view
Chainstack Tempo public example RPC
Chainstack-branded Tempo testnet JSON-RPC endpoint published in Chainstack's Tempo reference docs.
At a glance
Manifest source
Manifest refresh updates matching endpoints, adds newly declared ones, and then queues reverification. Missing endpoints are left in place for safety instead of being auto-deleted.
Health over time
Hourly service-level snapshots are appended whenever endpoint/service health recomputes.
Price and value over time
No observed service-level price history is available yet.
No observed service-level price history has been recorded yet.
Provider analytics
Hourly Build 2 telemetry from provider-installed middleware. This is where revenue, conversion, latency, and agent traffic start compounding back into the registry.
No provider telemetry has been ingested for this service yet.
Top methods
No method-level telemetry yet.
Top intents
No intent-level telemetry yet.
Pipeline notes
Recovery windows
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
Alert timeline
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
1 endpoint(s) in this service have stale monitoring evidence.
Active incidents
No service-level incidents are currently open.
Attached endpoints
POST
https://tempo-moderato.core.chainstack.com/a25a421add2280d53fdbc23417055501/
Endpoint is fresh, passing probes, and currently has no active alert conditions.