Skip to main content

Know what’s
upstream.

Find the vendors your code depends on. When one reports an incident, see which projects to investigate.

Get startedSee how it works

Free to start. No credit card required.

GitHub GitLab

Connect a public or private repository.

Example: one project, three vendors.

From our vendor catalog

Explore vendor data

Connect a repository

Start with
your code.

Create your account and connect a public or private repo. The scan turns known dependencies into a vendor list to review.

Get started

Free to start. No credit card required.

CheckUpstream Illustrative example
Illustrative repository scan and matched vendors
web-app / package.json
{
  "dependencies": {
    "stripe": "*",
    "@supabase/supabase-js": "*",
    "resend": "*"
  }
}

Matched dependencies

  • StripePayments
  • SupabaseDatabase & auth
  • ResendEmail

Review the vendor matches.Confirm where this app uses them.

Follow vendor incidents

Know where
to investigate.

When Stripe reports API errors, find the projects with a Stripe dependency. Start with the calls that use it.

See the vendor records

Alerts follow the vendors connected to your project.

CheckUpstream Illustrative example
Illustrative vendor incident linked to a project

Stripe reports API errors.

Stripe
web-app

A project to investigate

Check your app’s calls next.A vendor report doesn’t confirm app impact.

Application telemetry / Optional SDK

Did it affect
your app?

A vendor incident doesn’t tell you what happened to your app. The optional SDK shows whether your outbound calls slowed down or failed.

See how the SDK works
Illustrative requestChoose an outcome

Success / This example

Stripe responded to this call.

With the SDK

Compare response times and failures across your Stripe calls to check the wider impact.

SuccessMeasure how long successful calls take.

Slow responseSpot delays even when calls still succeed.

TimeoutRecord failed calls when a vendor doesn’t respond.

Keep the sources
web-appIncident file

Stripe
API errors.

  • Vendor incident timeline
  • Request errors and latency
  • Our outside checks, with times
Example incident file · Illustrative.

Evidence, not estimates

Keep the evidence
with the incident.

The vendor’s own timeline, in its words and times, sits next to our outside checks and, with the optional SDK, what your requests saw. No uptime percentages, credit estimates or recovery predictions.

If your contract includes an SLA, its terms and the vendor decide whether an outage qualifies for a credit.

What a vendor’s SLA covers

Read your vendor’s published terms

Open vendor data

Check the data
for yourself.

Look up a vendor’s history and check the sources behind it. No account needed.

How we collect the data

Vendor directory / 232 services

View all

Recent recorded incidents

All records

These are dated records. Open a vendor to check its current status.

Status reports What vendors are reportingReliability history Measurements and coverageSources & methodology Where the data comes from

Setup, coverage & limits

Before you
connect.

Getting started guide
What does the free repo scan tell me?

It maps known packages in your repository to external services, giving you a list of vendors to review and monitor. It works with public and private repos. The scan can miss custom API integrations and cannot confirm which packages run in production.

Can I scan public and private repositories?

Yes. Create an account with GitHub or GitLab, then link a public or private repository during setup. Connecting the repo starts its scan. Your account is created on first sign-in.

What is included in the free monitoring plan?

Two projects, five monitored services, one team member, email alerts and seven days of incident history. No credit card required. Paid plans add team capacity and other alert channels; Pricing has the full comparison.

Does an alert mean my product is down?

Not necessarily. It tells you which projects depend on a vendor with an incident. Optional SDK telemetry adds your request errors and latency to help check whether your app is affected.

Do you calculate SLA credits?

No. A credit depends on your contract, plan, billing period, exclusions and evidence, and the vendor decides whether an outage qualifies. CheckUpstream keeps the vendor’s own incident timeline and the checks we record with each incident. It does not estimate uptime, credits or recovery times.

Which services and dependency files are covered?

The catalog maps 232 services across 25 package ecosystems. Detection and measurement coverage vary by service. The public vendor pages show the available data and whether independent measurements exist.

Start with your repository

See what your
code depends on.

Connect GitHub or GitLab and scan a public or private repo.

Get startedFree to start. No credit card required.

Free includes 2 projects, 5 monitored services and email alerts. Compare plans