based on user reports and queries over the last 24 hours
GitHub outage statistics
During last hour where are reports about GitHub not working in regions:
Operating systems of devices, from which fault reports are arriving:
Fault reports are arriving from the networks of this telecom providers:
* for the last hour
- Help Center at https://docs.github.com;
- Submit ticket at https://support.github.com;
- Community forum at https://github.community;
- X (Twitter) @githubstatus for status;
- Contact support (paid plans);
- Status page: https://www.githubstatus.com.
- Official Website - https://github.com;
- X (Twitter) - https://twitter.com/github;
- Status - https://www.githubstatus.com;
- Blog - https://github.blog;
- YouTube - https://www.youtube.com/github;
- LinkedIn - https://www.linkedin.com/company/github;
- Docs - https://docs.github.com;
- Community - https://github.community;
- Changelog - https://github.blog/changelog;
- Facebook - https://www.facebook.com/GitHub.
Service disruptions manifest as GitHub not loading, repositories inaccessible, dashboard blank, login errors, or complete platform unavailable.
- Check GitHub status at https://www.githubstatus.com;
- Refresh browser page completely;
- Verify stable internet connection;
- Clear browser cache and cookies;
- Try different browser (Chrome/Firefox);
- Wait 15-30 minutes during maintenance;
- Check firewall not blocking GitHub;
- Switch between WiFi and mobile data;
- Try incognito/private browsing mode;
- Monitor @githubstatus for service updates.
Repository access issues include repos not loading, "404 not found" errors, files missing, or repositories displaying blank.
- Refresh page to reload repository;
- Check repository visibility settings;
- Verify account has access rights;
- Clear browser cache completely;
- Check repository not deleted/archived;
- Verify organization permissions;
- Try GitHub CLI instead;
- Check repository URL correct;
- Verify branch exists;
- Contact repository owner for access.
Authentication problems include login failing, password rejected, two-factor authentication errors, SSH key issues, or account locked.
- Verify username and password correct;
- Use "Forgot password" for reset;
- Check 2FA code entering correctly;
- Verify SSH keys configured properly;
- Clear browser cookies and retry;
- Try personal access token instead;
- Check account not suspended;
- Verify email address confirmed;
- Remove and re-add SSH key;
- Submit ticket for account recovery.
Git operation issues include push rejected, pull failing, "permission denied" errors, merge conflicts, or authentication errors.
- Check repository permissions granted;
- Verify SSH/HTTPS credentials correct;
- Update Git to latest version;
- Check branch protection rules;
- Verify remote URL configured;
- Try force push cautiously;
- Check file size limits (100MB);
- Clear Git credential cache;
- Verify network allows Git protocol;
- Contact admin about access rights.
Workflow issues include Actions not triggering, jobs failing, runners offline, or workflow syntax errors.
- Check workflow file syntax valid;
- Verify Actions enabled in repository;
- Check runner availability;
- Review workflow logs for errors;
- Verify secrets configured correctly;
- Check billing/usage limits;
- Test workflow locally if possible;
- Verify trigger events correct;
- Check required checks passing;
- Update action versions used.
GitHub Pages problems include site not publishing, 404 errors, build failing, or custom domain not working.
- Check Pages enabled in settings;
- Verify source branch configured;
- Review build/deployment logs;
- Check custom domain DNS settings;
- Wait for build completion;
- Verify HTTPS enforcement settings;
- Check file structure correct;
- Clear browser cache for site;
- Verify Jekyll configuration if used;
- Check Pages quota not exceeded.
Pull request issues include PRs not creating, reviews failing, merging blocked, or status checks stuck.
- Check branch up to date;
- Verify required reviews completed;
- Check status checks passing;
- Review branch protection rules;
- Verify no merge conflicts;
- Check required checks configured;
- Update PR branch from base;
- Verify permissions to merge;
- Check draft PR status;
- Review merge queue settings.
Issue management problems include issues not creating, labels missing, milestones broken, or project boards not updating.
- Refresh page to reload issues;
- Check issue template used correctly;
- Verify permissions to create issues;
- Check filters applied on view;
- Clear browser cache;
- Verify project board automation;
- Check issue not already exists;
- Review repository settings;
- Verify labels exist;
- Try different browser.
Notification problems include alerts missing, email notifications off, watch settings ignored, or notification feed empty.
- Check notification settings in profile;
- Verify email preferences configured;
- Check repository watch settings;
- Review email spam folder;
- Enable web notifications;
- Verify email address verified;
- Check notification filters;
- Test with manual @mention;
- Review custom routing settings;
- Check email provider not blocking.
Gist functionality issues include gists not creating, snippets not loading, embed codes broken, or search failing.
- Refresh gist page;
- Check gist visibility settings;
- Verify account logged in;
- Clear browser cache;
- Try creating new gist;
- Check embed code syntax;
- Verify gist not deleted;
- Check file size limits;
- Try different browser;
- Review gist permissions.
Organization management problems include members not adding, team permissions wrong, billing issues, or settings not saving.
- Verify organization owner permissions;
- Check member invitation sent;
- Review team role assignments;
- Verify billing current;
- Check organization plan limits;
- Review security settings;
- Check SAML/SSO configuration;
- Verify member accepts invitation;
- Review audit log for changes;
- Contact GitHub billing support.
Codespaces issues include environment not launching, connection failing, timeouts, or filesystem errors.
- Check Codespaces quota available;
- Verify repository configuration valid;
- Restart Codespace completely;
- Check internet connection stable;
- Verify machine type sufficient;
- Review devcontainer.json settings;
- Check prebuild status;
- Clear Codespace cache;
- Delete and recreate Codespace;
- Verify billing/usage limits.
Security feature issues include Dependabot not updating, alerts missing, scanning failing, or vulnerability warnings ignored.
- Enable Dependabot in settings;
- Check security alerts permissions;
- Review dependency graph;
- Verify scanning enabled;
- Check alert notification settings;
- Review Dependabot pull requests;
- Verify repository language supported;
- Check manifest files correct;
- Review security policy;
- Update dependencies manually.
API problems include rate limiting, authentication failures, webhook not firing, or integration broken.
- Check API rate limits;
- Verify authentication token valid;
- Review API endpoint correct;
- Check webhook payload delivery;
- Verify token scopes sufficient;
- Test API with curl/Postman;
- Check API version used;
- Review webhook secret configured;
- Verify firewall allows webhooks;
- Check integration logs.
Application problems include mobile app crashing, desktop app freezing, sync failing, or notifications broken.
- Update GitHub app to latest;
- Clear app cache and data;
- Restart device completely;
- Check sufficient storage available;
- Verify account logged in correctly;
- Reinstall app from store;
- Check stable internet connection;
- Grant necessary app permissions;
- Try web version instead;
- Report crashes with logs.
GitHub
Your message will be published in about
5 minutes
Service administration will see your message