GitHub status: access issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of GitHub reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.

Most Reported Problems

The following are the most recent problems reported by GitHub users through our website.

• Website Down (57%)
• Errors (30%)
• Sign in (14%)

Live Outage Map

The most recent GitHub outage reports came from the following cities:

City	Problem Type	Report Time
Inverness	Website Down	9 days ago
Quito	Sign in	10 days ago
Junín	Errors	10 days ago
Guadalajara	Errors	10 days ago
Paris	Website Down	10 days ago
Quito	Errors	10 days ago

Full Outage Map

Community Discussion

Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.

Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.

GitHub Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Carlos Sanchez (@casancamdev) reported 4 minutes ago

  Github is down again? Maybe Origin will end up being a good option after all

• 
  Sayo Oladeji (@oluwasayo_) reported 4 minutes ago

  Another GitHub outage is brewing.

• 
  ARAMEON (@NeoAramean) reported 7 minutes ago

  @gregisenberg Why is this needed? The same people that are getting into software now are vibecoding and the harness they use is perfectly capable of using *** and push code to github. A non issue really

• 
  Vikram (@vchennai2) reported 7 minutes ago

  How is your latest Github outage going? I might go on a walk

• 
  Steven.Sun (@redboynono) reported 13 minutes ago

  @WatcherGuru The $13B Hugging Face number is still a reported talk/agreement, not a closed deal — neither side has confirmed. HF is not another model lab. It is the distribution layer: where developers find, pull, and ship models. NVDA already tried to put $500M in at ~$7B and got turned down because HF did not want one dominant shareholder. Buying the whole company at ~$13B would be L1 purchasing the L4 on-ramp, not stacking another faster SKU. The asset is community trust; AMD and Google publish there too. Is this owning the GitHub of models, or paying 2x for the minority stake they were refused last year? NFA

• 
  WhiteCap Data (@WhiteCapData) reported 18 minutes ago

  @nicbstme @github That screenshot data could flood the PRs if not normalized with the rest of the issue metadata.

• 
  Chris Hallas (@hicsfh) reported 19 minutes ago

  I kinda feel like there’s an opportunity between GitHub problems, object storage backed ***, AI and the AUR not wanting to collaborate…

• 
  Tim Harris (@timharris707) reported 20 minutes ago

  Sixteen files in my public repo have been showing a red error banner to anyone who opened them. I found out on Tuesday night, and only because I clicked into one of my own files on the web instead of reading it on my laptop. The cause is one character. Each of those files opens with a one-line description, and sixteen of them had a colon followed by a space inside that sentence. A strict reader of that format takes the colon as the start of a nested structure, finds a sentence instead, and stops. GitHub stops politely and prints a banner. Anything stricter refuses the file outright, and that is the part that actually matters. The whole claim I make about these files is that you can pick them up and use them somewhere else. So the descriptions are quoted now, with the wording byte for byte unchanged, and the build fails if any of them stops parsing. That check would have caught all sixteen on the day the first one broke. Twenty-five minutes from first commit to merged. I still cannot tell you how long they had been broken, and that is the part I keep thinking about.

• 
  based.slavic (@basedsnipez) reported 22 minutes ago

  might have found a $pons easter egg🥚 I checked the website, and I‘m not the best at reading blockchains but… I been digging into something for a Today that I think most of you are gonna fade it anyway but let me put it out there on 22 july the pons dev wrote a doc in their official github. a mascot called pepons, a frog, whole story about how he never moves which was his way of explaining the anti snipe protection on the pad 7 minutes later he deploys the token 10 minutes after that he goes back into the doc and swaps the placeholder 0x0000 for the real contract address 16 minutes and 49 seconds from writing the story to publishing the CA. both commits signed with his key, github shows the verified badge on both of them then 13 hours later he deletes the whole file. commit is titled "update README.md". it removed 243 lines you cant delete *** history tho. its all still sitting there the part that actually matters pons has documented mascots before and after this one. pepons is the only one with a live contract address attached every other one is just a story. this one is a story the dev signed a CA into and then took down what the chain says token was deployed through PonsLaunchFactory, thats the launchpads own contract. the tokens class is PonsLauncherToken which is the exact contract the doc names in its technical part. so the paperwork and the chain are saying the same thing contract has no mint, no owner, no tax switch, no pause, no blacklist. supply fixed at 1 billion minted once. nobody can touch it, not even the dev who made it and the story is actually in the code. the frog is about wallet caps and anti sniping, the contract has maxWallet, maxTx and a restriction period. it wasnt marketing it was a description the holder nobody looked at pons own fee wallet holds 26,874,358 pepons. thats 2.69%, biggest position that isnt the LP came in 20 seperate payments from PonsLaunchLocker starting launch day and still going this week not one token has ever left that wallet 🤝 it‘s really interesting and I love the fact it‘s a peoe derivative too we had a pepe run on every chain basedpepe on @base went to 100M+ basically, it‘s on their website, and fun to research shared it to some friends around 40k and they‘re up alot, seems like people catch up and thats why I thought, I‘dshare it $PEPONS

