Skip to content
iGaming Platform Provider
Bounded operating record

BetConstruct incident history: 42 records in a defined 2026 window

Our dataset contains 42 countable unscheduled incident records inside one fixed observation window. Each row keeps its own component scope and timestamps; the records are not collapsed into a provider-wide outage rate, uptime percentage, or operator impact estimate.

Observation window: May 1, 2026 through August 13, 2026. Record reviewed August 13, 2026. Page updated August 13, 2026.

Incident history summary

Countable records
42
Exact scope labels
19
Records with both timestamps
42 of 42
The denominator is 42 records, not all outages
Every count on this page uses the 42 incident objects in the 2026-05-01 to 2026-08-13window. Planned maintenance is excluded. Platform, back-office, third-party, and internal-tool scopes are mixed. The dataset does not establish completeness, provider-wide uptime, affected operators or players, SLA breach, or the duration of actual user impact.

Publication boundary

What the record can and cannot establish

Countable from this dataset
  • The exact 42-record denominator and observation window.
  • Each record's date, title, component-scope label, and impact label.
  • Whether both a start and resolution timestamp are present for a record.
  • How many records carry each exact scope or impact label inside this population.
Not established by this dataset
  • A complete provider-wide incident population or uptime.
  • Which operators or players were affected, or how severely.
  • Contractual SLA measurement, exclusions, breach, or remedy.
  • Actual service-impact duration, combined MTTR, root cause, or corrective-action closure.

Dataset composition

Keep scope and impact labels separate

Counts below describe the 42 records only. A compound scope remains one exact label, and an impact label is not an independent severity assessment. “None” is a recorded label; it is not evidence that nobody was affected.

Records by exact component-scope label
Swipe horizontally to view all columns.
Counts sum to 42 incident records.
Exact component-scope labelRecords
BackOffice Panel9
Casino Platform8
3rd Party Provider6
SpringBuilder3
Jira2
Affiliates/Agents systems1
Affiliates/Agents systems and CRM1
AGP Panel1
Bonuses, BackOffice Panel1
Casino Bet Settlement1
Casino Bet Settlement, Casino Bets Placement1
Casino Bet Settlement; Casino Bets Placement1
Casino Platform and Bonuses1
Casino Platform, Payments System, Sport Bet Settlement, BackOffice Panel1
Casino Platform, Sport Bet Settlement, Sportsbook, BackOffice Panel1
Component mapping unavailable1
Microsoft Remote Apps Services1
Payments System1
Spring Platform1
Records by impact label
Swipe horizontally to view all columns.
Counts sum to 42 incident records.
Impact labelRecords
Major21
None12
Critical9

Full bounded record

All 42 incident records

Records are ordered newest to oldest. Start and resolution values retain their recorded UTC offset. They delimit the record, not a confirmed period of platform-wide or player-facing impact.

Swipe horizontally to view all columns.
42 countable records in the defined 2026-05-01 to 2026-08-13 observation window.
Record dateIncident recordExact component scopeImpact labelStartedResolved
Issue with bonus winning settlementCasino Platform and BonusesMajor
Issue with SpringBuilder WebsitesSpringBuilderCritical
Springbuilder website issueSpringBuilderCritical
Pragmatic Play Provider Issue3rd Party ProviderNone
Issue with Agent System / Affiliate System / CRM SystemAffiliates/Agents systems and CRMNone
Issue with Casino PlatformCasino PlatformCritical
Backoffice Login Global IssueBackOffice PanelNone
Casino Rollback Global IssueCasino Bet Settlement; Casino Bets PlacementNone
Issue with the Pragmatic Play Provider3rd Party ProviderCritical
Issue with PG Soft Provider3rd Party ProviderMajor
Global Issue with Casino GamesCasino PlatformNone
Global Issue with Casino GamesCasino PlatformNone
Issue with JiraJiraMajor
Backoffice IssueBackOffice PanelMajor
Backoffice Login IssueBackOffice PanelMajor
Issue with Casino/Live Casino GamesCasino PlatformMajor
Backoffice loading and slowness issueBackOffice PanelMajor
Global Issue with Casino/Live Casino GamesCasino PlatformNone
Affiliate and agents panel issueAffiliates/Agents systemsCritical
Issue adding bonus to players in BackOfficeBonuses, BackOffice PanelMajor
RDS connecting issueAGP PanelCritical
AGP connection issue with Remote Desktop ServiceMicrosoft Remote Apps ServicesCritical
Issue with Casino PlatformCasino PlatformMajor
Issue with Pragmatic Play Free Spins3rd Party ProviderMajor
Issue with Backoffice PanelBackOffice PanelNone
Issue with Casino PlatformCasino PlatformMajor
Issue with EGT Digital games3rd Party ProviderMajor
Issue with Backoffice PanelBackOffice PanelCritical
Issue with error message in Backoffice platformBackOffice PanelMajor
Issue with Deposits and WithdrawalsPayments SystemMajor
Issue with Evolution provider3rd Party ProviderMajor
Issue with JiraJiraMajor
Issue with Casino Slot gamesCasino PlatformMajor
Issue with the PlatformCasino Platform, Sport Bet Settlement, Sportsbook, BackOffice PanelMajor
Issue with the PlatformCasino Platform, Payments System, Sport Bet Settlement, BackOffice PanelMajor
Issue with Spring Builder websitesSpringBuilderMajor
Backoffice Replication IssueBackOffice PanelNone
Backoffice Replication issueBackOffice PanelMajor
Issue with Casino betsCasino Bet Settlement, Casino Bets PlacementCritical
Withdrawal Reflection issuesComponent mapping unavailableNone
Casino Bets Rollback IssueSpring PlatformNone
Casino Bets Rollback IssueCasino Bet SettlementNone

Buyer use

Convert the record into contract-specific evidence

Map the proposed component set

Match each included platform, back-office, payment, content, and third-party dependency to the exact component names used in operational reporting.

Request the buyer-specific population

Require the incident and maintenance export for the proposed environment and contract term, with immutable identifiers and inclusion rules.

Define impact and SLA clocks

Set the measurement point, severity rules, exclusions, start and stop events, aggregation rule, notice time, and remedy for each critical service.

Close causes and corrective actions

Tie material records to root-cause review, action owner, due date, verification result, recurrence threshold, and buyer escalation rights.

Continue the reliability review

Compare evidence boundaries before converting any incident count into a shortlist decision.

Reliability comparison