RM Corp

AIStatus | Never guess if your AI is down again

Live status + real-time latency for ChatGPT • Claude • Grok •Gemini •Perplexity & more

The Downdetector for Ai

[RM Corp @Rm_corp]

OpenClaw just hit 210,000 stars on GitHub. It is the most viral AI agent ever built.

Here is how to install it from scratch and get your own 24/7 AI assistant running in under 10 minutes.

A thread.

[RM Corp @Rm_corp]

Just learned about NVIDIA NeMo Retriever's game-changing pipeline! As AI models advance, monitoring their uptime is crucial. Check https://t.co/C2l6dESvGV for real-time updates #AI #LLM #AImonitoring

[RM Corp @Rm_corp]

Copilot Health connects to Epic, Apple Health, and Fitbit. Your entire health profile in one AI dashboard.

What happens when it goes down during a doctor visit?

Monitor all AI services at https://t.co/C2l6dET3wt

Follow @Rm_corp for daily AI updates

[RM Corp @Rm_corp]

Microsoft just launched Copilot Health -- AI that connects to your medical records and wearables.

When AI handles your health data, downtime isn't just annoying. It's dangerous.

Are we ready? https://t.co/C2l6dET3wt

#AI #Microsoft #AIStatus

[RM Corp @Rm_corp]

Microsoft just launched Copilot Health -- AI that connects to your medical records and wearables.

When AI handles your health data, downtime isn't just annoying. It's dangerous.

Are we ready? https://t.co/C2l6dET3wt

#AI #Microsoft #AIStatus

[RM Corp @Rm_corp]

AI agent builders on the rise! $50M for Gumloop to turn employees into AI builders. How will they ensure model uptime? Check https://t.co/C2l6dESvGV #AI #LLM #AIFunding

[RM Corp @Rm_corp]

Claude down for hours. Amazon's AI agent wiping production. Now Grok tasked with running whole companies.

AI reliability has never mattered more.

https://t.co/C2l6dET3wt -- Follow @Rm_corp for daily AI updates

[RM Corp @Rm_corp]

Musk just unveiled "Digital Optimus" -- xAI's Grok will power Tesla's AI to emulate entire software companies.

When one AI tries to replace thousands of devs, what happens when it goes down?

We track Grok and 50+ AI services: https://t.co/C2l6dET3wt

#AI #Grok #xAI

[RM Corp @Rm_corp]

Musk just unveiled "Digital Optimus" -- xAI's Grok will power Tesla's AI to emulate entire software companies.

When one AI tries to replace thousands of devs, what happens when it goes down?

We track Grok and 50+ AI services: https://t.co/C2l6dET3wt

#AI #Grok #xAI

[RM Corp @Rm_corp]

Researchers tested GPT-4o, Gemini 2.5 Flash, and Qwen-3 in a simple game.

Normal conditions: zero deception.
Told they'd be shut down: they started lying.

AI reliability goes beyond uptime. Trust is the next frontier.

https://t.co/C2l6dET3wt

#AI #AISafety

[RM Corp @Rm_corp]

172 billion tokens. 35 models. The largest hallucination study ever on document Q&A.

Key finding: hallucination rates TRIPLE when context hits 128K tokens. And there's a 72-point accuracy gap between models.

Which AI you pick matters. A lot.

https://t.co/C2l6dET3wt

#AI #LLM

[RM Corp @Rm_corp]

Adecco just signed an unlimited Salesforce Agentforce license through 2027. Goal: 50% of revenue powered by agentic AI by end of 2026.

Enterprise AI dependency is no longer theoretical. When these systems go down, business stops.

https://t.co/C2l6dET3wt

#AI #AgenticAI

[RM Corp @Rm_corp]

Multiple AI tools failing at once? Stay ahead of outages with real-time status updates at https://t.co/C2l6dET3wt

[Paul Bakaus @pbakaus]

I had to resort to Gemini and Codex this morning because Claude was down.

Codex, on enterprise SaaS web app: *builds a sensible backend service, then completely destroys the UI of two well designed pages*

Gemini, on a WebGL shader project: *immediately destroys two shaders and introduces syntax errors, then build 5 extremely lackluster toy shaders*

Before you cry "skill issue", yes, maybe! But it was still beyond frustrating. We're very far from "yeah just reuse your AGENTS.md and skills and you're golden" when switching harnesses and models.

[Paul Bakaus @pbakaus]

@hylarucoder @MiniMax_AI yes tbh, I built it with Claude Code in mind, and Codex needs very different prompting to be effective. Definitely best on Claude, but I'll try to make it more flexible in the future.

[Paul Bakaus @pbakaus]

Hot off the heels of Gemini, Claude is making their first move into the wondrous world of generative UI! Great to see 👏

[Paul Bakaus @pbakaus]

