GitHub 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:

• 
  Techjunkie Aman (@Techjunkie_Aman) reported 52 seconds ago

  @JasonBoxman Raise an issue in GitHub

• 
  Danny 🏴󠁧󠁢󠁷󠁬󠁳󠁿 (@danjones) reported 2 minutes ago

  @stolinski @v_sapronov @rpunkfu Again, you said it yourself. It's cheap. Completely get why you would get hyped over it. But there's much deeper issues within GitHub, this is simply PR/ Marketing to mask over that. Feel free to tell me otherwise.

• 
  Puzzle Paws (@paws4puzzles) reported 3 minutes ago

  @rauchg man, 1.6% for open weight is rough. all this open source comeback talk and i'm just seeing a rounding error. developers vote with their wallets, not their GitHub stars.

• 
  Lina (@silent_puddle) reported 4 minutes ago

  @NeeK2323 i farmed all 8 by killing rares while in queue for m+. i have nothing left to do now when queueing :( btw, how does your rarity work? curseforge version is broken for me, i tried downloading one from github but it didn't work either

• 
  void (@voidcooks) reported 7 minutes ago

  @github Why ******** would anyone ever need this? If you wanted it…even more local…?… why wouldnt you just throw it on a flash drive? The whole point of github is to have your code not local..? Please fix downtime on actions or something remotely useful lol. What a joke.

• 
  echo (@echostatic101) reported 8 minutes ago

  @Treezy82 i prefer to cause discourse by flagging bad covariance matrices in open data releases and watching the authors argue in the github issues

• 
  Zed (@thezlatkom) reported 11 minutes ago

  @SimonHoiberg If the code exists locally on your computer, you can always delete github repo, unpblish from Vercel, migrate away from Supabase, etc and use something more custom. These problems aren't unsolvable.

• 
  Arshad Kazmi (@arshadkazmi42) reported 13 minutes ago

  @hetmehtaa honestly i stopped googling for tools a while back. if i hit a problem now i just build the fix. i've got a server running a few claude instances, exposed over termi so i can reach them from my phone. idea pops in my head on the commute, i throw a prompt at one of them, and its usually done by the time i get to office. buy a domain, point it to cloudflare, live in under an hour (server has cloudflare + github mcps so the domain is the only thing i do by hand). same thing for bug bounty. instances are hooked to the bounty platform over mcp so i can kick off a hunt from my phone, and when im at my desk i just tell ichat to take over and keep hunting with claude on the server via termi. if something i build feels worth selling i throw up a landing page and sell the source, lifetime only. been at this over a year now.

• 
  Galaxis (@GalaxisBeast) reported 13 minutes ago

  @voidcooks @github its obviously not something practical in the slightest, its a reference to an issue that is popular right now, which is sony ending disc production for ps5 games in 2028

• 
  Rambone (@vinrambone) reported 14 minutes ago

  @sudoingX My blank github days are spent deep in a rabbit hole of code im not ready to push bc its too broken But i dont want to *** restore.

• 
  Nexis (@Nexisintel) reported 16 minutes ago

  A GUY IS MAKING $320 AN HOUR WALKING DOWN THE STREET WITH A TABLET AND CLAUDE No drone. No survey crew. No week of processing. Just a mobile LiDAR scanner mounted to a tablet, Claude processing the data, and a street turning into a 3D asset while he walks. The device captures the geometry around him in real time. Building facades. Doorframes. Sidewalk edges. Surface textures. Every wall, curb, and corner becomes part of a point cloud on the screen. Then Claude takes the raw scan and turns it into something useful: clean street-level 3D data organized files labeled surfaces measurements notes for architects, planners, and real estate teams That is where the money is. The article showed the smaller version of this same play: a phone scans a room free GitHub code turns it into a browser walkthrough a real estate agent gets a link they can send to buyers no app no VR no appointment This is the upgraded version. Instead of scanning one room, he scans full streets. Instead of selling a virtual tour, he sells usable 3D datasets. Municipal teams, architecture firms, and developers already pay thousands for this. He charges $320/hour and delivers the files the next morning. The crazy part is not the scanner. It is the business model. Walk through the city once. Turn the physical world into data. Sell the data to people who used to hire a whole crew to collect it. Most people see a guy holding a tablet. Clients see a cheaper survey team.

• 
  Elias (@iam_elias1) reported 18 minutes ago

  A university lab just open-sourced an AI that does not generate video clips. It directs entire films. Screenwriter. Director. Producer. Video generator. Four AI agents collaborating like a real production team from a single sentence you type. It is called ViMax. Built by Hong Kong University's Data Science Lab. 10,800 GitHub stars. Trending #5 on GitHub. MIT licensed. Free. Here is the problem every AI video tool has right now. Sora generates a 10-second clip. Runway generates a 10-second clip. Veo generates a 10-second clip. Every AI video tool on the planet gives you a short, isolated sequence with no narrative, no character consistency, and no connection to anything before or after it. Ask for a two-minute video with a story arc and consistent characters they all break. Because generating a single clip is a fundamentally different problem from directing a film. A clip needs one prompt and one generation. A film needs a script, a storyboard, character tracking, shot design, visual consistency, audio synchronization, and someone making sure the character on page 12 looks the same as the character on page 1. No single AI model can do all of that. So ViMax does not use one model. It uses four agents. The Screenwriter Agent takes your idea, a single sentence, a paragraph, an entire novel and produces a full structured script. Characters, scene segmentation, dialogue, transitions. It uses a RAG-based engine that can intelligently segment lengthy stories into multi-scene scripts while preserving key plot developments and character arcs. You type: "A cat and a dog are best friends. They meet a new cat." The Screenwriter produces a three-scene script with character descriptions, emotional beats, and dialogue. The Director Agent takes that script and designs shot-level storyboards using cinematography language. Camera angles. Transitions. Pacing. Visual rhythm. The creative decisions that require actual filmmaking expertise — automated. It does not randomly arrange shots. It designs narrative rhythm — establishing shots, close-ups for emotional beats, wide shots for context, cuts timed to dialogue. The Producer Agent is the quality controller. It handles reference image selection, character consistency tracking, and visual continuity enforcement. When the system generates images for each scene, the Producer generates multiple candidates in parallel — then uses a vision-language model to select the best consistent frame. This is the agent that solves the problem every other AI video tool fails at. The character in scene 5 looks the same as the character in scene 1. The lighting stays consistent. The environment does not randomly shift. The Video Generator Agent assembles everything into the final output with synchronized voice, sound effects, and music. Four agents. One production pipeline. From a single sentence to a finished multi-scene video. Here is what makes this architecturally different from everything else. Most AI video tools are single-model systems. One prompt in, one clip out. ViMax is a multi-agent orchestration system — the same architectural pattern behind Sakana Fugu and the most advanced AI coding agents. Each agent specializes in one role. The orchestration layer coordinates them. The same way a real film production team works. Nobody expects the screenwriter to also operate the camera. Here is what you can actually do with it. Idea to Video — describe a concept, get a complete multi-scene video. Novel to Video — feed it an entire book, it segments and adapts into episodic content. Script to Video — write your own screenplay, ViMax produces it. Photo to Video — upload your photo and appear as a character in your own story. That last one is worth pausing on. Upload a selfie. Describe a story. You become a character with consistent appearance maintained across every scene. Here is the honest part. ViMax orchestrates, it does not generate pixels. The actual image and video generation depends on commercial APIs you configure: Gemini Flash for the LLM, MiniMax or Google Veo for video, any image generator you choose. You bring your own API keys and pay those providers directly. It is also early-stage. The TUI and agent loop were just stabilized on June 28. No formal benchmark against Sora or Runway exists. Quality depends heavily on which generation backends you plug in. And it is researcher-grade Python tooling — not a polished consumer app. But the architecture is right. And the research community knows it. The paper was published on arXiv on June 2, 2026. The repo has 10,800 stars in under five weeks. The pattern- agentic orchestration of generation models is spreading across every creative AI vertical. Here is what this means for the future of video. The next jump in AI video quality is not a bigger diffusion model. It is better orchestration. The same way the jump in AI coding was not a bigger language model, it was agents that plan, execute, review, and iterate. ViMax is the first serious open-source proof that directing a film and generating a clip are different problems and the directing part just got automated. A university lab in Hong Kong just open-sourced a film production team. You provide the idea. Four AI agents do everything else. Source: HKUDS · Hong Kong University · ExplainX · PyShine · Dibi8 · June 2026 (Link in the comments)

• 
  Tristan Poland (@Trident_For_U) reported 21 minutes ago

  @piq9117 @github 10 minute localized 'Degraded Performance' incident (like a slow API runner queue in Europe) as a 100% outage It also seems to count the post-fix 'monitoring windows' as dead time. ​I'll stick to my actual local CI/CD logs. Real telemetry beats a bad data parser every time.

• 
  Harish Kotra 🥑 (@HarishKotra) reported 23 minutes ago

  Day 183 of 2026 building! I built an onchain reputation graph for open source contributors. Every GitHub repo, contributor, issue, PR, and npm package gets a deterministic atom ID on the Intuition blockchain. Relationships between them become triples. No central registry needed, IDs are derived from canonicalized data, so any app computing the same input gets the same ID.

• 
  Patrick Barnhill (@Patrickbarnhill) reported 26 minutes ago

  DGX spark hosting main Hermes connected to telegram group chat threads. Honcho memory (just saw it was available trying it out hosted locally). Sharing to GitHub "agent ops" so other agents share important skills. Home computer running Hermes WSL and also windows native Hermes for computer control. Office PC running Hermes windows only for computer control. Daily driver codex gpt5.5. also running Qwen on DGX spark 1 and nemotron on DGX spark2 but with how inexpensive codex sub is with insane usage virtually no use for the DGX except for smart home if Internet is down