GitHub outage records
Read official GitHub outage and maintenance notices and daily records.
Ongoing now
- Status
- Operational
- Last checked
- Last outage
- Oct 30
All sources operational · 1 sources ·
Last 90 days
- Outage
- 6 entries
- Outage duration
- About 8 hours 30 minutes (3 incidents with unknown duration)
- Maintenance
- 0 entries
- Days with outages
- Day 6
- Average outage duration
- About 2 hours 50 minutes (3 incidents with unknown duration)
- Longest outage duration
- About 5 hours 32 minutes (3 incidents with unknown duration)
Outages by weekday
Daily records
Aug 6 – Nov 3
Events
Monthly records
About GitHub records
These records collect incident and recovery notices for GitHub development services such as repositories and Actions. New notices come from GitHub’s official status page. Notices are grouped by outage, delay, maintenance and recovery wording in their titles and descriptions, with the original times shown. When no time is given, older notices show no time, while newly found notices show the first check time marked observed. Check the original notice for the precise impact on the services you use.
Source: GitHub
About these records
Where do these records come from?
We check each company’s own official incident notices every 10–15 minutes.
What do outage, degraded and maintenance mean?
We use the words in the original notice: outage means an interruption, degraded means reduced service, and maintenance means planned work.
How is outage time counted?
We add time only when both the start and recovery times are known. Otherwise, we show duration unknown.
Which time zone is used?
All dates and times are shown in Japan Standard Time (JST).