Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Talonone outage history

    3 recorded Talonone incidents since July 2024, with official updates, affected components, duration and resolution information.

    Back to current status

    Brief Disruption to Point Deduction Processing

    Started June 24, 2026 at 12:40 PM UTC · 0m

    Pending
    1. June 24, 2026 at 1:50 PM UTCresolved

      During today's product release, a technical issue caused requests that involve point deductions to fail momentarily. This has been resolved. If your account was impacted, your account team will be in touch directly with further details.

    Temporary increase in response times in EU/US clusters

    Started September 27, 2024 at 3:33 PM UTC · 1m

    IssuesMinor incident
    1. September 27, 2024 at 3:33 PM UTCmonitoring

      A recent database update caused a temporary increase in response times, along with some occurrences of 499 and 5xx errors. This issue has now been resolved. Our team is actively investigating ways to prevent these errors going forward. If you would like more information, please contact your dedicated Customer Success team.

    2. September 27, 2024 at 3:34 PM UTCresolved

      The incident is now resolved. If you would like more information, please contact your dedicated Customer Success team.

    Network outage leading to unreliable communications

    Started July 8, 2024 at 6:33 PM UTC · 1d 16h

    OutageMajor incident
    1. July 8, 2024 at 6:33 PM UTCidentified

      Instability in our cloud network has led to notifications being sent irregularly or not at all. We are working closely with our providers to restore stability and resend the missing notifications.

    2. July 9, 2024 at 8:27 PM UTCidentified

      A solution has been reached and tested successfully in the development environment. Affected parties may experience a short silence period, but will be contacted prior to ensure the appropriate window of silence is selected. No data loss has been confirmed as well.

    3. July 11, 2024 at 7:19 AM UTCresolved

      Incident identified and resolved