• 
  DFIR Lab (@DFIR_Lab) reported 26 minutes ago

  A server-side request forgery (SSRF) vulnerability was found in AWX's webhook status callback mechanism. When processing GitHub pull request webhooks, AWX extracts the status callback URL (pull_request.statuses_url) from the incoming webhook payload without validating the target host against the expected *** provider. This URL is persisted in job extra variables and later used to send authenticated status updates. A user with admin role on a webhook-enabled job template can read the template's webhook signing key, forge a signed GitHub webhook payload with an arbitrary statuses_url, and cause AWX to POST status updates to an attacker-controlled or internal URL. The status update request includes the configured *** Personal Access Token (PAT) in the Authorization header, resulting in credential leakage to the attacker-specified endpoint.

• 
  Sean the SRE (@SeanTheSRE) reported 26 minutes ago

  Another day another @github outage. I can't rely on this infrastructure anymore @Microsoft.

• 
  Jesse Ezell (@jezell) reported 27 minutes ago

  @jvallery Yep. When the actions are down hosting your own doesn't work either, you gotta also put the trigger outside github.

• 
  Kevin Burton (@inputneuron) reported 27 minutes ago

  @github Maybe on your podcast you guys could discuss the MASSIVE problem you guys have with stability and downtime. You're DOWN AGAIN! I work at a co-working facility and OTHER COMPANIES are actively discussing migrating away from GitHub - in public!

• 
  佐藤ひつじ@業務系システムエンジニア (@_hitsuji_sato) reported 28 minutes ago

  We are seeing HTTP 400 InvalidInput errors on Amazon Orders API v2026-01-01 searchOrders (/orders/2026-01-01/orders) in FE regions (JP/AU) since around 2026-08-26 18:08 UTC. The issue appears to occur when using: includedData=FULFILLMENT We have reproduced the same behavior in our environment as well. According to Amazon GitHub Issue #5365: - Requests including FULFILLMENT fail - Requests without FULFILLMENT succeed - Reproduced in JP/AU (FE) - NA appears unaffected - Reproduced across multiple seller accounts If you are using Orders API v2026-01-01 searchOrders, it may be worth checking for HTTP 400 InvalidInput errors, regardless of whether you currently use includedData=FULFILLMENT. Although FULFILLMENT is a documented supported value, the root cause has not been disclosed and no official response from Amazon has been confirmed yet. If you are seeing the same behavior, I'd appreciate any additional information. I'll share updates if Amazon provides further details.

• 
  Seth Rubenstein (@SethRubenstein) reported 28 minutes ago

  @jeffr0 You can just expect GitHub to go down in between 10-12 eastern time now, every single day.

• 
  Ayush Singh (@advolt7) reported 31 minutes ago

  follow him if you want to know whether github is down or not, useful.

• 
  Jesse Ezell (@jezell) reported 34 minutes ago

  @michaelbushe Often when github actions are down the remote runners don't work either. They also charge you to run your own runners. I'm starting to think local racks are the future.

• 
  RaoulDuke (@RaoulDukeDegen) reported 35 minutes ago

  @PovilasKorop devs even opened dozens of github issues just to kill that line

• 
  Chris 👽 (@VeryBullishGuy) reported 36 minutes ago

  @namespacelabs this is one of the smartest capex calls in infra right now and its not even close. apples license only lets macOS run on apple hardware, and only two VMs per machine. thats not a policy on a pdf somewhere, its enforced in code. try to boot a third one and the framework just errors out. so if you want to sell iOS CI you have to physically own the metal. no way around it. thats why AWS has to lock a dedicated host for a 24 hour minimum just to stay compliant, which is completely useless for a 6 minute build. and its why github charges about 10x for a mac minute vs linux, 6 cents against half a cent. that spread IS the business. apple killed the mac pro in march and has no server product at all now. so custom shelves full of consumer hardware is the only play anyone has. this isnt an unboxing video, its a barrier to entry.

• 
  rahul agarwal (@rahul67) reported 36 minutes ago

  Github Actions down again?

• 
  Joe Bond (@josephscottbond) reported 41 minutes ago

  @gregisenberg Hah! 2 anecdotes from my day confirm you’re right. 1. GitHub actions was down today… GitHub seems like they are having an outage every week now. 2. I was trying to figure out how to help a normie coworker contribute to a technical project without making her sign up for GitHub. Made a joke about vibe coding GitHub this weekend.