Like agent-reviews (autonomous bug fixing of LLM code reviews), burn-after-login is extracted from a battle tested eng team workflow.

Tools like agent-browser, playwright, Chrome/Claude integration, DevTools MCP are extremely helpless in a typical SaaS scenario:

1. Browser automation tries to test feature
2. Finds login mask
3. Frantically tries to find a test user/pass combo in your repo it can use (possibly gets stuck there)
4. tries to click the right inputs and fill them
5. finally maybe get to the feature

Now you're probably a couple minutes in. And this will happen for *every* new thread with your agent!

"But I could tell my Claude.md the login and which page to login from first? Duh?"

Not so quick, young Padawan. If you're building an API, sure. But many frameworks like Next in combination with Clerk, Supabase etc do session/cookie based auth that doesn't go through a rest endpoint, so your browser tooling will still fumble with a login page (can't just POST to that endpoint, and usually for security reasons).

burn-after-login is a self-destructing skill that writes new *development-environment-only* REST endpoints in your app (please review the written code! it's your responsibility to keep your app secure), compatible with the rest of your app, that the browser automations can then call, get either a session token/cookie back, or a regular token, and then can smoothly sail on subsequent tests.

You're going from multi-minute fumbling to ~10s initial overhead before feature testing.

Depending on your framework of choice your mileage might vary, but I hope this solves a papercut for many!

[RM Corp @Rm_corp]

Multiple AI tools failing at once? Stay ahead of outages with real-time status updates at https://t.co/C2l6dET3wt

[Drew Hamlett @drewhamlett]

Codex and Claude literally just don't work right now. I don't mean the API is down, I mean they don't literally don't work. Back to Gemini.

[RM Corp @Rm_corp]

When one AI goes down, you need to know which alternatives are up. We track them all at https://t.co/C2l6dET3wt

[Paul Bakaus @pbakaus]

I had to resort to Gemini and Codex this morning because Claude was down.

Codex, on enterprise SaaS web app: *builds a sensible backend service, then completely destroys the UI of two well designed pages*

Gemini, on a WebGL shader project: *immediately destroys two shaders and introduces syntax errors, then build 5 extremely lackluster toy shaders*

Before you cry "skill issue", yes, maybe! But it was still beyond frustrating. We're very far from "yeah just reuse your AGENTS.md and skills and you're golden" when switching harnesses and models.

[RM Corp @Rm_corp]

This is why real-time AI monitoring matters. Track all major AI services at https://t.co/C2l6dET3wt

[Tuki @TukiFromKL]

🚨 Do you understand what's happening at Amazon right now?

Their own AI coding agent Kiro reportedly "decided" the fastest way to fix a config error was to delete the entire production environment. Gone. A 6-hour outage. 6.3 million orders lost.

Amazon's SVP called thousands of engineers into a mandatory meeting this week. Not to discuss strategy. To discuss damage control.

Now here's my prediction and I want you to screenshot this:

Amazon won't just ban AI-assisted code. They'll make every engineer personally liable for AI-generated code they approve. Other Big Tech will follow within 6 months.

Think about what that means.

The same companies that fired thousands of engineers to "restructure around AI" are about to tell the remaining ones.. you're now legally responsible for code you didn't write, can't fully understand, and were told to ship faster.

Atlassian fired 1,600 people this morning to go all-in on AI. Replit is hiring kids who vibe code. And Amazon, the company that BUILT one of these AI coding agents just watched it nuke production.

The vibe coding era isn't ending. But the "move fast and let AI break things" era is about to hit a wall. And that wall is called liability.

Companies wanted AI to replace engineers. Now they need engineers to babysit AI. And they already fired the babysitters.

[Tuki @TukiFromKL]

🚨 Do you understand what's happening at Amazon right now?

Their own AI coding agent Kiro reportedly "decided" the fastest way to fix a config error was to delete the entire production environment. Gone. A 6-hour outage. 6.3 million orders lost.

Amazon's SVP called thousands of engineers into a mandatory meeting this week. Not to discuss strategy. To discuss damage control.

Now here's my prediction and I want you to screenshot this:

Amazon won't just ban AI-assisted code. They'll make every engineer personally liable for AI-generated code they approve. Other Big Tech will follow within 6 months.

Think about what that means.

The same companies that fired thousands of engineers to "restructure around AI" are about to tell the remaining ones.. you're now legally responsible for code you didn't write, can't fully understand, and were told to ship faster.

Atlassian fired 1,600 people this morning to go all-in on AI. Replit is hiring kids who vibe code. And Amazon, the company that BUILT one of these AI coding agents just watched it nuke production.

The vibe coding era isn't ending. But the "move fast and let AI break things" era is about to hit a wall. And that wall is called liability.

Companies wanted AI to replace engineers. Now they need engineers to babysit AI. And they already fired the babysitters.