Rewindex

RewindexScorecards

How vendors report incidents

For the 152 vendors with enough history to compare: how often the first post said “resolved”, how long incidents last, how many are major, and which incidents they rewrote or deleted. Built from every archived version of their status pages.

Provisional. Updated nightly, last on Oct 19. Lower is better in every column; select a column to put the highest first.

Typical vendor: 6% posted after it was over, 2 h to resolve, 1.2 major incidents a month.

VendorPosted only after it was overTime to resolveMajor a monthRewrites caught
ActiveCampaignmartech0% 0 of 502 h 27 min1.2none
Brazemartech14% 7 of 501 h 12 min0.7none
Brevomartech6% 2 of 3245 min1.6none
Buffermartech9% 2 of 231 h 20 min2.7none
Hootsuitemartech22% 11 of 501 h 48 min1.4none
HubSpotmartech6% 3 of 501 h 20 min0.0none
Klaviyomartech6% 3 of 502 h 3 min1.2none
Mailgunmartech8% 4 of 501 h 29 min0.8none
Optimizelymartech8% 4 of 504 h 54 min2.0none
Sprout Socialmartech2% 1 of 5117 h 2 min0.3none
Squarespacemartech4% 2 of 491 h 27 min2.0none
SurveyMonkeymartech8% 4 of 501 h 53 min1.4none
Webflowmartech12% 6 of 502 h 32 min0.7none
Wixmartech2% 1 of 4940 min1.3none

Built nightly from every archived version of each vendor’s status page (rwx_api.vendor_reliability). Comparable vendors have >= 20 incidents in 365 days and >= 10 with full update detail; vendors that share one status page are compared once. Time-to-acknowledge, late-post and backdated rates are left out because they follow each status platform’s start-time convention. Rewrites are counts since 10-minute tracking began on 2026-10-17. Provisional. 174 more vendors are not compared yet.

MarkdownJSON