Building a service status notifier with .NET and Cloudflare Workers

Ludde — Fri, 06 Nov 2026 12:49:38 +0000

I've been working on a small side project recently.

Like most developers I depend on quite a few external services. GitHub, Cloudflare, OpenAI, and others.

When something breaks, I usually end up checking their individual status pages to figure out what's going on.

I wanted a simpler way to keep track of these incidents and get notified in Slack without having to configure every provider separately.

So I started building https://StatusRelay.dev.

Why build another status monitoring tool?

Of course, tools like this already exist, and they offer much more comprehensive solutions.

I wasn't trying to reinvent everything they do. I just wanted something lightweight where I could select the services I care about, connect a Slack channel or webhook, and start receiving notifications.

No accounts, no paid plans, and no complicated setup.

It also seemed like a fun opportunity to experiment with event processing, background jobs, and reliable notification delivery.

But how does it work?!

The idea is pretty straightforward:

Poll official status APIs from different providers.

Normalize their status and incident information.

Store incidents and detect changes.

Send notifications to Slack or custom webhooks.

The backend uses .NET 10 with PostgreSQL. An Azure Container Apps job handles polling, while Cloudflare Workers handles subscriptions, the frontend and notification delivery.

Currently, it supports ~36 providers.

I initially thought fetching status information would be the easy part.

But not every provider exposes incidents in the same way.

Some use Atlassian Statuspage, others have completely different formats. Some feeds provide detailed incident updates, while others give you very little information.

Another interesting problem is handling stale data and irrelevant updates.

If a provider's status API stops responding, should the dashboard continue showing green based on the last successful check?

I decided it shouldn't. Once the data gets too old, the status is marked as unavailable rather than assuming everything is operational.

Notifications introduce their own challenges too. You dont want to send duplicate messages every time you poll an API. You need to track incident changes, handle delivery failures and avoid replaying old incidents to new subscribers.

How far have I come?

The project is up and running, and I've been testing Slack and webhook notifications.

It relies on official provider status feeds, so it's not an independent uptime monitor. That's an important limitation.

There's still plenty to improve, particularly around how incident updates and notifications are handled.

If you're curious, you can check it out here:

https://statusrelay.dev

How do you monitor incidents across external services? Do you use a dedicated service, individual status subscriptions, or something you've built yourself?

DEV Community: Ludde

Building a service status notifier with .NET and Cloudflare Workers