Talis Outage History

Talis is up right now

Talis had 3 outages in the last 2 years totaling 12h 47m of downtime — averaging 0.1 incidents per month.

There were 3 Talis outages since October 17, 2025 totaling 12h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.talis.com

Minor March 26, 2026

Availability Issues

Detected by Pingoru
Mar 26, 2026, 10:43 AM UTC
Resolved
Mar 26, 2026, 11:22 AM UTC
Duration
38m
Affected: General
Timeline · 2 updates
  1. investigating Mar 26, 2026, 10:43 AM UTC

    We've become aware of an issue with the print availability of items in Talis Aspire not displaying as expected. In some cases this is impacting on bookmarking too. Our tech team are investigating as an urgent priority, we will look to update you again shortly. Apologies for the inconvenience this may be causing you and your users today.

  2. resolved Mar 26, 2026, 11:22 AM UTC

    The cause has been identified and normal service has been resumed.

Read the full incident report →

Notice February 9, 2026

Emails to Talis support site 'undeliverable'

Detected by Pingoru
Feb 09, 2026, 10:15 PM UTC
Resolved
Feb 10, 2026, 09:56 AM UTC
Duration
11h 41m
Affected: General
Timeline · 2 updates
  1. investigating Feb 09, 2026, 10:15 PM UTC

    We are currently experiencing an issue where emails to [email protected] are receiving a bounce-back to say that the message could not be delivered. You should still be able to raise support tickets when logged into the support site.

  2. resolved Feb 10, 2026, 09:56 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 17, 2025

Talis Aspire inaccessible

Detected by Pingoru
Oct 17, 2025, 10:46 AM UTC
Resolved
Oct 17, 2025, 11:13 AM UTC
Duration
27m
Affected: General
Timeline · 2 updates
  1. investigating Oct 17, 2025, 10:46 AM UTC

    Talis Aspire is currently showing an error message when users attempt to access the system. We are investigating as a matter of urgency.

  2. resolved Oct 17, 2025, 11:13 AM UTC

    This incident has been resolved.

Read the full incident report →