Independent monitoring
GitHub status
OperationalMerlonix has monitored GitHub around the clock and recorded every status change we observed. Below is a 30-day timeline of those observations, followed by incident and maintenance details from the latest recorded snapshot.
Snapshot as observed by Merlonix at Oct 17, 2026, 08:31 AM UTC. This is a point-in-time snapshot, not real-time — see the live vendor board for the current minute-by-minute status.
30-day observation timeline
Each cell is one UTC day, coloured by the most severe status we observed that day. A “degraded” day reflects GitHub’s own published component-level status and may mean a single component was affected while the overall service was fine.
Observations recorded
48
distinct status changes over 28 days we have data for
Most recent change
Oct 12, 2026
last time the observed status changed
Days by observed status
- Operational16d
- Degraded11d
- Partial outage1d
What Merlonix monitors for GitHub
Merlonix polls GitHub's published status source around the clock and records every change we observe — overall status, component-level incidents, and their start/resolve times. The timeline and incidents below are Merlonix's own observations, sampled independently of GitHub.
Incidents and maintenance in the latest snapshot
Entries from GitHub’s latest recorded status snapshot may include active incidents, resolved notices or scheduled maintenance.
No incident or maintenance details are listed in this snapshot. Historical incident counts are available in the digest linked below.
For incident counts and recent examples across the historical window, read the 30-day vendor status digest. The digest has its own dated snapshot and counts scheduled maintenance separately.
Reduce alert noise during GitHub incidents.
When a monitored asset has GitHub listed as a dependency, Merlonix suppresses its alert notifications while the vendor reports degradation or an outage. The alert stays visible in your dashboard.
Other vendors we monitor