What each issue contains
- The disruptions SutramX confirmed that month, longest first: the vendor (or AWS region), the start time in UTC, how long it lasted, whether it looked degraded or like a likely outage, the probe regions that saw it and the kind of failure (timeouts, 5xx errors, connection or TLS failures).
- How many disruptions each category had (payments, cloud, developer tools and so on), when there were enough to compare.
- How many of them the vendor's own status page also reported.
- How many tracked vendors SutramX had enough checks for. A vendor with too few checks is not called healthy.
- A short summary built by fixed rules from those numbers. No AI writes it, and nothing is added that the data does not show.
If a month has too little data to compare vendors, the issue says so and stops there.
Where the data comes from
From SutramX live vendor status. A disruption counts when checks of the same vendor failed for at least 3 different customer accounts at once, seen from 2 or more probe regions or vendor hostnames. Size is shown as “several” or “many” accounts, never an exact number, and no customer, monitored URL or response time is ever named. It is not the vendor's official status page.
Your address
We send a confirmation link first and add nobody who does not click it; unconfirmed addresses are deleted after 7 days. SutramX customers are not added automatically. Every issue has a one-click unsubscribe link. Details are in the privacy policy.
Past issues
No issue has been sent yet. The first one covers a full calendar month.