Operations | Monitoring | ITSM | DevOps | Cloud

When SendGrid goes down, your transactional emails stop reaching customers. Password resets fail. Order confirmations vanish. Support tickets never arrive. By the time you notice, customers are already complaining. For DevOps and SRE teams, checking SendGrid status shouldn't be a manual process. It shouldn't wait until customers report it either. For a team sending 10,000 transactional emails per day, a 15-minute outage means roughly 100 emails that never arrived.

We’ve made a small but important improvement to API tokens in StatusGator. API tokens now support permission levels. When creating a token, you can choose between: That’s it. A simple change that gives you more control and better security.

We’ve added service status page ratings to API v3. You can now access the same letter grades, descriptions, and average acknowledgment delay metrics that appear on StatusGator service pages – directly from the API.

On February 19, 2026, Trello users around the world began experiencing issues loading boards and accessing their workspaces. StatusGator received the first outage reports at 14:24 UTC and triggered an Early Warning Signal at 14:28 UTC. Trello did not officially acknowledge the incident until 15:08 UTC, after user reports had already subsided. This incident highlights how real time user reports and Early Warning Signals can identify widespread service degradation before providers confirm a problem.

On February 17, 2026, YouTube went down for users worldwide. Starting around 8:00 PM ET, the platform's homepage, Shorts feed, sign-in system, smart TV apps, YouTube Music, and YouTube Kids all stopped working. Over 21,000 reports were logged on IsDown alone. The error message was the same everywhere: "Something went wrong." For consumer users, it was an inconvenience. For businesses that depend on YouTube — content teams, advertisers, media companies, live streamers — it was a blind spot.

We’ve made another improvement to the StatusGator API based directly on customer feedback. Many teams are managing monitors programmatically, and one recurring request was the ability to fully manage monitor cleanup via API. You can now delete all monitor types through the API.

We shipped a small improvement to monitor filtering to make it easier to stay organized — especially if you’re managing a board with a lot of monitors.

On February 10, 2026, Amazon Web Services (AWS) experienced an outage that triggered widespread reports of CloudFront failures and DNS resolution issues. While AWS later acknowledged the incident, StatusGator detected the disruption earlier using Early Warning Signals, giving customers valuable lead time before the provider confirmed anything publicly.

On February 10, 2026, Claude users around the world began reporting service failures affecting chat sessions, API integrations, and Claude Code workflows. The first verified outage report reached StatusGator at 19:33 UTC. StatusGator issued an Early Warning Signal at 20:24 UTC. Claude did not post an official “Investigating” update until 22:11 UTC. This incident clearly demonstrates the gap between real user impact and official status page updates.