Monitor supplier service status
Watch the public status pages of the suppliers you depend on, and hear about their incidents as they happen.
What it is
Most cloud and software suppliers publish a status page where they declare incidents and maintenance. Noru reads those pages for the suppliers you pick, records every incident, and tells you when a supplier you depend on has one. You see each supplier's status now, any incident open now, and its record over the last 90 days: how many major and minor incidents it declared, and the median time it took to resolve them.
Where to find it
SuppliersService statusEach supplier's record also shows its status in the side panel, under Service status, and its recent incidents on the Overview tab.
Key actions
Monitor a supplier
You can also start from the supplier's record: on the Overview tab, click Find status page under Service status.
Find status pages for many suppliers
Choose who gets alert emails
A new monitor emails the supplier's owner. Its alert level follows the supplier's tier: all incidents for critical and high suppliers, major and critical only for medium ones, and off for the rest.
What reaches you
| Where | What | When |
|---|---|---|
| Inbox | A Service incident item to handle or dismiss | A major or critical incident at a critical- or high-tier supplier |
| The incident, its impact, and links to it and to the supplier | Every incident the monitor's alert level covers: when it opens, on each update, and when it is resolved | |
| Webhooks and workflows | A vendor.service_status_changed event | Every incident opening, update and resolution. Maintenance is included only for monitors set to All incidents |
The Inbox item stays until someone decides it, even after the supplier resolves the incident. It says when the incident was resolved at the source, so you can decide whether a finding or a review is needed.
Statuses and fields
| Status | Meaning | Set by |
|---|---|---|
Operationaloperational | The provider reports no problems. | The status page |
Degradeddegraded | A minor incident is open. | The status page |
Partial outagepartial_outage | A major incident is open. | The status page |
Major outagemajor_outage | A critical incident is open. | The status page |
Maintenancemaintenance | Planned maintenance is in progress. | The status page |
Unknownunknown | The page has not been read yet, or says nothing Noru can use. | Noru |
A cloud mark next to the status means Noru could not read the page the last time it tried. The status shown is the last one read, and Noru keeps trying.
Tips and gotchas
Start with your critical and high suppliers: their major incidents are the ones that become Inbox items, and the 90-day record helps when you review them.
Some providers publish only a feed of incidents, not a status with severity. For those, Noru judges the impact from the incident's wording and treats an incident with no update for a day as resolved.
What Noru does not do
- Noru does not test your suppliers' services itself. The status is what the supplier declares on its own page, which can lag behind a real outage or leave one out.
- Noru does not know which parts of a supplier's service you use. An incident in a product you do not buy still counts.
- A resolved incident does not close its Inbox item. A person decides.
Related
Last updated on