G2 Best Software 2026, Fastest GrowingSee the list
official source · developer scope

Is GitHub down right now?

GitHub Status currently reports the selected GitHub components as operational.

GitHub Statusofficial 90-day view
Current provider state
All selected systems operational
Operational

Uptime over the past 90 days, as published by the provider.

View official history ↗
Git OperationsOperational
90 days ago99.99% uptimeToday
WebhooksOperational
90 days ago100% uptimeToday
API RequestsOperational
90 days ago99.91% uptimeToday
Pull RequestsOperational
90 days ago99.98% uptimeToday
ActionsOperational
90 days ago99.42% uptimeToday
PackagesOperational
90 days ago100% uptimeToday
Scope
Git operations, APIs, webhooks, pull requests, Actions, and Packages
Source updated
Checked by Qodex
Public provider history, cached for up to five minutes. Published uptime is used when available; otherwise bars show matching incidents in the provider feed. This is not a Qodex availability measurement. Account-specific health may differ.

This page reads the official GitHub components most likely to affect software delivery. It does not test your repository permissions, workflow configuration, runner, webhook receiver, or deployment.

Qodex does not operate GitHub. Source: GitHub Status.

GitHub is operational. Is your workflow?

An official status page answers whether the provider sees a broad service problem. It does not execute the request, repository, or browser journey your product depends on.

What Qodex verifies nextprovider green ≠ workflow green
01

Region and service

Match the failing request to its exact service, region, edge location, and account-specific health view.

02

Credentials

Verify token expiry, scopes, role assumptions, and the identity used by the deployed environment.

03

Request and response

Capture the real endpoint, status code, headers, latency, and response body from the failing path.

04

Dependent flow

Replay the application journey that depends on the platform and assert the user-visible result.

Official components and incidents

Scope matters. The rows below come from GitHub Status and are filtered to GitHub developer services. They are evidence from the provider, not synthetic Qodex probes.

Official incident feed0 shown

No matching incident is active in the GitHub source data returned for this render.

Troubleshoot GitHub without guessing

Start with the provider state, then move inward through your account, request, application, and final user journey.

Diagnostic sequence4 checks
SignalWhat to verify
Region and serviceMatch the failing request to its exact service, region, edge location, and account-specific health view.
CredentialsVerify token expiry, scopes, role assumptions, and the identity used by the deployed environment.
Request and responseCapture the real endpoint, status code, headers, latency, and response body from the failing path.
Dependent flowReplay the application journey that depends on the platform and assert the user-visible result.

GitHub status FAQ

Is GitHub down right now?

The status above is rendered from GitHub Status and scoped to Git operations, APIs, webhooks, pull requests, Actions, and Packages. If the official source is unavailable, Qodex reports the status as unavailable instead of guessing.

Why can GitHub be operational while my integration is failing?

Provider dashboards report aggregate platform health. Your account, credentials, model access, region, request contract, SDK, repository, browser session, or downstream application flow can still fail independently.

Does Qodex monitor or operate GitHub?

No. GitHub is operated by its provider. Qodex renders the provider’s public status data here and helps engineering teams test the API and UI workflows that depend on it.

What should I test after the provider status is green?

Replay the real request and user journey with the same environment, credentials, payload, and assertions used in production. Check the response contract and the final user-visible result, not only connectivity.

from status to proof

Provider green is the start of diagnosis.

Qodex tests the API and UI path your team actually ships, then keeps the evidence with the failure.

Test the workflow