iGaming platform reliability evidence
A provider-by-provider record of status history, incident objects, scoped availability figures, communications, and the gap between marketing percentages and a buyer's enforceable SLA.
Four evidence layers
Do not collapse telemetry, history, measurement, and contract
Bounded reliability record
Reliability transparency matrix
A zero appears only for an explicitly recorded incident array within a defined window. “Not countable” means no complete bounded incident population is recorded.
| Provider | History state | Incident window | Incident objects | Availability record types |
|---|---|---|---|---|
| BetConstruct | Defined incident history | 2026-05-01 through 2026-08-13 | 42 | Availability result not confirmed |
| EveryMatrix | Defined incident history | 2022-03-09 through 2026-08-13 | 0 | Availability result not confirmed |
| Altenar | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Aristocrat Interactive | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Bragg Gaming Group | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Delasport | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Digitain | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| GiG (GiG Software) | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| GR8 Tech | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Kambi Group | Incident history unavailable for a complete count | Countable incident window not available | Not countable 1 separate communication record | Availability result not confirmed |
| Light & Wonder (iGaming) | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| NuxGame | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Pariplay | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Playtech | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| Slotegrator | Incident history unavailable for a complete count | Countable incident window not available | Not countable 1 separate communication record | Availability result not confirmed |
| Soft2Bet | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
| SOFTSWISS | Incident history unavailable for a complete count | Countable incident window not available | Not countable | Availability result not confirmed |
2 provider records have an explicitly countable incident array. Counts remain bounded by each defined window and service scope.
Provider-by-provider reliability boundary
Each card states the current service scope, available operational record, and conclusions that remain unsupported.
Comparable availability for All unscheduled incident records from operator-facing, third-party, and internal components is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
As of 13 August 2026, component status showed a partial system outage across 11 records: eight OddsMatrix split endpoints plus the B3, D5, and F8 shard groups. Separate unsuffixed Webapi OddsMatrix components were operational. No incident narrative, affected-customer scope, root cause, or resolution time is recorded. The incident history contains zero objects, which does not establish zero outages, provider-wide uptime, or MTTR.
Managed trading and continuous customer support are available. Achieved uptime, incident frequency, restoration performance, and contractual remedy remain unquantified.
Component status history, measured product availability, incident history, standard SLA terms, and breach remedies are unavailable. FY2025 group reporting covers technology-integration risk, cyber controls, and service-level obligations but does not quantify product uptime.
Component-level status history, measured availability, incident register, and a complete provider-wide SLA are unavailable. Listed-company status and named deployments do not quantify operating performance.
Continuous managed-service coverage is available. Component status history, observed availability series, and complete SLA terms are unavailable. ISO 27001 and GLI credentials concern security management or technical compliance; they do not establish uptime.
Comparable availability for Digitain platform products, with a separate check of the Sports Data/API claim is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
Comparable availability for GiG CoreX, SportX, LogicX, DataX, and managed-service products is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
Comparable availability for GR8 Tech Platform, GREAT_Turnkey, GREAT_SPORTSBOOK, GREAT_AGGREGATION, and Payment Gateway is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
A Q2 2026 disclosure records credits related to unspecified operational issues in April 2026. The affected component, partners, duration, cause, restoration time, and credit value are unknown. A separately cited third-party World Cup uptime ranking has no recorded benchmark or methodology. Public evidence contains no component status history, numerical observed-availability series, or complete SLA terms.
Comparable availability for Light & Wonder iGaming systems, with the Infinity Gateway portal claim kept separate is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
Comparable availability for NuxGame platform, Casino API, Sports Betting API, Sportsbook, and infrastructure scope is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
Fusion has recorded continuous support coverage. Component status history, measured availability, incident history, response targets, and complete SLA terms are unknown. Named deployments establish adoption, not operating reliability.
FY2025 control scope includes a 24/7 security operations centre, incident response, backups, and continuity testing. Product status history, observed availability, and standard SLA terms are unknown. Financial and control reporting is not an uptime audit.
Measured availability and incident history are unknown. The April 2026 AMATIC content event lacks enough detail to establish event timing, affected operators or sessions, resolution, final root cause, or a reliability metric.
Comparable availability for Soft2Bet iGaming platform is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
Comparable availability for SOFTSWISS Game Aggregator and Casino Platform as separate products is unknown. Product scope, observation period, formula, measurement point, exclusions, independent assurance, contractual threshold, and remedy remain unconfirmed.
Comparability gate
Evidence completeness before any uptime comparison
A check means the required field exists in the public operational record. It does not mean the value is good, independently assured, or contractually acceptable. A missing field prevents a comparable provider-wide conclusion.
| Provider | Bounded incident window | Exact incident timing | Measurement period | Measurement method | Published exclusions | Contract remedy |
|---|---|---|---|---|---|---|
| BetConstruct | Recorded | Recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| EveryMatrix | Recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Altenar | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Aristocrat Interactive | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Bragg Gaming Group | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Delasport | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Digitain | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| GiG (GiG Software) | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| GR8 Tech | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Kambi Group | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Light & Wonder (iGaming) | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| NuxGame | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Pariplay | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Playtech | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Slotegrator | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| Soft2Bet | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
| SOFTSWISS | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded | Not recorded |
Convert reliability claims into acceptance tests
Reliability evidence questions
Which iGaming platform has the best uptime?
Provider-wide uptime figures are not comparable across different products, periods, formulas, components, and exclusions. This comparison therefore has no provider-wide leaderboard and is limited to transparency and record scope.
Do zero recorded incidents mean zero outages?
No. Zero means a defined incident window contains zero recorded incident objects. An unavailable complete history is a separate, uncountable state; neither one establishes zero outages.
Is a status page the same as an SLA?
No. A status page is communications or telemetry. An SLA needs a service definition, measurement point and window, exclusions, breach threshold, reporting process, and remedy in the contract.
Does GLI, ISO, or regulator approval prove uptime?
No. Testing, security controls, and market approval answer different questions. They can support diligence, but they do not establish measured availability, incident recovery, or the buyer's contractual remedy.
What should a buyer test before signing?
Request component-level availability data, incident exports, maintenance treatment, synthetic and real-user measurements, recovery tests, RTO and RPO evidence, dependency mapping, communications samples, and the exact SLA formula and remedy for the proposed product and environment.