Platform status

• Baz CloudBaz itself: the app, the API and the review workers.

  All services are online99.40%
  90 days agoToday
  Show 5 components
• GitHubWhere most Baz reviews are triggered: pull requests, webhooks and Actions.

  All Systems Operational93.34%
  90 days agoToday
  Show 11 components
• GitLabRepository hosting, merge requests and CI for teams on GitLab.

  Operational96.38%
  90 days agoToday
  Show 23 components
• Azure DevOpsAzure Repos, Pipelines and Boards for teams on Microsoft's stack.

  Service maintenance is in effect87.13%
  90 days agoToday
  Show 7 components
• OpenAIModels behind Codex and the OpenAI-backed review paths.

  All Systems Operational92.74%
  90 days agoToday
  Show 25 components
• AnthropicClaude models behind Baz reviews and Claude Code.

  All Systems Operational85.56%
  90 days agoToday
  Show 6 components
• AWS BedrockManaged model inference behind Baz reviews running on AWS.

  No open AWS events affecting Bedrock100%
  90 days agoToday
  Show 6 components

• MajorAnthropicOct 24, 5:16 AM UTC37 min

  Elevated errors for Claude Fable 5 and Claude Fable 5.1

  The issue affecting Claude services has been resolved. Impact occurred from 22:00 PT on October 23 / 05:00 UTC on October 24 to 22:35 PT on October 23 / 05:35 UTC on October 24.

• MajorAnthropicOct 24, 12:31 AM UTC6 min

  Elevated errors for Claude Opus 5.5

  The issue affecting Claude Opus 5.5 has been resolved. Impact occurred from 17:23 PT on October 23 / 00:23 UTC on October 24 to 17:34 PT on October 23 / 00:34 UTC on October 24.

• MinorGitHubOct 23, 11:41 PM UTC42 min

  Grok 4.6 and Grok 4.7 Service Issues

  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.

• MajorAnthropicOct 23, 11:37 PM UTC34 min

  Elevated errors for Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5

  The issue affecting Claude models has been resolved. Impact occurred from 16:28 PT / 23:28 UTC on October 23 to 16:59 PT / 23:59 UTC on October 23.

• MinorOpenAIOct 23, 10:52 PM UTC50 min

  Degraded experience with ChatGPT app connections using CIMD

  All impacted services have now fully recovered.

• MinorGitLabOct 23, 4:32 PM UTC32 min

  General slowness on Gitlab.com

  Resolved - We have resolved the issue that caused slowness on GitLab.com. GitLab.com is operating normally, and we are continuing to monitor the platform. The impact may have included partial degradation to the web UI and Git operations.

• 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.