OpenedFilesView VS OutageDeck

I built OutageDeck because I got tired of opening a dozen browser tabs every time something broke, trying to work out whether the problem was mine or somebody else's.

It watches the status pages that 172 cloud and SaaS companies publish about themselves. AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, Vercel, and a long tail of others. Every ten minutes it reads what each one is saying and puts it all in one place, so answering "is it us or them" takes seconds instead of twenty minutes. When something does break, it tells you where you already are: Slack, Teams, Discord, email, or your own webhook.

One rule I set early and haven't bent: official sources only. Nothing scraped, nothing crowdsourced, no probing from my own servers. If a vendor hasn't said it, OutageDeck doesn't say it either. That means fewer vendors than the aggregators that scrape everything. It also means that when you get an alert, something is genuinely wrong.

The other thing that kept bothering me is how fast the evidence disappears. A vendor resolves an incident, the banner comes down, and six weeks later you're writing a postmortem with nothing to point at. So OutageDeck keeps it. Uptime history and incident timelines stay where you left them, and every entry links back to the vendor's own page.

If you depend on something I don't track, paid plans let you point it at any Statuspage or Instatus page yourself, and it shows up privately in your account like everything else.

For developers there's a JSON API with no account and no key, an OpenAPI 3.1 spec, RSS feeds, README status badges, and an MCP server so a coding agent can check whether a vendor is down before it starts tearing apart your code.

Email alerts for five vendors are free, no card needed. Paid plans start at $19 a month and add the other channels, unlimited vendors, and your own feeds.

Built and run by Kerolos Atallah, a developer in Cairo. Not affiliated with any of the companies it tracks.

Questions & Answers

As answered by people managing OpenedFilesView and OutageDeck.

Which are the primary technologies used for building your product?

OutageDeck's answer:

Frontend / app: Next.js 16 (App Router), React 19, TypeScript, Tailwind CSS
Data: Supabase Postgres. Every upstream feed is validated with Zod, so provider format drift fails loudly instead of corrupting data
Ingestion: each vendor's official feed polled every 10 minutes, with per-provider failure isolation, so one broken feed never blocks the rest
Alerting: a delivery ledger with exactly-once claims, so overlapping runs never double-page anyone

What makes your product unique?

OutageDeck's answer:

OutageDeck only reports what vendors officially publish. Every status comes from the provider's own machine-readable feed, never crowd reports and never scraping. Then it holds vendors to what they said:

Independent uptime history, with honest partial and regional impact framing
Every incident links back to its source on the vendor's own status page
One dashboard for 172 vendors, with alerts to Slack, Teams, Discord, email, or webhooks
Bring your own feed on paid plans: point it at any Statuspage or Instatus page it does not track yet
A JSON API, RSS feeds, README badges, and an MCP server so a coding agent can check the vendor before it blames your code

What's the story behind your product?

OutageDeck's answer:

I got tired of opening a dozen vendor status pages during every incident, just to work out whether the problem was mine or somebody else's. So I built the thing I wanted.

It launched in July 2026 as one live board over the official status feeds of the vendors teams actually depend on. The catalog is at 172 now: AWS, Cloudflare, GitHub, OpenAI, Google Cloud, Slack, Twilio, and a long tail of others.

The rule from day one: official machine-readable sources only. No crowd reports, no scraping. If a status can't be traced back to the vendor's own feed, it doesn't get published.

How would you describe the primary audience of your product?

OutageDeck's answer:

Anyone whose incident channel regularly starts with "is AWS down, or is it just us?":

DevOps, SRE, and platform engineers. Answer "is it us or them?" in seconds during an incident.
Small SaaS teams. Your uptime depends on other people's clouds, so know before your customers tell you.
Agencies and MSPs. Watch the vendor stacks of many clients from one place.

Why should a person choose your product over its competitors?

OutageDeck's answer:

Three reasons.

Pricing. Paid plans start at $19 a month flat with unlimited vendors, while most alternatives meter by "monitors" and get expensive as your stack grows. The free tier is genuinely useful: email alerts for up to 5 vendors, no card.
Honesty. Official sources only means you never get paged over a rumor. Statuses, uptime history, and incident timelines all trace back to the vendor's own feed.
Developer surface. A JSON API you can call without an account, RSS feeds, README status badges, and an MCP server for coding agents. No login gate on any of it.

What are some alternatives?

When comparing OpenedFilesView and OutageDeck, you can also consider the following products

LockHunter - It is a free tool to delete files blocked by something you do not know.

StatusGator - Early outage alerts for every app you rely on

FileASSASSIN - FileASSASSIN is an application that can delete any type of locked files that are on your computer.

IsDown.app - When a vendor goes down, does your team find out in seconds or after users start complaining? IsDown monitors 6,000+ official status pages and alerts your team within seconds across Slack, PagerDuty, Datadog, and more. 14-day free trial

DelinvFile - Use DelinvFile to delete files and folders with invalid names that cant be deleted or renamed via...

IncidentHub - Real-Time Vendor Monitoring That Actually Works

Compare OpenedFilesView VS OutageDeck and see what are their differences