Client: SpinHarbour · iGaming & Betting · Maltese casino aggregator (90 staff and 41 game vendors)
Improving Uptime Across Casino Vendor Integrations
TechSupport Team managed L2 escalations for 12 of the 41 game vendor integrations on SpinHarbour’s casino platform. In six months, platform uptime rose from 99.81% to 99.98% in the client’s Datadog records.
Client and engagement facts
- Client
- SpinHarbour
- Industry
- iGaming & Betting
- Business context
- Maltese casino aggregator (90 staff and 41 game vendors)
- Delivery model
- Managed L2 integration escalations
- Application
- Casino platform aggregating 41 game vendors
- Supplied geography
- Maltese
- Company size in source
- 90 staff
Related services: L2 and L3 support
Application stack and tools
Application stack
- Node.js
- MongoDB
- Redis
- AWS
Tools used
- Datadog
- Zendesk
- Intercom
- Jira Service Management
Why Support Was Needed
The client’s helpdesk needed a way to distinguish a slow game vendor from a failed integration before paging product engineers. The client kept player tickets and assigned the named technical queue to TechSupport Team.
Technical Work
- Built a health dashboard for each vendor to help isolate TLS, DNS and payload errors.
- Added integration contract checks that detected three breaks in the first month.
- Wrote diagnostic runbooks for the 12 integrations in scope.
Representative Incident
In week one, a vendor API failure affected 18% of players. L2 traced it to a TLS mismatch at the vendor’s new endpoint and applied a compatible cipher suite from the runbook. Connectivity returned in 20 minutes.
Results and how they were measured
| Metric | Baseline | Result | Units | Measurement window | Sample / population | Source and scope |
|---|---|---|---|---|---|---|
| Uptime | 99.81% | 99.98% | % | 6 months | Client platform uptime; TechSupport Team managed L2 for 12 of the 41 integrations. | Client Datadog |
| Queue first response | 22 min | 4 min | min | 6 months | Client Zendesk support queue; the client first-line team retained player tickets. | Client Zendesk |
| Vendor tickets closed independently | 0% | 74% | % | 6 months | Vendor tickets within the 12 integrations in scope. | Client JSM |
Evidence and Limitations
One vendor outage was excluded. Zendesk first response describes the support queue. Jira Service Management tracked vendor tickets the team could close independently.
Integration and Ticket Ownership
TechSupport Team owned L2 for the 12 integrations in scope. SpinHarbour’s first-line team kept player tickets.
Scope a Similar Engagement
List the vendor integrations that repeatedly reach engineering and the handoff your helpdesk uses today. Request a support plan or explore L2 and L3 support.
Get a technical support plan
Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.
- We reply by email.
- We agree a call about the roles, your stack and the hours.
- If there is a fit, we propose engineers after an assessment.