Skip to main content

Changelog

What’s changed at CheckUpstream.

Product updates, in date order. Follow the releases here or add the feed to your RSS reader.

Subscribe with RSS

For setup instructions, use the documentation. Check SDK availability before installing.

Latest entry

Vendor records and SLA guides

Review recorded vendor history, follow incident updates and find the evidence a potential SLA claim needs.

  • Vendor records. Browse status reports and reliability records for a vendor. Dates and source labels help you interpret each record.

  • Incident history. Open the incident feed to find dated vendor reports and their latest recorded updates.

  • SLA claim guides. Use vendor guides to review tracked terms, evidence requirements and filing routes. Check the applicable contract before submitting; the vendor decides eligibility.

Status badges and a sample workspace

Share vendor status in your docs and explore sample projects before connecting your own code.

  • Embeddable status. Choose a vendor and copy an image, Markdown or iframe from the badge builder.

  • Sample workspace. A separate demo organization provides sample projects and vendor connections to explore. These examples do not describe your application.

  • Platform activity. The platform status page shows the latest recorded vendor checks, SDK telemetry and outage signals, with timestamps and measurement limits.

CheckUpstream public launch

Connect a public or private repository to find vendor dependencies and review your alert settings.

Create an account, connect GitHub or GitLab and choose a repository. Review the matched vendors and your alert settings. A vendor report gives your team somewhere to investigate; it does not establish that your application had an outage.

Follow the repository setup guide or compare plans for current limits.

Find vendor imports in your code

Repository scans can connect package matches to the files that import them.

Import analysis follows supported imports and wrappers to help you review vendor connections. A match is a lead to investigate, not confirmation that a package runs in production.

Selected source files can be stored in full. Read how scans handle repository data before connecting a repository.