Source-led reliability analysis
What first-party incident history can and cannot show for 2026-06-01 through 2026-08-31
For the fixed 2026-06-01 through 2026-08-31 UTC window, Dropbox’s first-party API yielded an observed count of four resolved incidents; GitHub and Zoom did not expose sufficient retained history for full-window counts.
- Service
- GitHub, Dropbox, and Zoom
- Current state
- unknown
- Evidence confidence
- medium
- Primary source
- https://status.dropbox.com/api/v2/incidents.json
- Source observed
- Source updated
- Not provided by the primary source
- Published
- Record updated
Record details
The analysis window is fixed at 2026-06-01T00:00:00Z through 2026-08-31T23:59:59Z. It uses only first-party status pages and their official incident endpoints observed on 2026-09-25.
Dropbox’s official incidents endpoint retained records spanning before and after the full window. Applying the documented rule of state resolved with resolved_at inside that UTC window produced an observed first-party incident count of 4.
GitHub’s official incidents endpoint retained only 50 incidents, with its oldest created_at on 2026-07-24T11:00:00.000Z. Zoom’s endpoint likewise retained only 50 incidents, with its oldest created_at on 2026-07-18T07:17:57.000-07:00. Because neither response covered the full window beginning 2026-06-01, this analysis reports their full-window counts as unavailable rather than calculating partial-window counts.
Dropbox’s observed count of 4 is not uptime, availability, SLA performance, an impact measure, or a cross-provider reliability ranking. Different providers can publish, retain, classify, and scope incident records differently.
Sources
- Primary source: Dropbox Status official incidents API
- GitHub Status official incidents API
- Zoom Status official incidents API
- GitHub Status incident: Disruption with billing information updates
- GitHub Status
- Dropbox Status incident: Some customers are unable to access certain website routes and features
- Dropbox Status
- Zoom Status incident: Service Degradation Affecting Live Transcription Services
- Zoom Service Status
Known limitations
Incident counts are not uptime or SLA measures. Official pages may omit local, regional, account-specific, or unreported effects. GitHub and Zoom retained insufficient incident history for a complete count over the fixed window, and Dropbox’s count is only an observed first-party incident count rather than a comparison or ranking.