Follow the recent outages and downtime for GitHub Codespaces in the table below.
Start Time |
Type |
Length |
Message |
Details |
|||||
---|---|---|---|---|---|---|---|---|---|
March 29, 2023 18:21 UTC |
WARN |
ongoing |
Incident with Actions, Codespaces and Pages |
See more
|
|||||
March 29, 2023 17:31 UTC |
WARN |
about 1 hour |
Incident with Actions, Codespaces and Pages |
See more
|
|||||
March 27, 2023 13:26 UTC |
WARN |
5 minutes |
Incident with Actions, API Requests, Codespaces, Git Operations, Issues, Pages and Pull Requests |
See more
|
|||||
March 27, 2023 12:52 UTC |
DOWN |
35 minutes |
Incident with Actions, API Requests, Codespaces, Git Operations, Issues, Pages and Pull Requests |
See more
|
|||||
March 27, 2023 12:36 UTC |
WARN |
15 minutes |
Incident with Actions, API Requests, Codespaces, Git Operations, Issues and Pull Requests |
See more
|
|||||
2023-04-01 07:06:42 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2023-04-01 07:06:42 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2023-04-01 07:06:42 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2023-04-01 07:06:42 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more | |||||
2023-04-01 07:06:42 UTC UTC |
STATUS |
? minutes |
Sign in to view more status history. |
See more |
Sign Up for More GitHub Codespaces History
StatusGator has about 8 years of GitHub Codespaces status history.
GitHub Codespaces status, last 24 hours:
Up: 24 hours
Warn: 0 minutes
Down: 0 minutes
Maintenance: 0 minutes
GitHub Issues is a DevOps solution that StatusGator has been monitoring since March 2015. Over the past about 8 years, we have collected data on on more than 1,473 outages that affected GitHub Issues users. When GitHub Issues publishes downtime on their status page, they do so across 11 components using 4 different statuses: up, warn, down, and maintenance which we use to provide granular uptime metrics and notifications.
More than 2,200 StatusGator users monitor GitHub Issues to get notified when it's down, is under maintenance, or has an outage. This makes it one of the most popular devops services monitored on our platform. We've sent more than 501,900 notifications to our users about GitHub Issues incidents, providing transparency and peace of mind. You can get alerts by signing up for a free StatusGator account.
If GitHub Issues is having system outages or experiencing other critical issues, red down notifications appear on the status page. In most cases, it means that core functions are not working properly, or there is some other serious customer-impacting event underway.
Warn notifications are used when GitHub Issues is undergoing a non-critical issue like minor service issues, performance degradation, non-core bugs, capacity issues, or problems affecting a small number of users.
GitHub Issues posts separate notifications for planned maintenance work. StatusGator will notify subscribers when GitHub Issues enters a pre-planned maintenance window, keeping you up to date.
Since GitHub Issues publishes a feed of proactive maintenance events on their status page, StatusGator will collect information about these events. Maintenance events for all your services can be viewed within StatusGator as a unified feed.
When GitHub Issues posts issues on their status page, we collect the main headline message and include that brief information or overview in notifications to StatusGator subscribers.
When GitHub Issues has outages or other service-impacting events on their status page, we pull down the detailed informational updates and include them in notifications. These messages often include the current details about how the problem is being mitigated, or when the next update will occur.
Because GitHub Issues has several components, each with their individual statuses, StatusGator can differentiate the status of each component in our notifications to you. This means, you can filter your status page notifications based on the services, regions, or components you utilize. This is an essential feature for complex services with many components or services spread out across many regions.
Frequently Asked Questions
According to its status page GitHub Issues is currently up. You can check the most recent events in the 'Recent Outages and Issues' section above.
StatusGator can send you instant alerts by email, SMS, Slack, and more. Sign up now, it's free!
There are two main options: You can check the GitHub Issues status page or you can subscribe to StatusGator for free alerts and notifications when their status page changes.
There may be several reasons for that:
We recommend contacting GitHub Issues customer support while checking everything on your side. You can also try Tweeting at them via @github on Twitter. Or visit their official status page or website:
We use the official GitHub Issues status page. Here are links to their status page and other helpful links.
Are you experiencing issues with GitHub Issues? Sign up to receive notifications when GitHub Issues publishes outages.
GitHub Issues Down or not working? Never be taken by surprise again.
StatusGator tells you when your cloud services have problems or their statuses change. We monitor the official status pages of more than 2,700 cloud services in real-time, aggregate the data, and send you alerts via email, Slack, Teams, SMS, and more.
Looking for recent downtime and outages of GitHub Issues?
Sign up for StatusGator and see all historical information about GitHub Issues outages and performance issues. Get free, instant notifications when GitHub Issues goes down.