30%
Availability
How long your systems were actually available.
Uptime, downtime and incident duration.
B2B Reliability Reputation
Prove your reliability.
Don't just claim it.
Reliability Reputation transforms your operational history into a public, continuously updated signal of how your systems actually perform.
Methodology preview. Scores, profiles and qualification thresholds on this page are illustrative; they are not live customer assessments.
Reliability Profile · example company12 months monitored
Illustrative score · demo data
95.5/ 100
Reliability Reputation
Calculated continuously from monitored operational data.
- Observed availability
- 99.97%
- Incident Response
- 92 / 100
- Transparency
- 96 / 100
- Consistency
- 94 / 100
- Recorded incidents
- 23
- Average acknowledgment
- 4m 12s
- Average resolution
- 18m
- Incident history available
- 100%
All figures are illustrative. This is not a live company profile or an assessment of a customer.
01The problem
Trust is easier when customers can verify it.
Claim
Evidence · examples
“99.9% uptime.”
12 months of independently monitored uptime data.
“We respond quickly to incidents.”
Measured incident response history.
“Our infrastructure is reliable.”
Reliability Reputation and the underlying operational data.
02The concept
An operational reputation based on evidence.
Reliability Reputation is calculated from observable operational data and updated as the history grows. It gives buyers a signal they can inspect, with the evidence behind it.
What it is not
A customer review, a self-declared claim, a marketing certification, a one-time audit or a badge that can be purchased.
What it is
Measurable, transparent, continuously updated and calculated from operational evidence using a published methodology.
03Four dimensions
More context than uptime alone.
25%
Incident Response
How your company reacts when something goes wrong.
Detection, acknowledgment, first update and resolution.
25%
Transparency
How much of your incident history customers can verify.
Incident history, communication, updates and maintenance notices.
20%
Consistency
How well your operation maintains that standard over time.
Monitoring history, monthly performance, SLA consistency and recurring incidents.
Response timing follows the incident timeline: detection to acknowledgment, first public update and resolution. Transparency considers the record customers can inspect, including updates and planned maintenance. Consistency adds the longer-term view.
04The methodology
A published model. A traceable calculation.
The four weights add up to 100%. Each normalized dimension contributes its share; a strong result in one area does not erase the evidence in another.
From observations to a score
Raw metrics and normalized scores must remain separate. Uptime is a percentage of observed time; response metrics are durations; transparency and consistency need explicit measurement rules.
This preview publishes the weighting model. Metric normalization, observation windows, monitoring coverage, missing-data handling and maintenance exclusions still need to be defined before live scores can be reproduced or published.
Missing observations must not be treated as perfect uptime. A period with no incidents does not, by itself, prove fast incident response. A public profile must disclose the measurement scope and data gaps.
Reliability Reputation =
(Availability × 3+Incident Response × 2.5+Transparency × 2.5+Consistency × 2) / 10
Each dimension is normalized to 0–100 before weighting. The resulting reputation also ranges from 0 to 100.
Worked example · normalized inputs
Availability99 × 30% = 29.7
Incident Response92 × 25% = 23
Transparency96 × 25% = 24
Consistency94 × 20% = 18.8
Illustrative score · demo data
95.5/ 100
Reliability Reputation
Calculated continuously from monitored operational data.
Observed uptime is a raw metric, not the normalized Availability score. The example starts with normalized inputs; it does not derive them from the profile metrics.
05Score ranges
Read the score with its evidence.
These labels describe numeric ranges in the methodology. They are not subjective endorsements, certifications or a guarantee of future performance.
A high score alone does not establish that enough evidence exists. Always inspect the monitoring period, coverage and underlying dimensions.
Scores are displayed to one decimal place. The range boundaries below avoid gaps between adjacent values.
- Exceptional
- 90–100
- Excellent
- 80 ≤ score < 90
- Good
- 70 ≤ score < 80
- Fair
- 60 ≤ score < 70
- Needs Attention
- < 60
06Minimum evidence
Reputation needs history.
Evidence maturity is separate from the score. These proposed qualification rules require continuous monitoring and enough data for every dimension; they are not a new medal hierarchy.
Verified
At least 30 days
Continuous monitoring and sufficient data for every dimension.
Eligibility to calculate a score; no endorsement of the company.
Established
At least 6 months
Continuous monitoring and sufficient data for every dimension.
Proposed minimum: 80/100 in each dimension.
Trusted
At least 12 months
Continuous monitoring and sufficient data for every dimension.
Proposed minimum: 90/100 in each dimension.
The periods and thresholds shown here are illustrative policy settings, not qualifications already awarded to customers.
07Always changing
Reputation is earned continuously.
Your reputation reflects what your systems have been doing — not what they did once.
Reputation is not permanently awarded. If reliability deteriorates, the score can decrease. Sustained operational improvements can increase it.
New incidents and monitoring data change the evidence. A profile should show the monitoring period, score history and methodology version so buyers can understand those changes.
08The evidence
Inspect what sits behind the number.
A Reliability Profile puts the score alongside the observations. Review availability, incident response, transparency and consistency together with the time period they describe.
The example shows a full year of monitoring, incident counts and response durations. Every number is demo data, including the score.
- Availability
- 30%
- Incident Response
- 25%
- Transparency
- 25%
- Consistency
- 20%
Reliability Profile · example company12 months monitored
Illustrative score · demo data
95.5/ 100
Reliability Reputation
Calculated continuously from monitored operational data.
- Observed availability
- 99.97%
- Incident Response
- 92 / 100
- Transparency
- 96 / 100
- Consistency
- 94 / 100
- Recorded incidents
- 23
- Average acknowledgment
- 4m 12s
- Average resolution
- 18m
- Incident history available
- 100%
All figures are illustrative. This is not a live company profile or an assessment of a customer.
09A public Reliability Profile
One link instead of a spreadsheet.
Each company can share one public URL containing its score, underlying dimensions, monitoring period, history, incidents, trends and methodology.
Use the profile in sales, RFPs, procurement, due diligence, vendor reviews and on your website. Buyers can examine the same evidence and draw their own conclusions.
View an example reliability profileReliability Report
Evidence that can travel with your proposal.
A monthly report can capture the reputation, monitoring period, availability, incidents, response metrics, transparency and historical information. It supports the review process without claiming to be a formal certification.
10Verification
The evidence is the product.
The optional Reliability Verified badge only signals that sufficient monitored data exists to calculate the reputation. It is separate from the score.
Clicking the badge opens the public Reliability Profile. It does not mean StatusPageOne considers the company trustworthy or guarantees its systems.
11Methodology principles
Designed to be questioned. Built to be verified.
Transparent
The methodology is public.
Evidence-based
Scores come from monitored operational data.
Continuous
The reputation changes as new data arrives.
Non-purchasable
Companies cannot buy a higher reputation.
Verifiable
Customers can inspect the underlying evidence.
B2B Reliability Reputation