Platform status
A code review touches more than one platform. This page reads the live status pages of Baz Cloud and the six services a review depends on, and puts the last 90 days of each in one place.
Status
One row per upstream status page, reconstructed over the same 90 day window.
- Incidents
- 141
- Last checked
- Aug 8, 12:44 PM UTC
- Baz CloudBaz itself: the app, the API and the review workers.All services are online99.980%90 days agoToday
- GitHubWhere most Baz reviews are triggered: pull requests, webhooks and Actions.All Systems Operational96.06%90 days agoToday
- GitLabRepository hosting, merge requests and CI for teams on GitLab.Operational96.24%90 days agoToday
- Azure DevOpsAzure Repos, Pipelines and Boards for teams on Microsoft's stack.Everything is looking good98.18%90 days agoToday
- OpenAIModels behind Codex and the OpenAI-backed review paths.All Systems Operational94.26%90 days agoToday
- AnthropicClaude models behind Baz reviews and Claude Code.All Systems Operational96.69%90 days agoToday
- AWS BedrockManaged model inference behind Baz reviews running on AWS.No open AWS events affecting Bedrock100%90 days agoToday
Uptime history
Jul 10, 2026 to Aug 8, 2026
| Baz Cloud | 99.980% | |
|---|---|---|
| GitHub | 96.06% | |
| GitLab | 96.24% | |
| Azure DevOps | 98.18% | |
| OpenAI | 94.26% | |
| Anthropic | 96.69% | |
| AWS Bedrock | 100% |
Incident timeline
141 incidents across all tracked services in the last 90 days.
- MajorGitHubAug 6, 3:22 PM UTC11 h
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
- MinorGitHubAug 6, 3:03 PM UTC1.3 h
Incident with Pages - Deployment Lag
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
- MinorGitLabAug 6, 2:01 PM UTC2.4 h
Resolved - We're seeing consistent background job and webhook delivery. The issue is now resolved.
- MinorGitLabAug 5, 10:13 PM UTC1.6 h
Resolved - We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
- MinorOpenAIAug 5, 5:06 PM UTC3.2 h
Elevated errors in ChatGPT conversations with files
All impacted services have now fully recovered.
- MinorOpenAIAug 5, 4:55 PM UTC5.9 h
Issues with Custom GPT actions
All impacted services have now fully recovered.
How this is built
Every row is read live from the provider's own status page. Nothing here is a Baz measurement of a third party, and none of it is a service commitment.
- Baz Cloud
Baz's own Better Stack status page: live resource states and published uptime read from the page, incident windows from its RSS feed grouped by incident.
- GitHub
Atlassian Statuspage v2 API: live component states, history from the published incident feed and its tagged impact.
- GitLab
Status.io public status API for live component states, plus the page's incident RSS feed. Severity is inferred from the incident text, since Status.io does not publish a machine-readable impact per incident.
- Azure DevOps
Azure DevOps health API for live per-service and per-geography health, plus the recent events RSS feed. Incident windows come from the timestamps Microsoft prints in each update, and severity is inferred from the event title.
- OpenAI
Atlassian Statuspage v2 API: live component states, history from the published incident feed and its tagged impact.
- Anthropic
Atlassian Statuspage v2 API: live component states, history from the published incident feed and its tagged impact.
- AWS Bedrock
AWS Health public events feed for anything currently affecting Bedrock, plus the per-region Service Health Dashboard RSS feeds. Consecutive regional updates within six hours are merged into a single incident window.
Daily status is reconstructed from published incident windows: a day takes the worst impact of anything overlapping it, and uptime is one minus the union of the minor and major windows over the period. Announced maintenance colours a day but does not count against uptime. Providers that do not publish a machine-readable severity have theirs inferred from the incident text, so treat those rows as indicative. Refreshed every two minutes; the raw aggregate is available at /api/status.