Live  /  Smarkets  /  Incident

Smarkets: Technical Issues

Smarkets · smarkets.comMinor incidentResolved2026-10-10 15:06 UTC
Public — what happened

Summary

Smarkets reported a minor incident beginning at 13:58 UTC on 2026-10-10, saying pages were loading slowly and some users were having trouble placing bets. The company advised customers whose bets did not appear to go through to review their existing bets before submitting again. Smarkets did not give a cause, and the incident was marked resolved at 15:06 the same day.

Affected

Exchange, SBK

As listed on Smarkets’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Smarkets against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Smarkets: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Smarkets report →

More from Smarkets

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Smarkets status & history page.

Related: Smarkets status & history. SquidGrid is not affiliated with Smarkets.