1. Add a vendor component
Open Status page settings, find Vendor components, and search the Outages catalog (195 tracked services) for the vendor. Give it a name your visitors recognize, or keep the vendor's own. It appears in your component list like any other component, in any group you put it in.
2. Read what it shows
The status is RealUptime's own probe reading of that vendor, the same verdict its /outages page shows, mapped to operational, degraded, partial outage, major outage, or unknown (third-party) when our probes hold no usable reading. The vendor's own status-page claim sits beside it when we ingest that feed. Visitors see a "Third-party, measured by RealUptime Outages" label with a link to the live measurement.
3. Decide what it may do
By default it does nothing but show: it never opens an incident on your page, and it does not change your page-wide status. Two opt-in toggles, both off until you turn them on: let vendor components pull the page headline to degraded (never down), and email your subscribers when RealUptime confirms the vendor down and again when it recovers.
4. Keep it honest
A vendor outage is information for your visitors, not a statement about your service. The label and the link stay on the row so nobody reads a third party's outage as yours, and when a vendor leaves the catalog the component reads unknown rather than green.
Go deeper
The full reference lives in the docs: Status pages documentation. Error codes named above are each explained in the error-code reference.