●Incident
GitHub Meta outage.
ResolvedDEGRADATION · HIGHNov 7, 2026, 02:21 AM · 6 days ago · Duration: 14min
Incident Summary
Incident Summary
API GitHub Meta is currently DOWN in europe.
Diagnostic Details
Error Type: http HTTP Status: 504 Error Message: API returned HTTP 504 Retry Attempts: 1 (all failed)
Validation Results
Validation Reason: DOWN only in europe - possible regional issue Consecutive DOWN Checks: 2 Time Between Checks: 272s
Regional Analysis
Status: DOWN only in europe (possible regional issue) Other Regions: us-east: degraded
Severity Assessment
Level: MEDIUM Limited regional impact or recoverable error type.
Detected by Probecast Health Monitor - 2026-11-07T02:21:59.697Z
Timeline
●Started
Nov 7, 2026, 02:21 AM
6 days ago
●Resolved
Nov 7, 2026, 02:36 AM
6 days ago
●Duration
14min
Total downtime
Evidence Logs7 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Nov 7, 02:21 AM | europe | down | 10ms | 504 |
| Nov 7, 02:20 AM | us-east | degraded | 9924ms | 200 |
| Nov 7, 02:17 AM | europe | down | 28ms | 504 |
How many of your clients depend on GitHub Actions?
When GitHub Actions slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.
One provider breaks. See every client it touches.
Ordered by how many clients it hits, so you message the right people first.
Each client's site and store, checked from up to four regions.
US West & East, Europe and Asia — a regional outage never hides.
A monthly report under your brand, reviewed by your team before it goes out.
Uptime, incidents, traffic, revenue and support — signed off by a person.
Your team scoped per client. Every change on the record.
Freelancers see only their clients; every change lands in an append-only audit log.
Alerts land on email, Slack, push or webhooks — with the client's name on them.