System status
Recorded status for BrightPath’s development services.
A separate regional monitor records one check of BrightPath’s development services every five minutes. This page reads saved history.
Latest recorded check
Loading recorded status…
Loading the most recent recorded result.
Development backend
The separate data-service health probe used during development.
Development sign-in
The separate sign-in health probe used during development.
- Checks recorded
- —
- Coverage gaps
- —
- Monitoring since
- —
Recorded metrics
Status history and response time
Loading saved monitor history…
Published updates
Incident notices
No incident notices have been published.
Planned work
Planned maintenance
No maintenance is scheduled.
Scope and methodology
What this monitor covers
A Montréal-based monitor records one response from BrightPath’s anonymous, PHI-free development-status endpoint every five minutes and stores a rolling 90-day record. It does not check this website, the TestFlight app, or the production backend selected by current Release builds. A failed, stale, or malformed check is recorded as “Unable to verify,” not as confirmed downtime.
Page requests
Opening or refreshing this page reads saved history from BrightPath’s monitoring service. It does not run a health check or contact the monitored development services from your browser. Ordinary website request metadata may still be processed by the website host and the stored-history endpoint. No clinic, account, app, or health information is sent.
Reading the history
Five-minute samples cannot prove continuous availability between checks. Daily bars show the highest-severity recorded result for that UTC day. A partial-coverage bar also has missing scheduled checks, so its recorded results do not describe those gaps. Gaps in the response-time chart mean no valid measurement was recorded; they are never plotted as zero.