Platform status

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

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

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

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

  Everything is looking good98.08%
  90 days agoToday
  Show 7 components
• OpenAIModels behind Codex and the OpenAI-backed review paths.

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

  All Systems Operational75.29%
  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

• MinorOpenAIJul 25, 10:09 PM UTCOngoing

  Elevated errors affecting ChatGPT conversations

  Mitigation has been implemented, and we are monitoring the recovery of ChatGPT conversations.

• MajorAnthropicJul 25, 9:34 PM UTC34 min

  Elevated errors for Claude Fable 5, Claude Sonnet 5, Claude Haiku 4.5, and other models

  This incident has been resolved.

• MajorAnthropicJul 25, 6:40 PM UTC1.1 h

  Elevated errors for Mythos 5, Fable 5, Opus 5 and Claude Haiku 4.5

  This incident has been resolved.

• MajorGitHubJul 25, 12:31 PM UTC42 min

  Actions run failures and delays

  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.

• MinorOpenAIJul 25, 11:35 AM UTC22 min

  Elevated error rates

  All impacted services have now fully recovered.

• MajorGitHubJul 25, 9:42 AM UTC29 min

  Several GPT models degraded

  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.

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