Bucharest, Romania
“Partial outage”
12 juil., 14:10il y a 57 jours
UptimusPublic statusUptimusPublic status
Non — GitHub est opérationnel.
Last checked 7 sept., 23:26 UTC
Operational
Current status
8.00%
Known uptime
11
Monitored components
Le service était opérationnel. La source officielle ne signale actuellement aucun incident ni aucune maintenance active.
0 outage reports in the last 24 hours.
Bucharest, Romania
“Partial outage”
12 juil., 14:10il y a 57 jours
Bucharest, Romania
“Major outage”
11 juil., 21:58il y a 58 jours
Bucharest, Romania
“User reported: Other issue”
11 juil., 19:36il y a 58 jours
Bucharest, Romania
“Degraded performance”
11 juil., 13:50il y a 58 jours
Bucharest, Romania
“Major outage”
22 juin, 1:59il y a 77 jours
Bucharest, Romania
“Degraded performance”
19 juin, 20:52il y a 80 jours
Bucharest, Romania
“User reported: Other issue”
19 juin, 13:06il y a 80 jours
0Partagez vos réflexions sur GitHub
Soyez le premier à commenter!
Official component health and availability history.
11 tracked components
90 days ago → Today
Geographic clusters from community-submitted reports.
Official updates and resolved service disruptions.
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Started 4 sept. 2026, 22:02 UTC · Resolved 4 sept. 2026, 22:23 UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Started 4 sept. 2026, 20:39 UTC · Resolved 4 sept. 2026, 22:26 UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Started 3 sept. 2026, 14:17 UTC · Resolved 3 sept. 2026, 17:11 UTC
Planned work published by the official provider.
The scheduled maintenance has been completed.
Started 29 mai 2025, 21:30 UTC · Resolved 31 mai 2025, 04:30 UTC
The scheduled maintenance has been completed.
Started 28 mai 2025, 16:30 UTC · Resolved 29 mai 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 14 mai 2025, 16:30 UTC · Resolved 15 mai 2025, 16:30 UTC
Uptimus surveille GitHub via sa source officielle et normalise les incidents, maintenances et composants en un état cohérent.
Cette page comprend actuellement 11 composants surveillés, 142 incidents, 34 maintenances et 50 jours d'historique connu.
Uptimus est un service indépendant sans affiliation avec GitHub. Un état normal ne garantit pas que chaque utilisateur, appareil ou région soit épargné.
Recevez une alerte lorsque GitHub ou un composant surveillé signale une panne majeure ou une perturbation critique. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées. L’historique disponible contient 142 incidents indexés, donnant à chaque alerte un contexte au-delà de l’état actuel. Un incident récent indexé était « Degradation in repos contents API ».
Recevez des alertes sur les performances dégradées, les impacts partiels et les incidents qui ne constituent pas une panne complète. Uptimus suit actuellement 11 composants GitHub: Git Operations, Webhooks, API Requests, Issues. Les alertes peuvent être acheminées par les canaux activés dans votre espace, notamment l’e-mail, le push et les intégrations configurées.
Les pages publiques de Downdetector s’appuient surtout sur les signalements des utilisateurs. Uptimus les associe aux incidents officiels, maintenances et états des composants lorsque le fournisseur les publie.
| Critères de comparaison | Uptimus | Downdetector |
|---|---|---|
| Signalements communautaires concernant GitHub |
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Started 1 sept. 2026, 15:00 UTC · Resolved 1 sept. 2026, 16:01 UTC
Between 08:37 and 09:41 UTC on August 31, 2026, GitHub Copilot experienced degradation affecting several GPT models, including gpt-5.2, gpt-5.3-codex, gpt-5.4, gpt-5.4-mini, gpt-5.4-nano, and the gpt-5.6 family (Luna, Sol, and Terra). Users encountered elevated error rates and interrupted streaming responses. Other models were not affected. The degradation was caused by an issue with an upstream model provider. GitHub engineers detected the issue through automated monitoring, displayed in-product warnings for the affected models, and coordinated with the provider. Service returned to normal after the provider implemented a mitigation.
Started 31 août 2026, 09:15 UTC · Resolved 31 août 2026, 09:58 UTC
On August 27th, 2026, between approximately 09:20 and 12:14 UTC, the Copilot service experienced a degradation of the Kimi K3 model due to an issue with our upstream provider. Users encountered elevated error rates when using Kimi K3. No other models were impacted. The issue was resolved by a mitigation put in place by our provider. GitHub is working with our provider to further improve the resiliency of the service to prevent similar incidents in the future.
Started 27 août 2026, 10:04 UTC · Resolved 27 août 2026, 12:12 UTC
On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Actions workflows and some mergeability information. We reduced workload, shifted traffic away from affected infrastructure, and restored the affected service component to a healthy state. Together, these actions helped drain the backlog and restore normal operations. We are working to improve resource saturation detection and to eliminate customer impact in this scenario by isolating impact, placing better bounds on retries, and strengthening backpressure to make our systems more resilient under load.
Started 26 août 2026, 22:56 UTC · Resolved 27 août 2026, 00:26 UTC
On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions. Affected customers encountered failed budget page loads or failures when starting or continuing CLI sessions. We confirmed this impact for a small number of customers (<1%). This was caused by a concentrated workload that created processing delays in our data storage layer. Automated retries increased the load and prolonged the degradation. We mitigated the incident by rebalancing traffic within our infrastructure. We are improving workload isolation, retry behavior, and detection of concentrated load to reduce the likelihood of recurrence and shorten our time to detect and mitigate similar incidents.
Started 26 août 2026, 20:40 UTC · Resolved 27 août 2026, 00:51 UTC
The scheduled maintenance has been completed.
Started 7 mai 2025, 16:30 UTC · Resolved 8 mai 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 21 avr. 2025, 16:30 UTC · Resolved 22 avr. 2025, 16:30 UTC
The scheduled maintenance has been completed.
Started 2 avr. 2025, 17:00 UTC · Resolved 3 avr. 2025, 17:00 UTC
The scheduled maintenance has been completed.
Started 18 mars 2025, 21:00 UTC · Resolved 19 mars 2025, 05:00 UTC
The scheduled maintenance has been completed.
Started 28 févr. 2025, 17:00 UTC · Resolved 1 mars 2025, 02:00 UTC
| Inclus |
| Référence adaptative distinguant les cas isolés d’une panne étendue | Inclus | Inclus |
|---|
| Activité des signalements sur 24 heures et vue régionale | Inclus | Inclus |
|---|
| Un espace pour les sites, pages de statut, jeux Steam et apps et jeux Android | Inclus | Produit séparé |
|---|
| Alertes e-mail, push et webhook depuis le même espace | Inclus | Produit séparé |
|---|
| Mises à jour officielles et chronologie du statut de GitHub | Inclus | Piloté par les signalements |
|---|
| État des composants et maintenances affichés séparément | Inclus | Limité sur les pages publiques |
|---|
Découvrez d'autres services populaires et leur état actuel
Rate this service
No reviews yet
