I made a gh extension that reads your repo before checking dependency status
▲ 2 r/git+2 crossposts

I made a gh extension that reads your repo before checking dependency status

During a GitHub outage I realized my first CLI interface was backwards. It asked people to remember provider slugs even though the repository already knew what it depended on.

So I changed it. gh outagedeck stack now scans manifests, infrastructure files, workflows, and git metadata, explains which files caused each match, then checks those providers' public status. It skips dependency and build directories. Detection stays local, and only provider slugs leave the machine.

On my own repo it found GitHub, Vercel, and Supabase from .git, workflow files, vercel.json, package.json, and the lockfile.

Install and run:

gh extension install outagedeck/gh-outagedeck

gh outagedeck stack

Repository: https://github.com/outagedeck/gh-outagedeck

It was just added to the community awesome-gh-cli-extensions list, which was a nice sign that the interface made sense outside my own terminal.

I'm Kerolos, founder of OutageDeck. The extension is open source. I would love examples of unusual manifests it misses or false positives it creates. Those are more useful than polite feedback.

github.com
u/Nervous-Honey-2695 — 7 days ago

My Keybase proof [reddit:nervous-honey-2695 = keybase:koko3tallah] (6VxjEC534C7TMk8tHEaRPHh6pH_CxnMFIsQn3g4APf8)

Keybase proof

I am:

Proof:

hKRib2R5hqhkZXRhY2hlZMOpaGFzaF90eXBlCqNrZXnEIwEgDtKMeF2bkgelh4ewCK2Yo/NHazgkH3bdmTLdxq5dA3EKp3BheWxvYWTESpcCCMQgISO5y5NsoqPIDZ3/BEiTk07UzBU75B7ZWSfnvVjd0ALEIMYLOungqDTA0jz3cvFWc+p8pcn/CjbHhcN/rVn3A4QUAgHCo3NpZ8RA+NTYlCvV29b9E626Qnw48ugAcQfOmjZlDTjqzRmBC9FBpN5Or2MDf1qNts2tAn16rquGX21pEYE3wVhB8c+iAahzaWdfdHlwZSCkaGFzaIKkdHlwZQildmFsdWXEIDOC2CfWlfatuF7fYv9fK6og7DTbWwznlr1df52v15bNo3RhZ80CAqd2ZXJzaW9uAQ==
reddit.com
u/Nervous-Honey-2695 — 10 days ago

My Keybase proof [reddit:nervous-honey-2695 = keybase:koko3tallah] (6VxjEC534C7TMk8tHEaRPHh6pH_CxnMFIsQn3g4APf8)

Keybase proof

I am:

Proof:

hKRib2R5hqhkZXRhY2hlZMOpaGFzaF90eXBlCqNrZXnEIwEgDtKMeF2bkgelh4ewCK2Yo/NHazgkH3bdmTLdxq5dA3EKp3BheWxvYWTESpcCCMQgISO5y5NsoqPIDZ3/BEiTk07UzBU75B7ZWSfnvVjd0ALEIMYLOungqDTA0jz3cvFWc+p8pcn/CjbHhcN/rVn3A4QUAgHCo3NpZ8RA+NTYlCvV29b9E626Qnw48ugAcQfOmjZlDTjqzRmBC9FBpN5Or2MDf1qNts2tAn16rquGX21pEYE3wVhB8c+iAahzaWdfdHlwZSCkaGFzaIKkdHlwZQildmFsdWXEIDOC2CfWlfatuF7fYv9fK6og7DTbWwznlr1df52v15bNo3RhZ80CAqd2ZXJzaW9uAQ==
reddit.com
u/Nervous-Honey-2695 — 10 days ago
▲ 5 r/devops

Seaking genuine advice

So I've been a software engineer focused on the backend for almost 10 years now, at the beginning of this year I faced a small bump and found needed solutions are paid, so did myself a favour and build myself a tool, and used it for a month, then thought wth, why don't I go public with it, it didn't have any interface at the beginning, so I started building and iterating a lot, and like a lot, to the point it's not advised to do so with a product on an MVP phase, and now I've reached a state where I believe I'm a head of my competitors (hopefully I'm not delusional)

And then nothing, I've been online for a month now, and I've very low traffic, my purpose of this is not promoting, therefore I'm not mentioning the product, nor even what it does

My question though, since obviously the product mostly concerns DevOps, what's the best channels you take seriously? And what could get you to try out or shift to something new? Cost a side since I've a full free tier.

reddit.com
u/Nervous-Honey-2695 — 11 days ago

DigitalOcean incident affecting new accounts, Droplets, Reserved IPs, snapshots and DOKS

DigitalOcean's status page says it has identified the root cause of an incident affecting multiple regions.

Reported impact includes:

- new account and Droplet creation

- Reserved IP allocation

- automated backups and snapshots

- Droplet Autoscale and DOKS operations

- GenAI services and the Droplet console

- database clusters stuck in a ‘Creating’ state

The latest official update was at 20:02 UTC and says a fix is being implemented.

Official incident: https://status.digitalocean.com/incidents/2wql4f4sb13r

Normalized live timeline: https://outagedeck.com/incidents/digitalocean-account-registration-droplets-and-related-services-2026-08-08?utm_source=reddit&utm_medium=incident_update&utm_campaign=digitalocean_aug8_outage

Disclosure: I'm the OutageDeck Founder. The second link mirrors DigitalOcean's official provider signal; it is not independent confirmation. Check the systems you actually run with your own probes too.

u/Nervous-Honey-2695 — 12 days ago
▲ 6 r/grafana+2 crossposts

I built a dashboard that checks 172 provider status feeds before I debug my own stack

I'm Kerolos, founder of OutageDeck.

The question I wanted to answer quickly was: is my app broken, or is AWS, Cloudflare, GitHub, OpenAI, Stripe, or another dependency reporting an incident?

I built OutageDeck to read and normalize the official status sources for 172 cloud and SaaS providers. It shows provider and service-level state, current incidents, source freshness, incident history, and 90-day uptime in one place.

What works today:

- check a whole dependency stack without creating an account

- free email alerts for up to five providers

- Slack, Teams, Discord, and webhook destinations on paid plans

- a keyless JSON API, RSS feeds, badges, CLI tools, and an MCP endpoint

- custom Statuspage or Instatus feeds on paid plans

What it deliberately does not do is pretend an official status feed is independent truth. Providers can acknowledge incidents late, so I think a serious production setup should use two signals: the vendor feed plus synthetic probes from your own regions and accounts.

You can try the stack checker here:

https://outagedeck.com/stack?utm_source=reddit&utm_medium=community&utm_campaign=sideproject_provider_monitoring

I would value blunt feedback from people who handle incidents. What would this need to do before you would keep it open or route its alerts into your on-call workflow?

u/Nervous-Honey-2695 — 10 days ago