Skip to main content

ArmorList status

Live health of this site's public surfaces, checked from your browser. Components behind sign-in or on the application surface are reported as not monitored until a monitoring provider is connected, never shown healthy on no evidence.

ComponentsChecked from your browser
Public site
Marketing, legal, trust, and knowledge pages
Checking
Feeds & discovery
The sitemap search engines and agents read
Checking
Catalog & product records
Companies, products, and materials in the directory
Not monitored

The directory is served by security-definer RPCs read server-side, not by a public file a browser can request. Needs a provider-side check.

Search
Full-text and faceted search
Not monitored

Search runs on the application surface. Needs a provider-side synthetic query.

Verification pipeline
NIJ CPL, SAM.gov, CAGE, and UEI sync
Not monitored

Sync health is known to the pipeline, not to a browser. Needs a provider health endpoint.

Authentication & accounts
Sign-in, MFA, SSO
Not monitored

Requires a provider-side login probe. Cannot be measured from a browser without an account.

API & integrations
Partner data sources
Not monitored

Integration health comes from the services involved, not from this site.

ArmorTrack bridge
Replacement and push-to-inventory handoff
Not monitored

The handoff spans two authenticated platforms. Needs a provider-side end-to-end check.

Past incidentsPublished by the monitor

No monitoring provider is connected yet, so no incident history is published rather than an invented all-clear.

Availability commitmentQuoted from the SLA

We target 99.9% monthly uptime: monthly uptime for the production platform for paid supplier subscriptions, excluding excluded downtime. Support response targets, from the Service Level Agreement:

S1, criticalProduction down or a major function unusable4 business hours
S2, highSignificant impairment, no workaround1 business day
S3, normalMinor issue or question2 business days
Subscribe to status updates

Get an email whenever a component's status changes.

The monitoring contractJSON

History appears when a monitoring provider writes the machine-readable status document (monitoring provider (synthetic checks), written on every check interval). The fields it must supply:

monitor.connectedbooleanFalse until a provider is wired. Fail-closed: the page shows no history while false.
monitor.providerstringName of the provider, shown so the reader knows who measures this.
components[].idstringMust match an id in the component list. Unknown ids are ignored, not rendered.
components[].stateenumoperational | degraded | partial-outage | major-outage | maintenance | unknown
components[].uptime90number|nullPercentage over the trailing 90 days. Null renders as no data, never as 100.
incidents[]arrayPublished incidents: { id, title, started, resolved, impact, components[], updates[] }.
maintenance[]arrayAnnounced windows: { id, title, start, end, components[], detail }.

Operational transparency is part of the Trust Center. For historical uptime or an incident post-mortem, contact support.