Inngest Status Monitoring
queues
DepsDown automatically detects Inngest in your codebase and monitors its status page for outages. Get instant alerts via Slack, email, or webhook when Inngest reports incidents — so you know immediately if the problem isn't your code.
How we detect Inngest
When you connect your GitHub or GitLab repository, DepsDown scans for these patterns to identify Inngest as a dependency:
Package
inngest
Found in: package.json
Env Variable
INNGEST_EVENT_KEY
Found in: .env
Env Variable
INNGEST_SIGNING_KEY
Found in: .env
What happens when Inngest goes down
We poll every 2 minutes
DepsDown checks Inngest'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 Inngest has an incident, you'll know immediately — saving hours of investigation.