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 and any incidents GitHub reported.
Snapshot as observed by Merlonix at Jul 7, 2026, 06:58 PM 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
39
distinct status changes over 30 days we have data for
Most recent change
Jul 7, 2026
last time the observed status changed
Days by observed status
- Operational4d
- Degraded17d
- Partial outage9d
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.
Recent incidents GitHub reported
No incidents recorded from GitHub’s status source in the current observation window.
Get alerted the moment GitHub has a bad day.
Merlonix watches GitHub and your other upstreams around the clock and suppresses the false alerts they would otherwise trigger on your own sites — so you only get paged when the problem is actually yours.
Other vendors we monitor