User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Sports
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 179 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 654 ms | 0 |
| Mon 15 | 0 | 0.0 | 681 ms | 0 |
| Mon 17 | 0 | 0.0 | 631 ms | 0 |
| Mon 19 | 0 | 0.0 | 726 ms | 0 |
| Mon 21 | 0 | 0.0 | 714 ms | 0 |
| Mon 23 | 0 | 0.0 | 678 ms | 0 |
| Tue 01 | 0 | 0.0 | 312 ms | 0 |
| Tue 03 | 0 | 0.0 | 241 ms | 0 |
| Tue 06 | 0 | 0.0 | 591 ms | 0 |
| Tue 08 | 0 | 0.0 | 210 ms | 0 |
| Tue 10 | 0 | 0.0 | 201 ms | 0 |
| Tue 12 | 0 | 0.0 | 682 ms | 0 |
| Tue 14 | 0 | 0.0 | 261 ms | 0 |
| Tue 16 | 0 | 0.0 | 432 ms | 0 |
| Tue 18 | 0 | 0.0 | 268 ms | 0 |
| Tue 20 | 0 | 0.0 | 675 ms | 0 |
| Tue 22 | 0 | 0.0 | 204 ms | 0 |
| Wed 01 | 0 | 0.0 | 218 ms | 0 |
| Wed 03 | 0 | 0.0 | 288 ms | 0 |
| Wed 05 | 0 | 0.0 | 247 ms | 0 |
| Wed 07 | 0 | 0.0 | 251 ms | 0 |
| Wed 10 | 0 | 0.0 | 242 ms | 0 |
| Wed 12 | 0 | 0.0 | 651 ms | 0 |
| Wed 14 | 0 | 0.0 | 633 ms | 0 |
| Wed 16 | 0 | 0.0 | 622 ms | 0 |
| Wed 18 | 0 | 0.0 | 230 ms | 0 |
| Wed 20 | 0 | 0.0 | 256 ms | 0 |
| Wed 23 | 0 | 0.0 | 305 ms | 0 |
| Thu 01 | 0 | 0.0 | 226 ms | 0 |
| Thu 03 | 0 | 0.0 | 275 ms | 0 |
| Thu 05 | 0 | 0.0 | 255 ms | 0 |
| Thu 07 | 0 | 0.0 | 250 ms | 0 |
| Thu 09 | 0 | 0.0 | 627 ms | 0 |
| Thu 11 | 0 | 0.0 | 632 ms | 0 |
| Thu 13 | 0 | 0.0 | 165 ms | 0 |
| Thu 15 | 0 | 0.0 | 186 ms | 0 |
| Thu 17 | 0 | 0.0 | 214 ms | 0 |
| Thu 19 | 0 | 0.0 | 666 ms | 0 |
| Thu 21 | 0 | 0.0 | 278 ms | 0 |
| Thu 23 | 0 | 0.0 | 629 ms | 0 |
| Fri 01 | 0 | 0.0 | 255 ms | 0 |
| Fri 03 | 0 | 0.0 | 223 ms | 0 |
| Fri 05 | 0 | 0.0 | 741 ms | 0 |
| Fri 07 | 0 | 0.0 | 207 ms | 0 |
| Fri 09 | 0 | 0.0 | 619 ms | 0 |
| Fri 11 | 0 | 0.0 | 558 ms | 0 |
| Fri 13 | 0 | 0.0 | 272 ms | 0 |
| Fri 15 | 0 | 0.0 | 179 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Scheduled MannaPlay Provider Maintenance
Service Impact: Services will be temporarily unavailable during the maintenance period.
EveryMatrix Provider maintenance
During the maintenance window, all services provided by EveryMatrix might suffer service interruptions.
Scheduled Novomatic Provider Maintenance
Impact: Please note that gameplay will be unavailable during this time
Pragmatic Play Maintenance
Impact-Production DK15 will have downtime affecting all brands on the production. Slots, LC games and Scratch cards will not be available; Slots Back Office access will be affected; FRBs, Tournaments, Prize Drops, Cashbacks, Jackpots will not be available. LC Back Office access will not be affected
Greentube maintenance
During the time, Game Client, Back Office, and Web Service API will be inaccessible.
Pragmatic Play Maintenance
Impact: Production DK5 will have downtime affecting all brands on the production. Slots, LC games and Scratch cards will not be available; Slots Back Office access will be affected; FRBs, Tournaments, Prize Drops, Cashbacks, Jackpots will not be available. LC Back Office access will not be affected.
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Betconstruct yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Betconstruct goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Betconstruct alerts to Slack, Discord or a webhook — free.
Betconstruct is listed in our Sports category and checked at betconstruct.com. Betconstruct offers a complete range of online betting & gambling software solutions. Start your sports betting business today.
Betconstruct publishes an official status page at status.betconstruct.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with sports services: ticketing, team app and live-score pages slowing down around game time.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 403 ms average, 179–741 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Betconstruct incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
403 ms on average over the last 24 hours (179–741 ms).
Yes, at https://status.betconstruct.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For sports services, watch for ticketing, team app and live-score pages slowing down around game time. If many people report Betconstruct here at once, the problem is on Betconstruct's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Betconstruct. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.