Your private incident feed
Your feed address is worked out from two things: the email you check out with, and an access code. Your browser does the maths; neither box is ever sent to us — there is no server here to send it to.
Before you buy — generate your access code
Do not invent this code. A code a person could think up can also be guessed by someone who knows your billing email, and guessing it would show them which vendors your company depends on. This button draws 130 random bits from your own browser, which cannot be guessed.
After you buy — find your feed address
Point your channel at it
Three platforms, three genuinely different mechanisms. Use the one that matches yours.
- Slack — in the channel you want the alerts in, type
/feed subscribe <your feed address>. That command is built into Slack; nothing to install. - Microsoft Teams — open the Workflows app, choose the template “Post to a channel when an RSS feed is published”, and give it the address. The old Teams connector route is gone: Microsoft retired Office 365 Connectors in Teams in May 2026.
- Discord — Discord has no built-in RSS subscription, so this is the one platform that needs a third-party piece: any free RSS-to-Discord bot (MonitoRSS is the usual one) will post it.
- Anything else — it is plain RSS 2.0. Feedly, Inoreader, Thunderbird, NetNewsWire, or six lines of your own code all read it.
Not a buyer yet? Open the live sample feed — real incidents, same format, rebuilt daily.
What is in the feed, and what is not
- One entry per opened, updated or resolved incident on the vendors you named, within five minutes of the vendor publishing it.
- One entry when a vendor's status page becomes unreadable — reported as cannot see, never as OK — and one when it is readable again.
- One daily check-in listing every watched vendor's current state, so a quiet feed is provably a working feed.
- No credential of yours, anywhere. We never asked for a webhook, so we cannot leak one.
The address is derived with PBKDF2-HMAC-SHA256 at 600,000 rounds, in your browser, over your email and your access code. Because the code carries 130 random bits, guessing it is not a route in even for someone who knows your billing email. The resulting address is still a bearer URL — anyone you forward it to can read it — so treat it like a calendar-sharing link. Lost it? Come back here — the same two answers always produce the same address. Vendor Status Watch · Privacy · Terms and refunds