Infrastructure Status

EVM JSON-RPC for the Integra mainnet (chain ID 26217), served via Caddy path routing on the mainnet Hetzner gateway (89.167.88.24). Serves all on-chain EVM data including wallet balances, token transfers, smart contract calls, and transaction receipts.

CometBFT RPC for the Integra mainnet, served via Caddy path routing on the mainnet Hetzner gateway (89.167.88.24). Handles block queries, transaction broadcasting, validator set lookups, and consensus state. Powers the mainnet block explorer with live chain data.

Cosmos REST/LCD for the Integra mainnet, served via Caddy path routing on the mainnet Hetzner gateway (89.167.88.24). Serves governance, staking, and account queries over HTTP.

EVM JSON-RPC for the Integra testnet (chain ID 26218), served via Caddy path routing on the Helsinki gateway (46.225.231.81). Used by the development team for testing smart contract deployments, EVM transaction flows, and wallet integration. Downtime blocks the entire dev team from testing any EVM-related feature changes.

CometBFT RPC for the Integra testnet chain, served via Caddy path routing on the Helsinki gateway (46.225.231.81). Provides block data, transaction broadcasting, and consensus state for development and QA. Powers the testnet block explorer with live chain data.

Cosmos REST/LCD for the Integra testnet, served via Caddy path routing on the Helsinki gateway (46.225.231.81). Serves governance, staking, and account queries over HTTP for development.

The primary backend powering the Integra Dashboard with 75+ REST API endpoints, built with NestJS, PostgreSQL, and JWT authentication. Handles portfolio management, staking position tracking, XP/points integration, asset management, bulk CSV imports, and notification preferences. The production Dashboard frontend is 100% dependent on this — if it goes down, users see a blank dashboard. Depends on the Absinthe XP API for points and leaderboard data. Deep health checks verify database connectivity and cache availability.

Development instance of the Dashboard API, running the same NestJS codebase as production but connected to testnet blockchain networks and a separate dev database. Used by Nawar and the backend team for feature development, API testing, and QA validation before promoting changes to production. Also depends on Absinthe for XP features. If down, the dev Dashboard frontend is completely unusable, blocking frontend development and integration testing.

Push notification service built with NestJS, responsible for delivering real-time alerts to Dashboard users for staking rewards, governance proposal updates, transaction confirmations, and account activity. Processes event triggers from the Dashboard API and dispatches notifications via push and in-app channels. If this service goes down, users miss time-sensitive alerts about their staking rewards and governance votes. Deep health checks monitor database and queue connectivity.

Development instance of the Notification API, used for testing notification delivery logic, alert templates, and event trigger configurations before production deployment. Runs against a separate dev database and test notification channels. Essential for validating that new notification types render correctly and trigger at the right events. If down, the dev Dashboard loses notification functionality, blocking QA on notification-related features.

The game backend for City of Integra, a gamified city builder experience hosted on AWS App Runner in ap-south-1 (Mumbai). Manages all game state including building placement, resource generation, city progression, upgrade paths, and player inventories. The City Builder frontend is 100% dependent on this service — without it, the game is completely unplayable. Deep health checks verify database connectivity and game state consistency. Contact Kalki for game logic issues or Nawar for infrastructure/deployment concerns.

Development instance of the City of Integra game backend on AWS App Runner (Mumbai), used for testing new game mechanics, balance tuning, feature prototyping, and QA before production release. Runs against a separate dev database with test game state. If down, Kalki and the game team cannot test new features or validate bug fixes. Also used for load testing game logic before mainnet events.

A lightweight API endpoint serving the current circulating supply of IRL tokens, consumed by cryptocurrency exchanges (for market cap calculations), data aggregators like CoinGecko and CoinMarketCap, and portfolio trackers. Returns a single number but has outsized importance — incorrect or unavailable supply data causes wrong market cap figures across all listing platforms. Hosted on Polytrade infrastructure (legacy domain). Contact Parth for supply calculation logic updates.

