Enablement® Service Availability

Availability Report · Advent Business Company Inc. · FedRAMP ID FR2628647239 · package id ADVENTBUSINESS-ENB · CDS-CSO-AVR · all times UTC · generated 2026-09-21T07:13:49Z · machine-readable JSON · certification package

Current status

OPERATIONAL

Most recent probe of every measured endpoint succeeded. Last probe 2026-09-21T07:10:02Z (3.8 minutes ago). State code operational.

EndpointLast probeResult HTTP
Public edge public2026-09-21T07:10:02Zreachable200
Application tier internal2026-09-21T07:10:02Zreachable200

Last 30 days (2026-08-22T07:13:49Z → 2026-09-21T07:13:49Z)

Uptime (of probes taken)99.071%
Uptime (lower bound, of probes expected)98.744%
Probes17062 successful of 17222 taken
History available30.0 days (first probe 2026-08-22T07:15:02Z) — meets the 30-day requirement
Measurement coverage99.67% of expected probes were actually recorded within that span (17279 expected at the 5-minute cadence)
Coverage of the full 30-day window99.664% of the 17280 probes a complete window would contain.
fullWindowCoveragePercent answers 'does the history reach back the full 30 days the rule requires'. measuredSpanCoveragePercent answers 'within the period the collector has been running, did it actually take every probe it should have'. A shortfall in the second is missing measurement, published as measurement-gap incidents, and is never counted as uptime.
Availability incidents0
Measurement gaps2

uptimePercentOfObservedProbes = successful probes / probes actually taken. uptimePercentOfExpectedProbes = successful probes / probes that should have been taken over the measured span, i.e. a LOWER BOUND that treats an unrecorded probe as not-known-good. Read the lower bound as the conservative figure.

EndpointWhat it probesProbes SuccessfulUptimeMedian latency Last probe
Public edge publicHTTPS front door at https://enablement.cc/ — the path every customer and agency user takes.8611852799.025%32 ms2026-09-21T07:10:02Z
Application tier internalTomcat probed directly on the host, bypassing the edge — separates an edge failure from an app failure.8611853599.117%1 ms2026-09-21T07:10:02Z

Availability incidents and measurement gaps

TypeFromToDuration AffectedDetail
Measurement gap
measurement-gap		2026-09-20T11:05:01Z2026-09-20T13:25:02Z140.0 minPublic edge publicavailability unknown
No probe result exists for this period, so availability during it is unknown. It is NOT counted as uptime. A gap means the collector, the host, or the database was unavailable to record a result.
Measurement gap
measurement-gap		2026-09-20T08:15:02Z2026-09-20T13:24:18Z309.3 minApplication tier internalavailability unknown
No probe result exists for this period, so availability during it is unknown. It is NOT counted as uptime. A gap means the collector, the host, or the database was unavailable to record a result.

An availability incident is 2 or more consecutive failed probes on an endpoint (the shortest outage a 5-minute cadence can resolve), merged across endpoints when the failure windows overlap. A single isolated failed probe appears in the daily rollup but is not promoted to an incident.

Daily availability

Date (UTC)UptimeProbes OK / taken Per endpointCoverageUptime lower bound
2026-09-2199.425%173 / 174internal 87/87; public 86/87100.0%
of 172 expected		100.581%
2026-09-2099.808%521 / 522internal 261/261; public 260/26190.625%
of 576 expected		90.451%
2026-09-1998.958%570 / 576internal 285/288; public 285/288100.0%
of 576 expected		98.958%
2026-09-18100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-17100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-1699.306%572 / 576internal 286/288; public 286/288100.0%
of 576 expected		99.306%
2026-09-1597.569%562 / 576internal 281/288; public 281/288100.0%
of 576 expected		97.569%
2026-09-1499.653%574 / 576internal 287/288; public 287/288100.0%
of 576 expected		99.653%
2026-09-13100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-12100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-11100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-10100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-09100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-09-0899.653%574 / 576internal 287/288; public 287/288100.0%
of 576 expected		99.653%
2026-09-0799.653%574 / 576internal 287/288; public 287/288100.0%
of 576 expected		99.653%
2026-09-0698.958%570 / 576internal 285/288; public 285/288100.0%
of 576 expected		98.958%
2026-09-0597.222%560 / 576internal 281/288; public 279/288100.0%
of 576 expected		97.222%
2026-09-0497.222%560 / 576internal 280/288; public 280/288100.0%
of 576 expected		97.222%
2026-09-0399.303%570 / 574internal 285/287; public 285/28799.653%
of 576 expected		98.958%
2026-09-0298.264%566 / 576internal 283/288; public 283/288100.0%
of 576 expected		98.264%
2026-09-0199.129%569 / 574internal 285/287; public 284/28799.653%
of 576 expected		98.785%
2026-08-3198.611%568 / 576internal 284/288; public 284/288100.0%
of 576 expected		98.611%
2026-08-30100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-08-29100.0%576 / 576internal 288/288; public 288/288100.0%
of 576 expected		100.0%
2026-08-2898.611%568 / 576internal 284/288; public 284/288100.0%
of 576 expected		98.611%
2026-08-2798.785%569 / 576internal 285/288; public 284/288100.0%
of 576 expected		98.785%
2026-08-2697.222%560 / 576internal 280/288; public 280/288100.0%
of 576 expected		97.222%
2026-08-2597.396%561 / 576internal 281/288; public 280/288100.0%
of 576 expected		97.396%
2026-08-2499.132%571 / 576internal 286/288; public 285/288100.0%
of 576 expected		99.132%
2026-08-2399.653%574 / 576internal 287/288; public 287/288100.0%
of 576 expected		99.653%
2026-08-2297.512%392 / 402internal 196/201; public 196/201100.0%
of 400 expected		98.0%

