Operations | Monitoring | ITSM | DevOps | Cloud

It's been a while since I last updated you on what's new in OnlineOrNot. For the most part, I've continued making it useful for software teams: there's now an MCP server, I've improved the terraform provider significantly, and there's a new TypeScript SDK. You can also (finally?) monitor DNS/TCP with it.

Last month I focused on adding Telegram alerts to OnlineOrNot, making scripted browser checks generally available, and making it clearer to understand why checks fail.

February was all about making OnlineOrNot better for dev teams. I shipped audit logs for teams, added support for two-factor authentication and passkeys, unified the webhooks system across uptime checks, heartbeats, and status pages, and made it possible to connect multiple Discord channels.

Hopefully this will be one of the last major "behind-the-scenes" updates for a while, because OnlineOrNot's frontend now runs on a React framework that's easy to deploy across multiple providers, and is fully off GraphQL, being powered by its own REST API.

Continuing on with the tradition I started to wrap up 2024, in this article I'll go over what's new in OnlineOrnot from 2025.

On 2025-11-18 at 11:48 UTC, Cloudflare declared an incident affecting the global network (that also affected OnlineOrNot). OnlineOrNot monitors websites, APIs, web apps, and cron jobs, while providing status pages as well. While we partially mitigated the issue by enabling a fallback to AWS-based monitoring, between 13:00 UTC and 14:33 UTC failing checks went unreported, heartbeat checks over-reported, and status pages were unavailable.

A bit more behind-the-scenes work than usual this month, but I still managed to ship some public-facing features you might be interested in. Logging in, and clicking around the dashboard just got 60% faster, and we're just getting started.

In this latest update, I'll walk you through a few features I added that will make working with uptime checks less noisy, an alerts integration with Teams, and a few behind-the-scenes changes that will finally let me build mobile apps for OnlineOrNot.

As OnlineOrNot has grown, I've been building features quickly to get them into your hands as fast as possible. However, this meant I ended up with multiple versions of similar pages that looked and worked differently from each other. This month, I focused on putting systems in place to create a consistent experience across all parts of the dashboard, making everything look and feel unified.

In April I worked on a behind the scenes refactor, webhooks for status pages, a new endpoint, and more.