Why CheckUpstream starts with your dependencies
Map the services in your code, connect vendor incidents to relevant projects, and review the evidence before acting or preparing a claim.
1 min read
The CheckUpstream blog
Engineering,
upstream.
What to check when a vendor fails. How to map your dependencies. And what the evidence can actually tell you.
Browse all articlesDependencies
4 articles
Topic: Dependencies
Clear filtersAlert on impact, not existence
Connect vendor incident reports to relevant projects, then use request evidence to understand application impact.
3 min read
Finding vendor connections in your dependency files
Use dependency files to find possible vendor connections, then review which services your application actually calls.
3 min read
Which dependencies should you monitor?
Choose which vendor failures need a page, which can wait, and what the recipient should do next.
3 min read