Uptime, component health, recent incidents, recovery timing, and support paths.
Platform uptime
99.94%
Rolling uptime across Attnom World, Solutions, Prism, and Workspace.
Median acknowledgement
7 min
Time to post a customer-facing note once a public platform issue is confirmed.
Last visible incident
12 days ago
The most recent issue that affected what customers could see or use.
Median recovery
41 min
Typical time from confirmation to recovery update for customer-visible disruptions.
Component health
Each area below maps to a part of Attnom so users can tell whether the website, delivery, Prism research, Workspace, or support is affected.
Root page, product selector, command ribbon
The Attnom home page and product previews are loading normally.
Programs, pricing, labs, payments, Workspace
Commercial discovery, payments, and delivery follow-up remain available.
Markets, token rooms, wallets, graph, alerts, research
Prism market and research pages are serving normally.
Auth, dashboard, workspace notices, account continuity
Account access and Workspace follow-through remain available.
Status, help desk, contact, escalation
Support remains visible without exposing private access.
Deposits, receipts, privacy, terms, billing references
Manual review remains active around payment verification and policy-linked record handling.
Incident history
Select an incident to inspect what users saw, how recovery unfolded, and which service areas needed an update.
Historical incident replay
Recovery time
22 min
The home page briefly showed outdated page counts because an older result remained cached.
Impact note
Selector previews lagged behind current product copy.
Impact note
Direct entry into Solutions and Prism remained available.
Impact note
Guidance was corrected without downtime to deeper product pages.
Recovery chronology
Detect
Review flagged stale proof text during public verification.
Confirm
Shared cache retained an older metadata payload for the root selector.
Recover
We cleared the stale gateway cache and rebuilt it against the current services.
Close
Status note updated once selector previews matched the live pages.
Affected areas
Platform entry
Root selector copy and product previews recovered first because they shape initial user trust.
Status page
Public notice remained available so users could verify readiness while the preview state was corrected.
Next steps
Best next step
Use Workspace and Solutions when the issue touches quotes, deposits, delivery, or project records.
Best next step
Use Prism and contact first when the question involves markets, tokens, wallet signals, graph context, or research confidence.
Best next step
Use contact when the issue crosses products or needs a direct human reply.
Operating model
Public status is updated when customer-facing behavior changes across Attnom World, Solutions, Prism, or Workspace.
Each incident entry includes the affected service area and the time to recovery so trust does not depend on vague reassurance.
The right next step is visible before anyone opens manual support or private review.
Escalation
Use direct contact for issues across products, or open Prism if the issue is market-, token-, wallet-, graph-, or research-specific.