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.
CheckUpstream Team
1 min read
Published
Updated
A vendor outage is easier to investigate when you already know which projects depend on that service. CheckUpstream starts with that list.
Start from the repository
The dependency scan reads supported manifests and lockfiles, then matches known packages to external services. For example, a supported payment client can point to a payment provider. The result is a list to review, not proof that every detected package runs in production.
Custom HTTP calls, runtime configuration, and unsupported files may need manual review. Create an account and connect a public or private repository to start a free scan. Review the vendor matches and your alert settings.
Connect incidents to the team’s work
A vendor notification is more useful when it names the projects that depend on that vendor. CheckUpstream brings that dependency context together with incident updates and available measurements.
Your own request telemetry can help establish whether the issue affects your application. Checks against the vendor’s public endpoints provide another view. The methodology explains what each source can establish and where coverage is limited.
Review credit eligibility separately
An outage does not automatically qualify for an SLA credit. Your plan, contract, affected product, billing period, exclusions, and evidence all matter. CheckUpstream does not assess eligibility, estimate credits or prepare claims. It keeps the vendor’s own incident timeline so you can check it against the agreement.
The SLA guide directory lists public terms and documented coverage findings. The pricing page explains the free plan and how to request a paid account.
Editorial correction, September 6, 2026: the earlier introduction included an unsourced origin story and broader detection claims. This version describes the product and its limits directly.
Editorial correction, September 27, 2026: an earlier version said CheckUpstream helps prepare SLA claims. It does not; it records vendor incident timelines and links to the published terms. The same revision removed a reference to public outage reports, which CheckUpstream no longer collects.