This guide walks you through all features of the pNode Pulse analytics platform.
Live Demo: pulse.rectorspace.com
- Getting Started
- Dashboard Overview
- Network Statistics
- Node List
- Node Details
- Leaderboard
- Storage Analytics
- Network Health
- Historical Data
- Embeddable Badges
- API Access
- Language Support
Visit pulse.rectorspace.com to access the live platform. No account required.
The platform provides real-time visibility into the Xandeum pNode network:
- 200+ nodes tracked across the gossip network
- Real-time metrics updated every 30 seconds
- Historical trends stored in TimescaleDB
- Network health scoring and alerts
The main dashboard at pulse.rectorspace.com provides a comprehensive view of the Xandeum pNode network.
| Metric | Description |
|---|---|
| Total Nodes | Number of nodes discovered in the gossip network |
| Network Storage | Combined storage capacity across all nodes |
| Avg CPU | Average CPU utilization network-wide |
| Avg Uptime | Average node uptime |
- Network Health - Visual gauge showing overall network status
- Version Distribution - Pie chart of pNode software versions
- Network Growth - Historical chart of node count over time
- Node Leaderboard - Top performing nodes by storage/uptime
- Storage Projection - Predicted network capacity growth
- Performance Comparison - Side-by-side node metrics
- Graveyard Stats - Inactive/archived nodes tracking
- IP Changes - Recent IP address changes detected
At the bottom of the dashboard, you'll find:
| Stat | Description |
|---|---|
| Active Nodes | Nodes responding to polls (green) |
| Inactive Nodes | Nodes not responding (orange) |
| Avg RAM Usage | Network-wide memory utilization |
| Peer Connections | Total gossip network connections |
Shows when the last data collection occurred and recent collection history.
Navigate to /nodes to see all discovered nodes.
- Status: Active, Inactive, All
- Version: Filter by specific pNode version
- Public/Private: Filter by RPC accessibility
Click column headers to sort by:
- Address
- Version
- Last Seen
- Uptime
- Storage
Each row displays:
| Column | Description |
|---|---|
| Address | IP:Port of the node |
| Version | pNode software version |
| Status | Active/Inactive indicator |
| Public | Whether RPC port is accessible |
| Last Seen | Time since last successful poll |
| Uptime | Node uptime in human-readable format |
Click any node to view detailed information at /nodes/[id].
- Node Identity: Address, pubkey, version
- Status: Current state (Active/Inactive/Archived)
- Accessibility: Public/Private RPC status
Real-time and historical metrics:
| Metric | Description |
|---|---|
| CPU % | Current processor utilization |
| RAM Used/Total | Memory consumption |
| Storage Committed | Allocated storage space |
| Storage Used | Actual data stored |
| Uptime | Time since node started |
| Packets Sent/Received | Network traffic |
| Active Streams | Current data streams |
Time-series charts showing:
- CPU usage over time
- RAM utilization trends
- Storage growth
- Uptime patterns
- Total Committed: Sum of all node storage allocations
- Total Used: Actual data stored across network
- Utilization %: Storage efficiency ratio
Each node with v0.7.0+ reports:
storage_committed: Allocated capacitystorage_used: Actual usagestorage_usage_percent: Utilization rate
Based on historical data, the platform projects:
- 7-day growth forecast
- 30-day capacity estimate
- Network expansion trends
| Status | CPU | RAM | Description |
|---|---|---|---|
| Healthy | < 50% | < 70% | Normal operation |
| Warning | 50-80% | 70-85% | Monitor closely |
| Critical | > 80% | > 85% | Attention needed |
The platform tracks version distribution:
- Current: Latest stable version
- Outdated: Older but functional versions
- Unknown: Nodes with version detection issues
Select from predefined ranges:
- Last 1 hour
- Last 24 hours
- Last 7 days
- Last 30 days
- Custom range
- Metrics: Stored indefinitely in TimescaleDB
- Aggregates: Daily/weekly rollups for efficiency
- Node History: Full lifecycle tracking
Data can be exported via the API for external analysis.
Navigate to /leaderboard for node rankings.
| Category | Description |
|---|---|
| Uptime | Longest-running nodes |
| Storage | Most storage committed |
| Performance | Best CPU/RAM efficiency |
- Top 10 nodes per category
- Your Node - Find your node's ranking
- Historical - Track ranking changes over time
- Badges - Embed rankings on external sites
Display live network stats on your website or README.
| Badge | URL | Description |
|---|---|---|
| Network Status | /api/badge/network.svg |
Total nodes and health |
| Storage | /api/badge/storage.svg |
Network storage capacity |
| Version | /api/badge/version.svg |
Latest pNode version |
Markdown:
HTML:
<img
src="https://pulse.rectorspace.com/api/badge/network.svg"
alt="pNode Network Status"
/>Badges are SVG format for crisp display at any size. They update automatically with live data.
Access network data programmatically via our REST API.
# Get network overview
curl https://pulse.rectorspace.com/api/trpc/network.overview
# Get node list
curl "https://pulse.rectorspace.com/api/trpc/nodes.list?input={\"limit\":10}"
# Check health
curl https://pulse.rectorspace.com/api/healthFull API documentation: API Reference
Currently no rate limits. Please be respectful with request frequency.
pNode Pulse supports multiple languages.
| Language | Code | URL |
|---|---|---|
| English | en |
/en (default) |
| Spanish | es |
/es |
| Chinese | zh |
/zh |
| Russian | ru |
/ru |
- Auto-detected from browser preferences
- Manual selection via URL prefix
- Preference stored in cookie
| Key | Action |
|---|---|
/ |
Focus search |
r |
Refresh data |
? |
Show help |
- Verify the collector is running
- Check database connectivity
- Ensure seed nodes are reachable
- Check collector logs for errors
- Verify network connectivity to pNodes
- Review collection status widget
- Node may have private RPC (expected for most nodes)
- Check if node IP has changed
- Verify node is still running
Q: Why do most nodes show as inactive?
A: Only ~6 nodes have public RPC ports. Private nodes are still healthy but can't be polled directly. We get their data via public nodes' get-pods-with-stats.
Q: How often is data updated?
A: The collector polls every 30 seconds for active nodes.
Q: What's the difference between Active and Public?
A: Active means the node is responding to polls. Public means its RPC port (6000) is accessible from the internet.