Wasabi Status Monitoring
Storage
DepsDown automatically detects Wasabi in your codebase and monitors its status page for outages. Get instant alerts via Slack, email, or webhook when Wasabi reports incidents — so you know immediately if the problem isn't your code.
How we detect Wasabi
When you connect your GitHub or GitLab repository, DepsDown scans for these patterns to identify Wasabi as a dependency:
Env Variable
WASABI_ACCESS_KEY
Found in: .env
Env Variable
WASABI_SECRET_KEY
Found in: .env
What happens when Wasabi goes down
We poll every 2 minutes
DepsDown checks Wasabi's official status page every 2 minutes for incidents, degraded performance, or outages.
Instant alerts to your team
When a status change is detected, we send alerts to your configured channels — Slack, email, or webhook — within minutes.
Know it's not your code
Stop debugging blindly. When Wasabi has an incident, you'll know immediately — saving hours of investigation.