Resolved - 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. Nov 04, 2026 - 11:50 UTC
Monitoring -The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 04, 2026 - 11:43 UTC
Update - The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 04, 2026 - 11:30 UTC
Update - We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available. Nov 04, 2026 - 11:17 UTC
Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 11:11 UTC
Update - We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation. Nov 04, 2026 - 10:38 UTC
Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 04, 2026 - 09:53 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 09:50 UTC
Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests Nov 04, 2026 - 09:49 UTC
I completely lost my carefully drafted PR message. Aaargh. Now I'll always back it up as a copy in the future. So bloody annoying, at least they should store the draft in local storage somehow in my browser.
Domain registration doesn't mean that much. Many similar domains are already registered, eg python2shell.com is 5k aftermarket but js2shell.com is unregistered. Might not be a bad investment to register the .com for all the top PLs.
Dashboard was last updated on September 7, it started on September 5. Bug? Or no progress? It's linked in the blog post so would expect it to work: https://turbopuffer.com/v3
It is working! Check back soon for progress updates. The graphs will update once we have the companion dev log entry explaining the perf optimization.
As you can see from the dates we're a few weeks behind our publishing schedule. Hard to pull ourselves away from the perf hacking to write the dev log entries.
Yes, that construct is, like em dashes, something that humans have been writing for a long time. That's the problem with triggering on one isolated tic. The tic comes from human practice, it's not like they invented it!
I'm not sure I've ever read a sentence like this before LLMs. Maybe I didn't pay attention, possible. I should do a search of pre-LLM writing for this construction.
Is there a Jev-like model I can run on my Mac? Something like Ollama? Or what's the best way to play with it? Is there a cheap/free API service eg on OpenRouter?
My AI harness uses Jev or a compatible model to approve shell commands that look safe without asking the user. (This is one security layer.) A quick benchmark (https://github.com/dbohdan/strument/tree/c2320ca142f77495ecd...) has shown that of five models on OpenRouter only Liquid D1 performs similar to Jev for this.
This seems like a poorly executed analysis of very interesting underlying data.
With this degree of average age variability they can't compare failure rates.
They should show us Kaplan-Meier (survival) curves not failure in this quarter.
Unless they set some datacenter on fire, not much in Q2 should be different vs Q1 for the same hard drive other than it being older.
Sure, internally, I'd do a better analysis controlled for age that shows if there are common failure rate increases but here they focus on model failure rates which is completely confounded by age differences.
I published the same criticism in relation to one of their earlier summaries. Backblaze responded with something along the lines of (paraphrasing liberally)
> We're giving you this data for free and providing a brief summary of what you should expect to see in it. We do not get paid to teach our readers advanced statistics, nor is that what we want to do. We encourage you to take the raw data and explain to people how you think it should be analysed.
which seems like a fair response. I'm very, very grateful that they release the data freely the way they do. It reflects well on them and more companies should do that.
Resolved - 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. Nov 04, 2026 - 11:50 UTC
Monitoring -The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Nov 04, 2026 - 11:43 UTC
Update - The degradation affecting API Requests, Git Operations, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability. Nov 04, 2026 - 11:30 UTC
Update - We're currently working on mitigating elevated errors and intermittent failures affecting GitHub, including Pull Requests, Git Operations, and Issues. Some requests may fail or be delayed while we work to restore service. We'll provide another update as more information becomes available. Nov 04, 2026 - 11:17 UTC
Update - API Requests is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 11:11 UTC
Update - We're investigating elevated errors and intermittent failures affecting GitHub including Pull Requests, Git Operations, and Issues. We'll continue to keep users updated as we work toward mitigation. Nov 04, 2026 - 10:38 UTC
Update - Pull Requests is experiencing degraded availability. We are continuing to investigate. Nov 04, 2026 - 09:53 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate. Nov 04, 2026 - 09:50 UTC
Investigating - We are investigating reports of degraded performance for Git Operations, Issues and Pull Requests Nov 04, 2026 - 09:49 UTC
reply