SLA Evidence
Explore provider evidence while the sample grows. SLA comparisons also require a published target and a direct source.
Source-attested sample rebuilding · no records currently meet this view's publication floor
Evidence you can explore now
1,829 vendors with a verified current provider check. A fresh check shows source coverage; it does not qualify a reliability rating or prove every customer is unaffected.
What this view needs before ratings appear
Each 30-day comparison needs at least 576 verified hourly observations. A 90-day percentage needs 1,728. SLA evidence also needs the provider's published numeric target and a direct source link.
Unverified and legacy records do not count toward these requirements. There is no promised publication date: missing observations and unmatched notices can extend the wait.
Recently checked providers
Sample of 12 verified current checks, listed alphabetically. Open a service to inspect its source, observation history and community reports.
- 100msChecked Sep 17, 09:55 UTC
- 10WebChecked Sep 17, 09:55 UTC
- 17hatsChecked Sep 17, 09:55 UTC
- 1PasswordChecked Sep 17, 09:55 UTC
- 360LearningChecked Sep 17, 09:55 UTC
- 42CrunchChecked Sep 17, 09:55 UTC
- 6senseChecked Sep 17, 09:55 UTC
- 7shiftsChecked Sep 17, 09:55 UTC
- 8baseChecked Sep 17, 09:55 UTC
- ABBYYChecked Sep 17, 09:55 UTC
- ABC TrainerizeChecked Sep 17, 09:55 UTC
- AblyChecked Sep 17, 09:55 UTC
Recent provider incident evidence
- Imperva: Degradation of performance in Imperva Management ConsoleNotice dated Sep 17, 2026 · Official provider source
- SendGrid: SMS Delivery Delays from Twilio to H3G United KingdomNotice dated Sep 17, 2026 · Official provider source
- Twilio: SMS Delivery Delays from Twilio to H3G United KingdomNotice dated Sep 17, 2026 · Official provider source
- Coinbase: Degraded Performance - Prediction MarketsNotice dated Sep 17, 2026 · Official provider source
- Bullhorn: Bullhorn Back Office - Unable to Send OnboardingNotice dated Sep 17, 2026 · Official provider source
Publication standard for SLA evidence
We publish an SLA target only when the service catalog contains both an explicit numeric target and a direct public source URL. We do not infer a generic target from provider size or status-feed type. Any comparison is against aggregate status-page observations and is not a determination of contractual compliance or customer eligibility for service credits.
No record is better than an unsourced claim. See status reliability observations and methodology and limitations.