api.github.com intermittently serves a self-signed api.glb certificate #204735
Unanswered
tidy-dev
asked this question in
Apps, API and Webhooks
Replies: 2 comments
|
Still recurring as of 2026-08-12 ~09:45 PDT. Confirming 172.182.252.137 is in the api.github.com DNS rotation from my location. My resolver cycles through 140.82.116.5, 140.82.116.6, 20.29.134.17, and 172.182.252.137. Direct openssl probes stayed clean across 13 consecutive samples, consistent with the ~8–12% figure. |
0 replies
|
Also seeing this on macOS via GitHub Desktop, home network (no VPN/proxy), intermittent ~1 in 10 syncs. Same CN api.glb / "Magic Provisioning / CI" self-signed cert. 2026-08-15 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Multiple users and GitHub clients—including GitHub Desktop and IntelliJ—are intermittently receiving a self-signed certificate from api.github.com instead of GitHub’s public certificate.
The certificate has CN api.glb, issuer/organization Magic Provisioning / CI, and identical validity dates but varying serial numbers. Repeated SNI probes isolated the behavior to 172.182.252.137, where roughly 8–12% of TLS handshakes returned the invalid certificate. Other api.github.com pool addresses tested cleanly. Clients correctly reject it; users report the issue across macOS and Windows.
Detailed reports: desktop/desktop#22702 and desktop/desktop#22709
All reactions