10to8 Outage History

10to8 is up right now

10to8 had 2 outages in the last 2 years totaling 5h 14m of downtime — averaging 0.1 incidents per month.

There were 2 10to8 outages since January 23, 2026 totaling 5h 14m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.10to8.com

Minor April 1, 2026

Service Disruption: Smart Messaging, Product Dashboard AI Assistant and Voice Booking

Detected by Pingoru
Apr 01, 2026, 05:21 PM UTC
Resolved
Apr 01, 2026, 06:56 PM UTC
Duration
1h 35m
Affected: SISc Web-ApplicationSISc Web-ApplicationSISc Web-ApplicationSISc Web-ApplicationCommunicationsCommunicationsCommunicationsCommunicationsCalendar SyncCalendar SyncCalendar SyncCalendar SyncWebsite
Timeline · 3 updates
  1. identified Apr 01, 2026, 05:21 PM UTC

    We are currently experiencing an ongoing issue impacting Smart Messaging and the Product Dashboard AI Assistant. We are also experiencing degraded performance on the voice booking name transcription. We have identified the root cause of these issues and are working on a solution.

  2. monitoring Apr 01, 2026, 06:26 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 01, 2026, 06:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 23, 2026

Partial Communications Outage

Detected by Pingoru
Jan 23, 2026, 10:30 AM UTC
Resolved
Jan 23, 2026, 02:08 PM UTC
Duration
3h 38m
Affected: Communications
Timeline · 5 updates
  1. investigating Jan 23, 2026, 12:49 PM UTC

    We are currently investigating an issue where some communciations are delayed in sending. This includes new appointment confirmations, reminders and ad-hoc messages.

  2. monitoring Jan 23, 2026, 12:53 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Jan 23, 2026, 01:13 PM UTC

    We are continuing to monitor for any further issues.

  4. monitoring Jan 23, 2026, 01:15 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Jan 23, 2026, 02:08 PM UTC

    This incident has been resolved.

Read the full incident report →