AttnomSolutions
Loading page
Bringing in the next surface without the heavy transition shell.
Loading page
Bringing in the next surface without the heavy transition shell.
Uptime, component health, recent incidents, recovery timing, and support routing.
Platform uptime
99.94%
Rolling uptime across platform entry, route trust surfaces, and shared workspace continuity.
Median acknowledgement
7 min
Time to post a customer-facing note once a public or exchange issue is confirmed.
Last visible incident
12 days ago
Most recent issue that changed customer-facing behavior across the shared front door.
Median recovery
41 min
Typical time from confirmation to recovery update for customer-visible disruptions.
Component health
Each lane below maps to a part of the product family so users can tell whether the gateway, delivery, exchange trust, workspace, or operator surfaces are affected.
Root route, route selector, command ribbon
The shared front door and its route previews are loading normally.
Programs, pricing, labs, payments, workspace handoff
Commercial discovery and delivery continuity remain available.
Markets, onboarding, wallets, tax, security, support
Trust-critical exchange routes are serving normally.
Auth, dashboard, workspace notices, account continuity
Shared account access and workspace follow-through remain available.
Status, help desk, contact, admin entry
Support routing and escalation entry remain visible near product entry.
Deposits, receipts, privacy, terms, billing references
Manual review remains active around payment verification and policy-linked record handling.
Status theater
Select an incident to inspect what users saw, how recovery unfolded, and which service lanes needed the trust update.
Historical incident replay
Recovery time
22 min
The new platform-entry surface briefly showed outdated route counts while the shared gateway cache still held the prior command state.
Impact note
Selector previews lagged behind current route copy.
Impact note
Direct entry into Solutions and Exchange remained available.
Impact note
Trust messaging was corrected without downtime to deeper routes.
Recovery chronology
Detect
Operator review flagged stale proof text during public route verification.
Confirm
Shared cache retained an older route metadata payload for the root selector.
Recover
Gateway cache was cleared and rebuilt against the current route command deck.
Close
Status note updated once selector previews matched the live pages.
Service-lane drilldowns
Platform entry
Root selector copy and route previews recovered first because they shape initial user trust.
Status lane
Public notice remained available so users could verify service readiness while the preview state was corrected.
Routing next steps
Best route
Use the workspace and solutions continuity routes when the issue touches quotes, deposits, delivery, or project records.
Best route
Use the exchange help and status family first when the question involves onboarding, security, wallets, or market-entry trust.
Best route
Use contact when the issue crosses routes or needs a direct human reply rather than a route-specific handoff.
Best route
Use the admin entry point when the issue belongs to platform operations, queues, or privileged recovery.
Operating model
Public status is updated when customer-facing behavior changes across the gateway, Solutions, Exchange, or workspace continuity surfaces.
Each incident entry includes the affected service lane and the time to recovery so trust does not depend on vague reassurance.
The right route should be obvious from this page before anyone opens manual support or operator review.
Escalation lane
Use direct contact for cross-route issues, or step into exchange help if the issue is trust-, security-, or market-lane specific.