Status Pages Built for Web3 Infrastructure
When something goes wrong, your users deserve to know whether the problem is their wallet, your dApp, or the underlying chain. Give them a real-time status page that understands Web3 - with RPC health, on-chain component status, and incident timelines built in.
Why generic status pages fail Web3 teams
- Tools like Atlassian Statuspage and Betterstack have no concept of chains, RPC endpoints, or on-chain state - they were built for Web2 SaaS availability, not decentralized infrastructure. Betterstack is an example of a generic approach that Web3 teams need to go beyond. Betterstack status page approach
- Users cannot tell if disruption is in your dApp, the RPC provider, or the underlying blockchain itself
- Incident communication happens across Slack, Twitter, and email with no single source of truth for users
- Manual status updates during incidents slow down response and leave users uninformed for too long
A status page that speaks Web3 natively
- Add RPC endpoints and chains as first-class components - their health updates automatically from your monitors
- Incident timelines with markdown support give users chronological, accurate communication in one place
- Email, RSS, and webhook subscriber notifications keep users informed without requiring them to check manually
- White-label branding with custom domain, logo, colors, and CSS overrides - looks like yours, not ours
- BlackTide's status page integrates directly with your monitors - no manual toggling required. As your engineering practice matures, consider pairing it with your incident runbooks for a complete communication workflow. incident communication best practices
Capabilities
Everything a Web3 team needs in a status page
From component health to incident communication - purpose-built for on-chain infrastructure.
RPC endpoints, chains, APIs, and custom services are all first-class components. Health updates automatically from your BlackTide monitors - no manual status toggling. When an RPC monitor detects block height lag exceeding your threshold, the corresponding status page component automatically transitions to 'Degraded' - your users see the problem reflected in real time without any manual intervention from your team.
Model complex multi-chain infrastructure accurately with nested components - Ethereum mainnet, Optimism, and Arbitrum as sub-components of your RPC layer. This granularity lets users understand exactly what is affected: if Arbitrum RPC is degraded but Ethereum is healthy, users can continue Ethereum transactions without confusion about the scope of the incident.
Chronological incident updates with markdown support give your users and stakeholders a single, clear record from detection through resolution. Incident timelines with markdown let you include technical detail for developers (block height, RPC error codes) and plain-language updates for end users in the same record - filtered by audience.
Users subscribe via email, RSS, or webhook and receive automatic notifications when incidents are created, updated, or resolved. Email subscribers receive HTML-formatted incident notifications with component status, affected chains, and a link to the full incident timeline - reducing support volume by keeping users proactively informed.
Custom domain, your logo, your brand colors, and full CSS overrides. Your status page should look like it belongs to you, not to a third-party tool. Enterprise teams can inject custom CSS that completely overrides BlackTide's default styles - achieving a status page visually indistinguishable from a custom-built solution at a fraction of the development cost.
Use Cases
Who uses BlackTide status pages
DEX with a public status page during upgrades
Smart contract upgrades cause temporary disruption. A public status page with real-time component health and an incident timeline prevents user confusion and support volume spikes.
RPC provider with B2B client SLAs
Your B2B clients have SLA expectations and need transparent uptime reporting. BlackTide's status page surfaces per-chain availability data your clients can trust.
Validator team with an internal health dashboard
Not every status page needs to be public. Internal status pages give your operations team a unified view of node health across all chains without building a custom dashboard.
BlackTide vs the status page alternatives
Web3 infrastructure needs more than a color-coded grid of checkboxes.
| Feature | BlackTide | Atlassian Statuspage | Betterstack |
|---|---|---|---|
| Web3 component types (RPC, chain) | |||
| Auto-sync from monitors | partial | ||
| Custom domain | |||
| White-label CSS overrides | Paid tier | Paid tier | |
| Sub-components per chain | partial | ||
| Pricing for small teams | Affordable | Expensive | Moderate |
| Incident history and uptime reports | |||
| RSS and webhook subscriptions | partial |
Frequently asked questions
Can I use a custom domain?
Is the status page public or private?
How do I add RPC health as a component?
Do subscribers get notified automatically?
Can I white-label it completely?
How does the status page update during an incident?
Used by
Monitoring for DeFi Protocols
DeFi protocols run 24/7 across multiple chains - one stale oracle or one silent RPC failure is enough to drain liquidity or halt a protocol.
Monitoring for NFT Marketplaces and Platforms
A failed drop is a PR disaster - monitor gas prices, contract events, IPFS availability, and frontend health before the mint window opens.
Monitoring for Teams Migrating from Web2 to Web3
You're adding blockchain features to your SaaS product but your SRE team doesn't know eth_blockNumber from HTTP 200 - BlackTide handles the Web3 monitoring so you don't have to learn it all overnight.
Give your users a status page they can actually trust.
Real-time, Web3-aware, and completely white-labeled.