Monitor GitHub and all cloud services with IsDown

IsDown fetches data from GitHub status page to monitor any minor and major outages. Every 5 minutes, we check the status page for any outages and updates.

IsDown also collects reports from users when they experience an outage. We use this information to provide early indicators of outages.

IsDown monitors GitHub for downtimes and major outages. A major outage is when GitHub experiences a critical issue that severely affects one or more services/regions.

IsDown monitors GitHub status page for minor outages. A minor outage is when GitHub experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application.

IsDown collects all information from the outages published in GitHub status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

GitHub publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.

IsDown monitors GitHub and all their 11 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages.

GitHub and other vendors don’t always report outages when they happen. Our crowdsourced status helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages.