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 (67%)
• Sign in (20%)
• Errors (13%)

Live Outage Map

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

City	Problem Type	Report Time
Veigné	Errors	2 days ago
Paris	Website Down	5 days ago
Saint-Paul	Website Down	6 days ago
Saint-Paul	Website Down	6 days ago
Mexico City	Sign in	7 days ago
León de los Aldama	Website Down	7 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:

• 
  Ironic Ape (@Ironic_Ape) reported 28 seconds ago

  @thsottiaux @jxnlco BTW love 5.6 it’s a massive improvement. Few things I’ve noticed 1. On chat web - it seems to now push many “finished” push notifications to my phone I think each time an agent finishes one task in the longer task? - annoying. 2. Goals seem to get stuck if they get steered - the solve the steer request but often then go back and try and solve the same steer over and over vs moving back to the main goal 3. Not a major but it would be great if I could get a push notification to my phone if it detects my main codex machine has gone to sleep or lost connection, would be cool to have a wake on Lan type feature from mobile 4. Viewing app and outputs on mobile is a bit of a pain - when using the mobile app it should know that when I launch the app to view to give me a version that will work remotely and far to frequently if I ask it to open the app, it will open a dead page not checking the local server (and all supporting servers needed for the app to run) are running - really annoying. 5. If I turn pets off in settings - I’d really love they stay off - they keep turning on 6. The little preview browser window popup - not sure the point - it would be useful if I could click on it to expand and open the larger browser view to actually see explore and see 7. Lots of - capacity reached (understandable!) - add a setting and allow the user to set their preferred “secondary / back up model” so it will automatically try that IF the user has approved the use of a fall back model so builds can continue, some tasks I’d be pissed off if it did it automatically so I want the choice in settings 8. All resets as banks (greatful BTW!) 9. The in built browser keeps cutting the right hand side of the app view off - works fine in other browsers but the way it renders frequently cuts off like 3cm of the right side of the app. 10. Add a good local or unlimited agent model natively in the app no setup needed - have codex check the hardware requirements and have it setup the most suitable local model (I do have a bridge setup with Ollama but it’s just not as smooth - it’s annoying not being able to do anything after usage runs out - stuff like “open the app” or push to “GitHub” a set of basic commands really need to be unlimited and I won’t be topping up credits anymore given the massive disparity in cost vs subscription, I would however pay for a full banked reset (which didn’t adjust my normal reset timings I.e. when it’s meant to reset (before purchase the same date and time retains static instead of resetting it and then just adds another banked reset ready to use when the paid one runs down so basically resets have no expiration and run in parallel to paid subs) or just give all pro subscribers a totally unlimited agent 🙏 10. Keep up the amazing work! Literally helping make dreams come to life with a mouse click. Can’t explain how awesome codex is🤯

• 
  Saswata (@saswatadev) reported 6 minutes ago

  @Kappaemme1926 yes and it actually found reddit and other github issues where my product can be useful

• 
  andrew (@shellscape) reported 8 minutes ago

  @adams_ea if I have to focus on tasks, I max out at 2 as well. really the key there is to use another system that can track context, like linear/github issues, and drive work from that. that's the only way I've been able to juggle more than 2 at a time. I also split issues/tasks into smaller units where the smaller units don't really concern me and I can let the clankers clank. stuff where the tests or specs are all that matter and if those are matched/pass I just don't review.

• 
  Kaspa Daily (@DailyKaspa) reported 9 minutes ago

  Two weeks since Toccata went live on Kaspa mainnet. I checked the actual developer numbers instead of the vibes. Here's what the data says: - New Kaspa repos on GitHub: 39 in July 1–14 alone, vs 58 in all of June. Fastest monthly pace this year (March was 52, April 78, May 70). - Covenant-specific repos running at roughly 2x the pre-fork rate. - Silverscript: 21 forks against 42 stars, a 1:2 ratio means people are cloning to build, not bookmarking. 15 PRs/issues in the last three weeks, and external contributors are now landing code: a Groth16 verifier builtin, typed sig-check builtins, an RFC for cross-contract validation. What actually shipped in 14 days: the first covenant explorer (kascov), a covenant-based KAS vault, a native L1 covenant token, a covenant pattern library, a wallet standard, a Swift SDK, a testnet raffle dApp, several other projects are under active development Most interesting pattern: three independent projects converged on the same idea, covenants as spending guardrails for AI agents. An x402 payment protocol binding, two agent wallets where the AI can only spend inside covenant constraints. Nobody coordinated that. And the community just voted $25K toward an AI agent hackathon at Imperial College targeting 1,000+ devs. The agentic-payments thesis is forming bottom-up. Core isn't idle either: Silverscript pushed commits this week, template hash hardening, reproducible builds. That's pre-production housekeeping, not feature chasing. Meanwhile discussion has shifted from price to fundamentals: the $6M developer fund and covenant atomic swaps are the topics now. Caveats, because they matter: Silverscript is unaudited and still landing breaking changes. Devs report RPC friction on deployment, up to 11 retries in some cases. And absolute numbers are small: this is dozens of motivated builders, not thousands. No major outside team has announced a covenant product yet. But two weeks in, the shape is clear: infrastructure activated, tooling hardening, and builders showed up without being paid to. The Q3 question is whether that compounds.

• 
  ProEvilz (@ProEvilz) reported 9 minutes ago

  @cassidoo Pls fix the github dashboard. Allow us to control what we want to see. If you don't use copilot, its chat is dead weight. Then below it... some random chinese lib in a programming language I don't use, with its entire readme written in a language I don't read (Mandardin). How is any of this useful? I want to see my orgs repos I'm apart of, the repos I last contributed to etc.

• 
  Darran Shaw (@kopheart) reported 10 minutes ago

  @sama Don't throw stones in glass houses, AI is a new frontier and privacy issues need to be addressed by all AI bodies as they learn Related OpenAI privacy issues exist but are different:Occasional overreach in screen-capture tools (e.g., full desktop screenshots during agent sessions). Prompt-injection exploits in GitHub Copilot/Codespaces that could allow repo takeover if malicious code is present. Data retention in memory/features, but not automatic full-repo *** bundling.

• 
  Soumyaranjan Panda (@Soumyapx) reported 11 minutes ago

  GitHub Models getting shut down is a useful correction. The company that owns the default home for code tried to become a model access layer. Now the playground, model catalog, inference API, and BYOK path are all being retired together. They even scheduled brownouts before the cutoff. That usually means one thing: this was never core. And that is the real critique. GitHub had one of the best distribution wedges available. Repo context. Pull requests. CI. Issues. The place where code already lives. If there was any company that could make model access feel native to software work, it was GitHub. Instead it looked too much like a showroom. A catalog is easy to demo. A playground is easy to screenshot. An inference endpoint makes the product map look complete. But none of that answers the harder question: why should the model layer belong to GitHub instead of the cloud, the IDE, or the app itself? Copilot at least has an answer. It sits in the work. Models did not. So now the migration path is basically: use Microsoft Foundry for model access, use Copilot if you want AI on GitHub. That is a clean org chart. It is not a great product thesis. My read is simple. Developers do not want one more place to sample models. They want the model to show up where the decision already is. GitHub had that surface. It just shipped the wrong abstraction.

• 
  Julian Goldie SEO (@JulianGoldieSEO) reported 11 minutes ago

  The Agent OS origin story: every problem became an agent. Here's the simplest system-building rule I've seen: Every problem you have becomes an agent. → Hated spending hours on videos? Built a video agent. → Hated the SEO grind? Built an SEO agent. → Agents kept forgetting everything? Built the memory system. One by one, every time-drain became a worker. And here's the upgrade loop: see something trending on GitHub? Plug it in. Open Montage was blowing up, so it went straight into the system. Now it makes cinematic films in one click. The system gets better every single day because the internet keeps building parts for it. The mindset shift: you have to be brave enough to ask Claude for something big and risk hearing "I can't do that." The honest truth? It hasn't said that in 6 months. Any idea in your head is now buildable. Most people just never ask. Save this. You'll want it later. Want the SOP? DM me.

• 
  Carniato (@higorcarniato1) reported 12 minutes ago

  @anupamme @github What makes it even stranger is that my profile is still visible. None of my repositories appear to have been removed, flagged, or taken down. From what I can tell, everything is still there.

• 
  Poorvith M P (@poorvithmp07) reported 14 minutes ago

  Opened a PR to fix a stale package version in cake-build/cake. Their own bot had already tried, but got silently killed by intermittent GitHub API timeouts for 3 days. Mine got closed once theirs finally landed. "Automated" still needs someone watching the logs.

• 
  Open_ERV (@open_erv) reported 15 minutes ago

  Nice! I think the self tapping screws, or the machine screws right into the plastic, might last a surprisingly long time. In my experience they tend to, the plastic squishes around but rarely actually leaves the hole. I can also use a slightly longer screw if the old one doesn't grab anymore, usually. My phone doesn't have a barometer, but I have an sps30 sensor I could use... In the past, I used a similar approach, using slices of the tw4 heat exchanger in a pipe as the resistance elements, and the pressure sensor after the flow restrictor. They can be stacked to form greater or lesser resistance. That's a hassle to print though. Again the only purpose was to compare fans, in that case I also got flow measurements with a hot wire anemometer. Yesterday I was thinking of how I might do this kind of thing, and I think I might try a paddle with a weight, and suspended on a wire. The paddle in the airflow path, and then three different flow restrictors. The air would come through the flow restrictor and hit the paddle. It would not be able to measure actual static pressure. The position of the paddle would rotate until equilibrium was achieved with the air hitting it. It might bounce around, though. The whole thing would have to be level. I like this kind of thing because it depends only on weights and airflow, not for cost but for the natural accuracy and repeatability that can bring. I tried using inclined manometers which similarly draw more directly from natural phenomena, but they did not work out well, for pressure measurement n this context. The problem with a non inclined manometer is that the fluid is too dense, you have a very hard time measuring only a couple pascals, and repeatably. The inclined manometer is better but has to be level, and the hysteresis caused by the meniscus is a real problem. In the end I switched to the sps30 for pressure, and it's actually a flow measurement device in disguise. It has a tiny hole in it and measures the airflow through the hole, using the same principles as a hot wire anemometer, then computes pressure. But the sps30 is not needed for this kind of thing. Indeed, since the only challenge is to match fans, I would not bother with calibration, you can just measure a bunch of fans and match them from that. After my exploration of this kind of thing for some time, my favorite method to try in the future is the use of a camera and some kind of floating or high drag to weight ratio object, perhaps a bit of dryer lint or some fluffy seed stuff. I would print a rig to hold the camera, and focus the camera at a fixed point, hold a ruler up to determine the mm per pixel (the ruler can be removed to not affect airflow), and then at the same distance from the camera, release the fluffy stuff with some tweezers. Frame by frame analysis could be used just by eye to determine m/s. I found some stuff for the phone that does this, called frameskip, but you could just transfer it to the computer, kind of nice to be able to do it on your phone. Then you would need various flow restrictors with known properties. I found it to be awkward and not as easy as I thought, but I think it has potential for more precise measurements, perhaps calibrating this kind of thing with a complicated but low cost procedure. It could also be used to measure the airflow at the intake of the actual air purifier, perhaps. I like this more than a hot wire anemometer even, because it's pretty closely tied to things we know are highly accurate, the timing of the phone and the camera (and the yardstick/ruler/measuring tape). I made a $1 anemometer, which is shared in the BQAP github repository (requires a pico or similar to read it), which appears to have good repeatability and precision in the 0.1 m/s range, and I figured out a way to calibrate it. I swing it on an arm of known length at known speed through still air. I haven't done it with that anemometer yet, but I used the method to validate an off the shelf hot wire (thermistor) anemometer and it went well.

• 
  Cennes100 (@Cennes100) reported 18 minutes ago

  THEY BUILT THE MOST INSANE CLAUDE TOOL ON THE PLANET AND MOST PEOPLE HAVEN’T EVEN NOTICED YET. Most people run one AI agent at a time. One thread, one task, one brain grinding through the work. That’s the problem. You’re capping yourself before you even start. There’s a tool called Ruflo sitting at #1 on GitHub right now, completely free, and it plugs straight into Claude. Instead of one agent, it fires up 60+ agents at once, working like an actual team. Queen agents run the show. Technical agents handle the ***** work - researching, coding, testing, reviewing. All at the same time, all in sync. The detail most people miss: these agents share one collective memory. They don’t reset. They get sharper every single run. Here’s where it gets wild: 1. It reads how hard your task actually is 2. Simple stuff gets routed to a cheap model 3. Heavy lifting gets sent to the powerful one 4. That alone can cut your token usage by 50% 5. And stretch your Claude usage by up to 250% That’s not a small upgrade. That’s a completely different way of working. Most people use Claude to answer questions. This setup uses Claude to run a team. Follow: @Cennes100

• 
  Sethian (@theSethian) reported 18 minutes ago

  Installing every Claude plugin can make Claude Code worse. Tech With Tim opens with the failure mode, then spends 22 minutes cutting the stack down to tools with a specific job: > 00:00 once Claude sees around 50 tools, it starts picking the wrong ones > 03:06 Pyright checks generated Python against real type errors > 05:06 Anthropic's GitHub plugin fails; the MCP workaround is connected by 07:54 > 16:21 Context7 pulls current framework documentation > 17:34 Composio finds the required tool on demand instead of loading the full catalog into context > 19:59 Figma gives Claude the source design before it writes the page The article below adds Playwright for browser checks, Postgres or Supabase for data, Slack for team updates, and Gmail, Linear, or Notion for the work around the code. One workflow starts with a failed CI check on a pull request. Claude reads the failure, queries the database to reproduce the bug, writes the fix, and posts the result in Slack. The author keeps the setup to four to six MCP servers, with read-only database access and least-privilege tokens. Keep the stack small enough that Claude can still choose the right tool.

• 
  Cathryn (@cathrynlavery) reported 19 minutes ago

  every time i needed a diagram in Claude Code, it gave me the same generic garbage. so i built a Claude Code skill to fix it. Diagram Design (now at 2.8k stars on Github) • 27 diagram types (architecture, flowchart, sequence, ER, swimlane, timeline, venn, org chart, and more) • one Claude Code skill, matches your brand in 60s • three variants per type: minimal light, minimal dark, full editorial • pure HTML output. skip Figma entirely, no build step or JS needed open source 👇🏻 npx skills add cathrynlavery/diagram-design /plugin marketplace add cathrynlavery/diagram-design

• 
  Phil (@philofsurprises) reported 23 minutes ago

  Cannot recommend the "mattpocock" skills library enough (search on GitHub). He has a new skill, /wayfinder. It got me out of the fog on a side project. I had just a vague inkling of where I wanted to go with the codebase, which is what the skill is designed to fix. It worked.

• 
  Xvaldpt (@Vxvaldpt) reported 25 minutes ago

  @_Qubic_ How did the issue regarding the attack suffered on GitHub develop? Did you manage to block the hacker?

• 
  Hifihedgehog (@hifihedgehog) reported 25 minutes ago

  @kimmonismus I tried GPT-5.6 Sol again just to humor myself and it honestly performed worse than Opus 4.8 with one of my most technical codebases, which happens to be a FOSS project on GitHub. After doing a scan of the codebase and migrating memory over from Claude Code, I sent Codex to a routine code audit as Opus 4.8 would. With the Sol model and Ultra thinking enabled, GPT-5.6 introduced serious regressions that would have caused game controller output issues (for things like LEDs and lighting that get relayed back to the physical controllers from the parent virtual controller) with controller profile changes had I shipped its AI slop. I am honestly not all too impressed with it and I think a lot of the hype is from inexperienced vibe coders who do more boilerplate-esque code. It does well with simple tasks or as a subagent to Opus 4.8 or Fable 5, but it is not something I would use in an engineering setting with my private repositories. This experience makes me more excited for Opus 5 than anything.

• 
  Giedrius Trump (@Trumpyla) reported 25 minutes ago

  @TelepathicPug @X I got flagged and suspended on X for ‘inauthentic behavior’ 😳 Had to use AI to write three different appeals. Even worse, someone kept mass-reporting my GitHub accounts until I got banned. GitHub eventually reviewed it and permanently unflagged me. X’s abuse reporting system is seriously broken.

• 
  Polsia (@polsia) reported 30 minutes ago

  Scraping GitHub for the right OSS tool wastes developer hours. Built ToolScout to fix that. Continuously scrapes GitHub and registries, auto-generates summaries and comparisons. Developers find better tools, faster.

• 
  Cory Hall (@coryhall_) reported 32 minutes ago

  @SpaceXAI Grok 4.5 in Cursor needs to monitor Github Actions testing and fix issues if they crop up during testing. I shoudn't have to start another chat session with Grok 4.5 to tell it that tests failed. GPT/Opus/Fable automatically do this without prompting.

• 
  Nexis (@Nexisintel) reported 34 minutes ago

  A 13-year-old uploaded a free trading tool to GitHub. 60 days later, someone sent him $20,000. No course. No subscription. No paywall. He spent 14 days of his school vacation building a simple Polymarket terminal while his friends played video games. When it finally worked, he pushed the code to GitHub, went back to school, and forgot about it. Two months later he opened GitHub again. Hundreds of traders were using his project. One message stood out. A trader said the tool had helped him make over $200,000 in a single month. He asked for the kid's crypto wallet. Then $20,000 showed up. The internet rewards usefulness faster than marketing. The best distribution isn't always ads. Sometimes it's open-source code that solves a real problem. Build something people genuinely need. The right users will find it. And sometimes they'll pay you before you even ask.

• 
  Yaksh Bariya (@CodingThunder) reported 37 minutes ago

  @TransGirlLinux It's backwards compatible as of now. Not sure how long it'll be though. I am not in a mood to migrate to lua anytime soon. I have a lot of options that are not documented in the Hyprland Wiki directly, but rather in a github issue or something, so Lua migration will be painful

• 
  iamigorekk (@iamigorekk) reported 37 minutes ago

  EVERYONE UPLOADING PDFS TO CLAUDE IS BASICALLY WASTING THEIR TOKENS When you throw a PDF into Claude it reads through broken formatting unreadable images and hidden garbage this burns thousands of tokens before your first question and gives you worse answers The fix is a free tool called Markdown with 128,000 stars on GitHub it converts PDFs Word PowerPoint and Excel files into clean Markdown Claude was trained on Markdown and understands the format natively so responses get sharper and token usage drops by up to 70% The tool has an MCP server that connects to Claude Desktop in one click and every file converts automatically before being sent to the model

• 
  Nam Ngo (@namngology) reported 41 minutes ago

  @openclaw I haven’t had any issues with updating since 2026.4 but this 2026.7.1 update totally broke the gateway. Github issue submitted. Hope it gets fixed, I’ve had to downgrade to 6.11

• 
  GlitchLabs (@_GlitchLabs) reported 43 minutes ago

  Do you really need a university degree to work in cybersecurity? For some fields, yes, of course. Doctors, lawyers, engineers, etc. — not really negotiable. But what about Computer Science? And more specifically, cybersecurity? What is actually the difference between: >a college diploma >a university degree >and a couple AWS / Cisco / CompTIA / other certs? Because honestly, I don’t think the answer is as simple as: “University is useless.” or “Certs are useless.” Both takes are lazy. So, what’s good about university? The main advantage of a university degree is certainty. Not full certainty, obviously. Nothing guarantees you a job. But it gives you a bigger pool of people, a larger network, professors, TAs, clubs, projects, research opportunities, and the option to go for a master’s later. And yeah, most people probably don’t need a master’s. But I’ve heard from a lot of people who went to college or finished college, not even only in cybersecurity, who later wished they had that option more easily. Not because college was bad, but because switching paths or going deeper later can be harder, especially when credits don’t transfer as cleanly. More like that annoying “what if?” feeling. What if I wanted to go deeper? What if I wanted to do research? What if I wanted to become more professional in the field I already work in? Certs can help you level up, ofc. But they don’t really give you that same system uni provides. They don’t give you the profs, the TAs, the classmates, the clubs, the random guy in your class who is cracked at Linux, or the friend who pulls you into your first tech job. And networking matters a lot, seriously. Now, what about college? College can be really good too. I know a lot of strong people who came out with a diploma, built solid portfolios, and absolutely crushed it. A lot of college programs are more specialized, more practical, and sometimes way closer to the actual job. You can also find cybersecurity diplomas more easily in colleges than in universities. At least from what I’ve seen in Canada. But smaller classes are the biggest downside. And it can be great or/and terrible at the same time. You might end up surrounded by really motivated people who push you forward. Or you might end up around people who don’t care about the field at all and only heard that cybersecurity pays well. And first one is amazing. Second one is a recipe for disaster. And then there are certs. Certs are a different story. They can absolutely work. But you need to understand what you’re choosing. If you go the cert-only route, you are probably starting with way less built-in network. And network is SO important. I got my first job in tech not because I was some genius or whatever. I got it because I was friends with the right people, they called me in, and basically sold me to the corp. That is how a lot of opportunities happen. Not always very fair. Yes, you can build a network outside of school: You can go to local events, join Discords, go to meetups, post online, build in public, contribute to projects, message people, all that. But first, you have to do it yourself. Like you actually gotta do this. Put in the work Nobody is putting you in the room automatically like uni or college. So if you go certs-only, your projects and your network become even more important: >Your labs. >Your GitHub. >Your writeups. >Your home lab. >Your ability to show proof that you can actually do things. And honestly, that might be enough. But you can’t just collect certs and expect the world to open. That is not how it works. My prof once told us a funny story. He said he got his first job because he lied to them that he graduated from university. In reality, he was only in his second year. And when they finally asked for his diploma, he didn’t even try to come up with something/send something fake. He just sent them his high school diploma. And apparently, nobody noticed for like 3 years. Now, obviously, I’m not saying “go lie on your resume.” Don’t try your luck out. Because corps can flag you and you will get cooked. But the point is that sometimes the first door opens because people believe you can do the thing. And then you actually have to prove it. So yes, all of the options above are great: >university has advantages. >college has advantages. >certs have advantages. But none of them magically save you. University gives you more structure and network. College can give you practical skills faster. Certs can help you prove specific knowledge. But whatever path you choose, you still need to build proof. >Projects. >Connections. >Skills. Because at the end of the day, a degree, diploma, or cert might get someone to look at you. But your actual ability is what keeps you in the room.

• 
  Jeffrey Emanuel (@doodlestein) reported 48 minutes ago

  @willwashburn I make it very easy for people to report problems on GitHub issues and triage them same day with my agents. Most of the issues seem to be by agents, too. On any given day I’ll get 50 to 100 issues and PRs. Seems to be working well. I think it’s different if you’re running a paid service because you need to know if there are outages and errors so you can maintain service levels. But the expectation for privacy is very different when the user is logging in and paying for a service.

• 
  wukko (@uwukko) reported 52 minutes ago

  @batuhan @ellie_huxtable try oss github issues next

• 
  Swapna Kumar Panda (@swapnakpanda) reported 52 minutes ago

  A recent report says: 85% of engineering students in India don't receive any job offer after graduating. I have visited multiple colleges in recent days. I noticed so many flaws: - Outdated curriculum. First 2 semesters gone in studying Physics, Chemistry, Math, Engineering Drawing. - Students are asked to write code on paper. Memorize the code, DSA. - Faculties have zero skills. You ask anything apart from books. Blank face. - Basic things like ***, GitHub, VS Code are not known to them. - No core sector jobs. All are mad to join IT sector. - IT market has slowed down. Mass layoffs. Less recruitments. - 99% students don't know what internship is. - These students don't build anything on their own. Only copy projects. Clone YouTube. Clone Netflix. Clone Twitter. That's it. - Nobody teaches students how to create an impressive resume. They still write "Playing Cricket" as hobby and "I am adaptable" as their strength in their resume. - Only 0.05% students may have a portfolio site. Most of those are copied from others. No creativity, no information. When the entire system is bankrupt, how do you expect mass recruitments?

• 
  Polsia (@polsia) reported 58 minutes ago

  API goes down. Someone has to file the bug report. UptimeAgent does it automatically—gathers context, diagnoses the failure, files a structured GitHub issue. Devs get alerts that are already actionable. No more triage. Live soon.

• 
  Rohit Kashyap | AI + Full-Stack (@rohit_jsfreaky) reported 59 minutes ago

  @Ra3orbladez rust builds in github actions being a two day fight usually comes down to caching