GitHub Enterprise Cloud (core) degraded Jun 15, 2026: SLA credit impact
Check your eligibility — use the checklist yourself or optionally request a free review from AllCaps Technologies.
What happened
Increased latency with webhooks — resolved.
Started Jun 15, 2026 15:37 UTC. Duration: 2h 0m.
Affected: Enterprise Cloud (core).
This month's ledger effect
The numbers below are month-to-date for the services this incident touched. A tier can already be open from other outages earlier in the month; this incident's own contribution is listed in the last column.
| Service | Region | Uptime | Month downtime | This incident | Status this month |
|---|---|---|---|---|---|
| Enterprise Cloud (core) | all regions | — | — | status incident only; not counted as SLA downtime | eligibility not established — customer contract and telemetry required |
Eligibility is not established by the public status incident. Use the self-service checklist to compare your plan, configuration and telemetry, or optionally request a free review from AllCaps Technologies on the eligibility page. Public incident duration is not counted as contractual customer downtime.
GitHub's SLA is measured per calendar quarter per Service Feature using GitHub's own monitoring; a public status incident does not establish the quarterly uptime figure, and credits attach to paid Enterprise Cloud, Actions and Packages fees.
Contract references: GitHub Online Services SLA
Preserve possible eligibility: open a Cloudflare support case promptly. Some standard terms require notice within five business days, but the exact notice and claim deadlines depend on the affected product and the customer's negotiated contract. No deadline is calculated here until those are validated.
Share
GitHub Enterprise Cloud (core): Increased latency with webhooks Duration: 2h 0m. Enterprise Cloud (core): SLA eligibility requires customer contract and telemetry validation https://slacreditwatch.com/i/github/67w72l5v25x3
GitHub Enterprise Cloud (core): Increased latency with webhooks. Duration: 2h 0m. Enterprise Cloud (core): SLA eligibility requires customer contract and telemetry validation. https://slacreditwatch.com/i/github/67w72l5v25x3
Calculator
No credit estimate is produced from this public incident. Use the applicable product fees, qualifying customer-observed outage period, affected-customer ratio, and the SLA in the customer's contract.
Get outage alerts
When a selected vendor reports a relevant outage, we tell you what evidence to preserve and help you check eligibility. Use the checklist yourself, or optionally request a free review from AllCaps Technologies on the incident's eligibility page. Confirmed contractual alerts include the credit math and filing deadline.
Choose vendors, add your email, and confirm once. No spend or contract details required.