All Systems Operational

Real-time health and uptime monitoring for the Specula platform — every service, every component, continuously tracked.

All Systems Operational Updated every 60 seconds Last 30 days
All Systems Operational

No active incidents · Monitoring 8 services · Last checked moments ago

99.4%
30-Day Uptime
147ms
Avg Execution Latency
18K/s
On-Chain Events/Sec
3
Incidents (30 days)
01

Service Status

Bot Execution Engine
Copy trading execution, Exit Mirror™, Cascade detection
Operational
On-Chain Data Feed
Block indexer, event pipeline, 18K events/sec
Operational
Wallet Tracker
Whale wallet monitoring, Ghost Wallet scoring
Operational
API
REST API v1, rate limiting, authentication
Operational
Dashboard
Web application, portfolio UI, analytics
Operational
Notifications
Email, push, Telegram, webhooks
Operational
Payment Verification
On-chain USDC payment detection, subscription activation
Operational
Arb Scanner
Cross-platform probability arbitrage monitoring
Operational
02

30-Day Uptime History

Each bar represents one day. Green = fully operational. Yellow = degraded performance. Red = partial outage. Hover over bars to view status.

30 days ago  →  Today 99.4% uptime
30 days ago 15 days ago Today
Operational Degraded Partial Outage
03

Performance Metrics (30 Days)

Metric P50 P95 P99
Bot Execution Latency (Whale Protocol) 112ms 187ms 298ms
Bot Execution Latency (Alpha Hunter) 341ms 478ms 612ms
Bot Execution Latency (Shadow Trader) 890ms 1.4s 1.8s
Exit Mirror™ Detection Latency 89ms 172ms 241ms
On-Chain Event Ingestion Lag 12ms 28ms 51ms
API Response Time (GET /portfolio) 38ms 87ms 142ms
API Response Time (GET /positions) 52ms 118ms 201ms
Dashboard Initial Load 610ms 980ms 1.3s
Webhook Delivery Latency 0.8s 2.1s 4.2s
Subscription Activation Time 18s 34s 52s
04

Incident History (Last 30 Days)

3 incidents recorded in the past 30 days. All incidents have been resolved. Downtime during these incidents totals approximately 4.3 hours, yielding a 30-day uptime of 99.4%.

Resolved Degraded execution latency — Whale Protocol accounts 9 days ago

Whale Protocol subscribers experienced elevated execution latency (250–410ms vs. the <200ms SLA) for approximately 2 hours 20 minutes. Caused by an RPC node pool exhaustion event following an unexpected spike in Polymarket block activity during a major election market resolution.

T+0:00Monitoring alert triggered — P95 execution latency exceeded 200ms threshold
T+0:08On-call engineer paged; incident declared
T+0:22Root cause identified: primary RPC node pool at capacity due to block activity spike
T+0:41Overflow node pool provisioned; latency beginning to recover
T+2:20All latency metrics returned to normal SLA. Incident resolved.
PostmortemPermanent overflow pool capacity increased 3x. Auto-scaling threshold lowered to prevent recurrence. Fix shipped in v2.4.1.
Resolved Partial service disruption — On-Chain Data Feed & Bot Execution 16–17 days ago

A database migration for the on-chain event archive caused a cascading disruption affecting both the data feed ingestion pipeline and bot execution for approximately 1 hour 40 minutes. During this window, new trade signals were not generated and copy trades were not executed. Existing open positions were not affected — positions that had already been entered remained live on-chain.

T+0:00Scheduled maintenance migration began; unforeseen lock contention triggered cascading failure
T+0:05Automated health checks detected data feed lag exceeding 30 seconds; incident declared
T+0:19Migration rolled back; database restored to pre-migration snapshot
T+1:40Full pipeline recovery confirmed. Event backlog processed. All bots resumed normal operation.
PostmortemFuture migrations will use online DDL operations with connection pooling. Zero-downtime migration protocol adopted as standard.
Degraded (Resolved) Elevated Ghost Wallet refresh failures — Whale Protocol accounts 23 days ago

The weekly Ghost Wallet Discovery™ scoring refresh silently failed for approximately 11% of Whale Protocol accounts due to a race condition in the scoring pipeline. Affected users received stale Ghost Wallet data for up to 7 days until the issue was detected during routine data quality checks. No copy trading functionality was interrupted. Fix shipped in v2.4.1.

T+0:00Race condition introduced during Ghost Wallet scorer v3 rollout
+6 daysData quality check detected staleness anomaly in 11% of Whale Protocol ghost wallet lists
+7 daysRoot cause identified; patch deployed; affected accounts' Ghost Wallet lists force-refreshed
PostmortemAutomated data freshness monitoring added to Ghost Wallet pipeline. Refresh retries with exponential backoff now standard.
05

Infrastructure Overview

Specula is built on a distributed, multi-region architecture designed for the sub-200ms execution latency requirements of professional Polymarket copy trading.

Execution Regions

  • Primary: US East (Virginia) — closest to major Ethereum RPC endpoints
  • Secondary: EU West (Frankfurt) — European user latency optimization
  • Failover: US West (Oregon) — activated during primary region incidents

RPC Node Infrastructure

  • Multi-provider RPC pool — no single point of failure for on-chain transaction submission
  • Auto-failover between providers with sub-second switchover time
  • Dedicated archive nodes for Ghost Wallet historical data analysis
  • 18,000+ on-chain events processed per second at steady state

Database & Storage

  • Primary database with synchronous replication to hot standby
  • Automated backups every 6 hours with 30-day retention
  • Event stream stored in append-only time-series store with sub-millisecond write latency

Monitoring & Alerting

  • All critical services monitored at 10-second intervals
  • On-call engineer paged within 5 minutes of any P1 degradation
  • Synthetic transaction probes execute real copy trade flows continuously in staging environment
  • Automated canary deployments with instant rollback capability
06

Stay Informed

Specula publishes all incidents, maintenance windows, and postmortems on this page in real time. To receive proactive notifications during incidents:

  • Telegram: Subscribe to @SpeculaStatus for push alerts on all P1 and P2 incidents (Whale Protocol subscribers only)
  • Webhook: Register a webhook for system.incident_created and system.incident_resolved events via the API
  • Email: Subscription expiry warnings are sent by email if you have provided an email address in your dashboard settings
  • This page: Always reflects current status within 60 seconds of any status change

For urgent issues during a confirmed incident, contact [email protected] with your wallet address. Whale Protocol subscribers receive priority incident support via their dedicated account manager.