• 
  oxy (@oxy_786) reported 45 minutes ago

  I have been approached by these scammers twice alone in previous month They will find your Github and offer you position at their company for genuine amount, use actual contract terms, take time to reply, respect weekends to work with you They will do preliminary interview and ask for your previous work and how much you were paid (likely to know your net worth?) Then they send you some sort of website for filling CRM info, their website will show that "it's not working, download desktop app" I don't know how many people fell for that, but it's never worked on me Stay vigilant!

• 
  luiz castro (@loez__) reported 48 minutes ago

  github down de novo?

• 
  Harshil Tomar (@Hartdrawss) reported 48 minutes ago

  Even if you're not 17, you can still learn building LLMs from scratch ! Laptop + below Sauce + Hard work = Infinite Money 1. start with @karpathy zero to hero playlist : - micrograd first, 150 lines, you write backprop by hand and never fear autograd again - makemore parts 1-5, you go from bigram counts to a batchnorm MLP and see why initialization decides whether a net trains at all - "let's build GPT", 2h and you have a working decoder-only transformer on tinyshakespeare, self attention, multi-head, residuals, layernorm - the tokenizer video, you build BPE from scratch. this is the one everyone skips and then can't explain why their model is bad at arithmetic that puts you ahead of a lot of people already 2. try to rebuild nanoGPT from an empty file - target is GPT-2 124M, 12 layers, 12 heads, 768 dim, 1024 context - write the dataloader, the model, the training loop and the sampler yourself, no forking - get it training on openwebtext and watch val loss land near 2.85, thats the public benchmark you're checking yourself against - learn what actually breaks: gradient accumulation, mixed precision, cosine LR with warmup, grad clipping at 1.0 3. train a tiny model on one dataset for a specific usecase - 10-50M params on your own data beats another wikitext run for learning - your discord export, every commit message you've written, one author's full catalogue, 20 years of match reports - chinchilla rule of thumb: roughly 20 tokens per parameter, so a 10M model wants ~200M tokens. know when you're data starved - build your own tokenizer for it, a domain vocab of 8k beats a generic 50k on narrow data 4. rent an A100 for $2/hr on vast[.]ai - runpod and lambda price similarly, $30-50 covers a real overnight run - a 124M model on one A100 80GB is roughly a day of training, budget for 3 failed attempts before the good one - do not buy a $3k gpu, thats spending money to avoid spending hours 5. start studying deeper topics : - finetuning: LoRA rank 8-16 on the attention projections, alpha at 2x rank. QLoRA in 4-bit nf4 fits a 7B on a single 24GB card, thats a $0.40/hr machine - inference: KV cache is why memory grows with context, quantize to Q4_K_M for ~4x smaller with small quality loss, use vLLM's paged attention and continuous batching before you blame the model for being slow - evals: write 50 real prompts for your usecase and grade them before you tune anything. no eval set means every finetune feels better and you'll never know 6. study one paper a week and reimplement the smallest part - start order: Attention Is All You Need, GPT-2, Chinchilla, LoRA, RoPE, FlashAttention, DPO - don't reproduce the paper. reproduce one figure, one layer, one loss function 7. build one thing people can use : - a narrow finetune that beats a frontier model at one job, classification, extraction, one specific format - self host it, measure cost per 1k requests, that number is your margin - 10 paying users is the proof, not the github stars 8. post every run in public, failures included : - the loss that diverged at step 4000, the run you killed at 3am, the config that finally worked - share the actual hyperparams and the wandb chart, people follow specifics - compute grants, jobs and co founders find you through this long before a credential does honest math: ~12 months of consistent evenings, about $400 in rented gpu hours.

• 
  Shreyans Jain (@shreyansj) reported 50 minutes ago

  been a while since Github was down, I was getting worried

• 
  Rahul Dahre (@RahulDahre) reported 52 minutes ago

  Nvidia buying Hugging Face for $12.9B gives huge Microsoft acquiring GitHub vibes. hope they actually keep open source AI free and open instead of trying to lock down the whole ecosystem.

• 
  Nicolai (@nicomoel) reported 53 minutes ago

  @gabriel1 Classic GitHub experience: “billing problem” meaning something is broken, but not the thing we’re telling you.

• 
  Jesse Jr Lim (林振燊) (@Jessejrlim) reported 54 minutes ago

  Damn GitHub was down again.. janky

• 
  AlicZhang (@ZhangAlic) reported 54 minutes ago

  That line of reasoning is flawed. GitHub is a product with a robust, battle-tested engineering foundation, precisely because the problem it addresses is inherently complex. In the past, average users needed to learn how to interact with it to unlock its full value. Today, average users should access it via AI—which knows how to leverage GitHub effectively—rather than trying to reinvent *** specifically for the layperson. Doing so would only conflate two distinct issues—code version management and barrier-free usability for non-experts—resulting in a product that ultimately fails to deliver a good user experience.

• 
  Thet Naing (@ThetNaingML) reported 57 minutes ago

  Another day, another GitHub outage 🫠