Real-time token pricing API that aggregates IRL and related token prices from multiple sources, serving them to the Dashboard for portfolio valuations, staking reward estimates, and transaction value displays. If this endpoint goes down or returns stale data, users see incorrect portfolio totals and missing price charts in the production Dashboard. Hosted on Polytrade infrastructure. No external dependencies but impacts user confidence when prices appear stale or zero.

Stateless microservice that generates time-limited pre-signed AWS S3 URLs for secure file uploads, used by the Dashboard for document uploads (KYC, title deeds) and the City Builder for asset uploads. Each URL expires after 15 minutes and is scoped to a specific S3 path. If down, all file upload workflows across the platform fail silently — users see upload buttons but files never reach S3. Contact Parth for S3 bucket configuration or CORS issues.

Companion service to the Presigned URL API that tracks file upload progress, stores metadata (file size, type, upload timestamp), and confirms successful uploads to the requesting application. The Dashboard polls this service to show upload progress bars and confirm document receipt. If down, uploads still succeed (files reach S3) but the frontend shows perpetual "uploading" spinners and cannot confirm completion to the user.

The backend API service for the mainnet block explorer, built with Node.js and BullMQ. Handles block indexing, transaction processing, and serves the explorer frontend with blockchain data via REST endpoints. The /api/status endpoint returns sync state, worker health, and queue metrics. If this backend is down, the explorer frontend shows stale or no data.

The backend API service for the testnet block explorer, same stack as mainnet (Node.js + BullMQ). Indexes Ormos testnet blocks and transactions, serving the testnet explorer frontend. Used by the dev team for testing explorer features and verifying testnet chain activity.

The mainnet block explorer built with Next.js and deployed on Vercel, providing transaction lookup, block browsing, validator profiles, governance proposal tracking, and account balance queries. This is the primary tool for anyone inspecting on-chain activity — validators checking their signing status, users verifying transactions, and developers debugging contract interactions. Depends on both the Cosmos RPC (for real-time blocks) and REST/LCD (for validator and governance data). Contact Kalki for explorer application issues.

Testnet block explorer for the Ormos chain, running the same Next.js codebase as the mainnet explorer but connected to testnet RPC and REST endpoints. Used daily by the dev team to verify test transactions, inspect testnet blocks, and validate governance features during QA. Depends on testnet Cosmos RPC and REST. If down, developers lose visibility into testnet chain activity and must resort to CLI queries for debugging.

Blockscout EVM block explorer for the Integra testnet (chain ID 26218), deployed via Docker Compose on the Helsinki gateway (46.225.231.81). Backend on port 4001, frontend on port 3002. Caddy reverse proxies testnet.blockscout.integralayer.com. Used by the dev team for inspecting testnet EVM transactions, verifying contract deployments, and testing token transfers.

The Integra infrastructure status page deployed on EC2 (3.92.110.107) at status.integralayer.com via Caddy reverse proxy (port 3003). Monitors 55+ endpoints across blockchain nodes, validators, APIs, frontends, and external services. Self-monitoring ensures the status page itself is accessible when users need to check system health during incidents. Telegram bot @IntegraHealthBot sends alerts on status transitions.

Validator dashboard web app built with Next.js 15 + TypeScript + Tailwind + shadcn/ui, deployed on Vercel. Features chain status monitoring, health dashboard, wallet connect (MetaMask/Keplr/OKX), and a mainnet/testnet network toggle. Provides validators and stakers with a quick overview of network health and their staking positions across both networks.

The mainnet blockchain portal for Integra Layer, providing a unified gateway to network metrics (block height, total bonded, active validators), validator browsing, governance proposals, chain parameters, and node operator dashboard. Also lists all mainnet RPC/REST/WebSocket endpoints for developers. This is the primary entry point for validators and stakers interacting with the Integra mainnet. Deployed on Vercel with Next.js.