What this measures

What it does not measure

A scheduled probe on the production host, every 5 minutes, recording each result in the platform's availability history, which keeps 90 days.

If this page will not load — the off-CSO mirror

https://trust.enablement.cc
Bookmark it now, because during an outage you cannot reach this page to find it. Live external observation: https://trust.enablement.cc/mirror-availability.json · mirrored copy of this document: https://trust.enablement.cc/availability.json

A point-in-time copy of every PUBLIC trust-center artifact, refreshed every 15 minutes by a scheduled job running OUTSIDE this offering, in the AWS commercial partition (a separate account, us-east-1), served from S3 through CloudFront. It shares no partition, account, region, host, database, web server, TLS certificate or DNS zone with production.

Two different things, and the difference matters. (1) The mirrored copy of THIS document is last-known-good: it is stamped with the time it was taken and will not contain the outage in progress. (2) mirror-availability.json is LIVE during the outage — the refresher is itself an external probe, so when it cannot reach this offering it publishes that fact, with a first-failure time and a running duration, from infrastructure the outage does not touch. That second document is the one this on-host service structurally cannot produce.

https://trust.enablement.cc/mirror-manifest.json carries a mirroredAt timestamp and a SHA-256 per artifact, and each stored object repeats it in an x-amz-meta-mirrored-at header. An age far past 15 minutes while the mirror reports this offering reachable means the refresher itself has stopped; that condition is alarmed by the same freshness worker that watches the rest of the evidence pipeline, so a silently frozen mirror is not left to be noticed by a reader. Only artifacts that are already public without authentication. No token-gated certification data is mirrored — not the evidence index, the package documents, nor the SDR, KSI, VDR, AVI, OCR, historical, assessor or query services. A static bucket has no token gate, so the copy list is an explicit allow-list of nine object keys and the storage policy grants read on exactly those object ARNs with no wildcard.

Limitations — read this

This report cannot report an outage it is part of.
This is a self-hosted availability report. The probe collector, the database it writes to, and the service that renders this document all run on the same production host in AWS GovCloud us-gov-east-1 as the offering being measured. It is not an independent, off-CSO status service.

Because this endpoint is served by the same application tier it reports on, it is unreachable during precisely the outages it exists to report. Treat a failure to reach this endpoint as itself an availability signal — the most severe one it can give you — and then read the off-CSO mirror at https://trust.enablement.cc/mirror-availability.json, which is written from outside this infrastructure and stays up when this endpoint does not.
2026-07-20 production outage — the known instance.
A ~23-hour HTTP 502 took the entire enablement.cc origin down, trust center included. The probe recorded it: 247 consecutive failed probes per endpoint on 2026-07-20 and a further 27-28 on 2026-07-21. The data is therefore honest about the outage — but had this endpoint existed at the time, it could not have served that fact while it was true, because it was down with everything else. That is the limitation above, demonstrated rather than asserted.

The event is separately recorded in Advent's incident record and is not knowable only from this endpoint.
Missing measurement is not uptimeA failed probe is positive evidence of an outage. An absent probe is NOT evidence of uptime. Missing measurement is published as measurement-gap incidents with availability 'unknown' and is excluded from the uptime numerator and denominator alike.
Not independently attestedProvider-generated. No third party attests these figures. An agency requiring independent availability evidence should operate its own external probe against https://enablement.cc/ and compare.

CDS-CSO-AVR compliance, arm by arm

RequirementStatusBasis
maintain a web service indicating current and historical availabilityMET metThis endpoint plus the human-readable page at https://enablement.cc/ml/20x/status.
core services, over at least the past 30 daysMET metAt least 30 days of continuous probe history is available.
including availability incidentsMET metIncidents are derived from the probe series and published in the incidents array; measurement gaps are published separately as unknown periods.
in both human-readable and machine-readable formatsMET metJSON at https://enablement.cc/ml/20x/availability and HTML at https://enablement.cc/ml/20x/status, both rendered from this same document.
available to all necessary partiesMET metBoth formats are public and unauthenticated; no token is required.
MUST be available even if the primary cloud service offering is unavailableMET metSatisfied by the off-CSO mirror at https://trust.enablement.cc — see limitations.offCsoMirror. THIS endpoint still shares a host, a database and an origin with the offering and still disappears with it; that has not changed and is not being claimed otherwise. What closes the arm is that the report no longer exists only here: a copy is refreshed every 15 minutes into the AWS commercial partition (a separate account, us-east-1) and served from S3 via CloudFront, sharing no partition, account, region, host, database, web server, TLS certificate or DNS zone with production. Verified by loading every mirrored artifact in a browser with all network access to enablement.cc refused. The qualification, stated rather than buried: the mirrored copy of this document is last-known-good and will lag an outage in progress, while the companion mirror-availability.json is live during one, because the refresher is an external probe and publishes its own failure to reach this offering.

Overall: MET (met). Every content, format, access and independent-hosting arm of CDS-CSO-AVR is satisfied. The 30-day window is complete.