What the service evidence establishes
Uptime describes channel-only white-label NOC, 24/7/365 monitoring, triage and remediation against agreed priorities and SLAs. Its brand announcement, dated March 28, 2024, describes the consolidation of Uptime Solutions and Inbay after their September 2023 merger. This directory uses one provider record. See the official service source.
Commercial boundary to resolve
The NOC page describes fixed monthly cost and broad RMM compatibility, without establishing a universal rate or a named connector for every product. Request the current rate, minimum, contract term and exact workflow. Broad compatibility language does not establish bidirectional ticket or documentation behavior.
Qualification by scenario
| Your scenario | First question | Evidence to retain |
|---|---|---|
| Existing Inbay relationship | Which entity and agreement now apply? | Current legal entity, order and notice address |
| RMM-heavy estate | Which alert classes are remediated rather than forwarded? | Approved actions and unsupported platform cases |
| Continuous operations | Who owns a critical unresolved shift-change incident? | Timezone calendar, accepting owner and fallback escalation |
Bring a defined inventory and anonymized workload to the first discussion. Device counts, user counts and ticket volumes describe different obligations. Record a missing answer as unresolved; do not substitute a zero cost, an assumed capability or a negative quality judgment. Ask the supplier to identify the applicable plan and legal entity in its reply.
Public customer evidence and its limits
The NOC page includes a customer-testimony section selected by Uptime. Seek a current reference for the consolidated service and ask whether the reference used the same coverage and remediation scope.
For a reference conversation, ask when the service was used, which plan and shifts were involved, what the customer retained internally and whether a material incident or exit was experienced. A named comment can help identify a question to investigate, but it does not establish the full SLA, staffing model or suitability for your clients.
A bounded pilot before enrollment
An external interview with the service leaders
In TubbTalk episode 78, Richard Tubb interviews Bradley Munday and Jason Kemsley about Uptime Solutions. The accompanying article explains their helpdesk pod approach, the relationship between outsourced support and an MSP's own team, and a trial arrangement described in that conversation. The article discusses the earlier Uptime Solutions business, before the later Inbay consolidation.
Use this interview to ask how technician continuity, onboarding and escalation work in your proposed service. Confirm current pilot terms in writing. The interview is a supplier explanation published by an external host, rather than a customer interview or measured benchmark; historical trial and staffing details are not current contractual guarantees.
Pilot an alert requiring a documented third-line escalation and one routine approved fix. Verify both the internal ticket trail and the MSP-facing record. For a legacy Inbay agreement, ask the provider to explain any changed process before comparing old experience with the current offer. Brand consolidation is not evidence that every historical service term remained the same.
Define pass and fail criteria before testing: correct tenant, permitted action, an intelligible audit trail, accepted escalation and a reversible access path. Preserve both successful and unsuccessful cases. Use these criteria when agreeing your own pilot.
Compare the same obligation
Use the provider directory to select candidates, then send one RFP with identical scope. Normalize the quote in the cost calculator and record the five SLA clocks separately. Confirm staff and data locations, notice and exit work in writing before granting production access. Read our methodology or send a sourced correction.