Incident history

This page tracks endpoint reliability observed from the deployment platform to the upstream WAX and AtomicHub APIs over the last 24 hours. Back to status.

Waiting for samples? You can trigger one now.

Monitoring history is persisted. Uptime metrics survive across deployments.

Collection metadata

Uptime: 97.00%Samples: 100Incidents: 3

Worst stateStartedEndedDurationSamples

down

Nov 7, 2026 · 08:57 UTC

Nov 7, 2026 · 09:28 UTC

30m

down

Nov 6, 2026 · 13:32 UTC

Nov 6, 2026 · 14:03 UTC

31m

down

Nov 5, 2026 · 16:32 UTC

Nov 5, 2026 · 17:03 UTC

31m

down

Nov 4, 2026 · 20:03 UTC

Nov 4, 2026 · 20:33 UTC

30m

Live floor prices

Uptime: 42.00%Samples: 100Incidents: 21

Live cheapest listings

Uptime: 14.00%Samples: 100Incidents: 15

WAX/USD

Uptime: 100.00%Samples: 60Incidents: 0

Blockchain node

Uptime: 96.50%Samples: 200Incidents: 7

Roadmap chains

Ethereum

Planned · 0 users voted

View roadmap and vote →

Solana

Planned · 0 users voted

View roadmap and vote →

Catalogue builds

kogsofficialnot-started

0 templates · updated never

farmersworldnot-started

0 templates · updated never

alien.worldsnot-started

0 templates · updated never

Each observation runs when a visitor-facing page or the status API requests a sample. Health state is derived from HTTP status and response validity. Incidents are contiguous runs of non-ok observations. With no samples an endpoint's health is unknown, not verified. Uptime percent is the fraction of ok samples in the retention window. An endpoint needs at least 12 samples to have a reliable uptime claim.