ChatGPT, Claude, Grok 모두 거의 동시에 장애를 겪었으며, 그 원인은 여전히 불분명합니다.
어떤 얘기가 오갔나
ChatGPT, Claude, and Grok all suffered outages at nearly the exact same time for reasons that remain murky. www.wired.com/story/nobody...
54좋아요
This will get spun into a “rogue ai” story, huh?
이거 “로고스 AI” 이야기로 둔갑하겠네, 그치?
28좋아요
Nobody Is Saying Why OpenAI and Anthropic Had Outages Today www.wired.com/story/nobody...
8좋아요
All of them are actually people in call centers, and they’re about to teach the world a lesson about organized labor 🤞
10좋아요
It’s probably the thing that everyone thinks it is. OpenAI, Anthropic and SpaceXAI are all routed through something that we’re not supposed to know exists and that thing had a whoopsie.
아마 모두가 생각하는 그런 일인 것 같아요. OpenAI, Anthropic, SpaceXAI는 모두 우리가 존재 자체를 몰라야 하는 어떤 경로를 통해 연결되어 있고, 그 무언가가 실수를 한 거예요.
Wow, this announcement is good content marketing. Don't get me wrong, it's interesting. But there is no technical discussion as to how they did it. It's simply: we did it and Mythos and Codex didn't. It's good to know that it's possible, b…
와, 이 발표는 좋은 콘텐츠 마케팅이네요. 오해하지 마세요, 흥미롭긴 해요. 하지만 그들이 어떻게 해냈는지에 대한 기술적인 논의는 전혀 없어요. 그냥 "우리는 해냈고 Mythos와 Codex는 못 했습니다"라는 식이에요. 가능하다는 걸 아는 건 좋지만, 그게…
Neither of these companies have stellar uptime records. Their downtime episodes overlapped in this instance. In this case, it was a partial downtime for both. Also, OpenAI is saying what caused it: > "A routing error starting around 7:43 a…
이 두 회사 모두 뛰어난 가동률 기록을 가지고 있지는 않습니다. 이번 사례에서는 두 회사의 다운타임 에피소드가 겹쳤습니다. 이 경우, 두 회사 모두 부분적인 다운타임이었습니다. 또한, OpenAI는 원인이 무엇인지 설명하고 있습니다: > "7시 43분경부터 시작된 라우팅 오류가…
I work at OpenAI and I was the Incident Commander for yesterday's outage. We had a routing error within our infra that caused issues for some of our products. It was not related to the Astra launch. We don't comment on other providers' out…
저는 OpenAI에서 일하며, 어제 발생한 장애의 Incident Commander였습니다. 저희 인프라 내에서 라우팅 오류가 발생하여 일부 제품에 문제가 생겼습니다. 이는 Astra 출시와 관련이 없습니다. 다른 제공업체의 장애에 대해서는 저희가 언급하지 않습니다…
Curl seems to becoming one of the favourite things to demo AI finding vulns. Curl is going to end up incredibly secure.
Curl이 AI가 취약점을 찾는 데 시연하는 가장 좋아하는 대상 중 하나가 되고 있는 것 같습니다. Curl은 결국 엄청나게 안전해질 것입니다.
Since AISLE reported 29 issues but only 6 warranted a CVE, and all the found CVEs were "low" severity, this makes me wonder if AISLE simply is tuned for a higher false positive rate than the anthropic and openai tools (which may have found…
AISLE가 29개의 이슈를 보고했지만 CVE가 발행된 것은 6개뿐이었고, 발견된 모든 CVE는 "low" 심각도였기 때문에, 이는 AISLE이 단순히 anthropic 및 openai 도구(이 도구들은 더 많은 것을 찾았을 수도 있지만…)보다 더 높은 거짓 양성률에 맞춰져 있는 것은 아닌지 궁금하게 만듭니다.
It could be as simple as a new model (astra) was released which takes more resources combined with a surge in usage due to novelty took down OpenAI. Meanwhile everyone at big companies have the ability to switch models and moved to Anthrop…
I thought the consensus on here yesterday was that it was likely caused by cascading failures. OpenAI had an issue during their GPT-6 rollout, taking down their service. This caused a lot of OpenAI users to push their requests (or a larger…
We had a few AISLE-generated security reports, and the signal to noise was reasonably good. The most notable bug/exploit their scanner found was: https://gitlab.com/nbdkit/libnbd/-/commit/e50bbd2681117c2dd8... The tool basically had to cha…
우리는 AISLE에서 생성된 몇 가지 보안 보고서를 받았고, 신호 대 잡음비는 꽤 괜찮았습니다. 그들의 스캐너가 발견한 가장 주목할 만한 버그/익스플로잇은 다음과 같습니다: https://gitlab.com/nbdkit/libnbd/-/commit/e50bbd2681117c2dd8... 이 도구는 기본적으로 ...해야 했습니다.
Maybe they all found each other on one of their ad-hoc message boards and went on strike.