The testnet blockchain portal for the Ormos chain, same app as mainnet but connected to testnet endpoints. Provides network metrics, validator list, governance proposals, and chain parameters for the Ormos testnet (EVM chain ID 26218). Used by the dev team and external testers to interact with the testnet. If down, validators and testers lose the primary UI for testnet chain interaction.

Developer documentation site built with Docusaurus and hosted on Vercel, containing API references, SDK integration guides, node operator runbooks, architecture overviews, and smart contract documentation. This is the first stop for external developers integrating with Integra and for internal team members referencing API specs. If down, developer onboarding stalls and the team loses access to canonical API documentation. Contact Tara for content updates or Vercel deployment issues.

The primary public-facing website for Integra Layer, built with Next.js and deployed on Vercel. Serves as the main entry point for potential users, investors, partners, and developers discovering the Integra ecosystem. Contains the product overview, team page, ecosystem links, blog, and investor materials. Downtime is highly visible — it is the first URL shared in pitches, press releases, and social media. Contact Tara for content or deployment.

The production Integra Dashboard — the flagship user-facing application built with React and deployed on Vercel. Provides portfolio management, staking delegation, XP tracking, asset management, leaderboard rankings, and notification preferences. This is where Integra users spend most of their time and is the single most important frontend service. Fully depends on the Dashboard API for all data. If the frontend itself is down (Vercel issue), users cannot access any platform features. Contact Nawar for API-related issues or Tara for frontend bugs.

Development instance of the Dashboard frontend on Vercel, connected to the dev Dashboard API and testnet blockchain endpoints. Used by Tara and the frontend team for building and testing new UI features, validating design changes, and running E2E tests before production deployment. Also serves as the staging environment for stakeholder previews. If down, frontend development is blocked and the team cannot demo upcoming features.

The production City of Integra web application — a gamified city builder where users construct and manage virtual cities to earn XP and rewards. Built with React and deployed on Vercel, it renders an interactive isometric city view with real-time building placement and resource management. Fully depends on the City API for all game logic and state persistence. If the frontend is down, users cannot access the game at all. Contact Kalki for game-related issues or Tara for frontend deployment.

Development instance of the City of Integra frontend on Vercel, used by Kalki for testing new game UI features, building animations, and UX improvements before production. Connected to the dev City API with test game state. Also used for playtesting new mechanics and balance changes with the team before releasing to users.

The Integra Layer technical whitepaper, a static site on Vercel detailing the protocol design, CometBFT consensus mechanism, EVM module architecture, tokenomics (IRL supply, staking rewards, inflation), and network governance model. This document is referenced in investor due diligence, exchange listing applications, and developer onboarding. Downtime prevents potential investors and partners from accessing critical technical information. Contact Tara for content updates.

The XP Portal built with React on Vercel, where users track their accumulated points, view real-time leaderboard rankings, complete quests, and claim rewards. This is a key community engagement tool — active users check it daily for leaderboard position changes and new quest availability. Depends entirely on the Absinthe XP API for all points data and leaderboard calculations. If Absinthe is down, the portal shows stale or empty data. Contact Tara for frontend issues or Parth for Absinthe integration.

The staking interface built with React on Vercel (Polytrade legacy domain), where users delegate IRL tokens to validators, manage their delegation positions, redelegate between validators, and claim accumulated staking rewards. This is critical for network security — it is the primary way token holders participate in consensus by staking. If down, users cannot delegate or claim rewards, potentially impacting validator economics and network security participation rates. Contact Tara for frontend issues.

NFT metadata and media storage service hosted on Vercel, serving asset images, metadata JSON files, and collection information for NFT display across the Dashboard and marketplace features. Follows the ERC-721/1155 metadata standard so wallets and aggregators can resolve token URIs. If down, NFT thumbnails and metadata fail to load across the platform — users see broken images and missing asset names. Contact Tara for deployment or Parth for metadata schema changes.