Onspring Outage History

Onspring is up right now

Onspring had 3 outages in the last 2 years totaling 51h 37m of downtime — averaging 0.1 incidents per month.

There were 3 Onspring outages since June 17, 2025 totaling 51h 37m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.onspring.com

Critical January 14, 2026

Onspring Connectivity

Detected by Pingoru
Jan 14, 2026, 02:39 PM UTC
Resolved
Jan 14, 2026, 07:35 PM UTC
Duration
4h 55m
Affected: Instances
Timeline · 3 updates
  1. investigating Jan 14, 2026, 02:39 PM UTC

    Onspring is currently experiencing downtime as of 8:15am Central Time. Our technical resources are aware and actively working on a resolution. GovCloud and Azure instances appear to be unaffected at this time. We will provide an update as soon as one is available. Thank you for your patience as we navigate this issue.

  2. monitoring Jan 14, 2026, 03:04 PM UTC

    Onspring connectivity has been fully restored and we are currently monitoring. Please contact [email protected] if you experience any further login issues.

  3. resolved Jan 14, 2026, 07:35 PM UTC

    After monitoring, our technical team has confirmed that the issue has been resolved and that there was no data loss. We appreciate your patience throughout these past two days and apologize for any inconvenience this may have caused. A follow-up communication regarding this issue will be sent out today.

Read the full incident report →

Major October 1, 2025

Onspring Data Processing Issues

Detected by Pingoru
Oct 01, 2025, 04:04 PM UTC
Resolved
Oct 02, 2025, 04:31 PM UTC
Duration
1d
Affected: InstancesFormula CalculationsAPIEmail MessagingTriggers / OutcomesImports / Data ConnectorsSearch IndexingRecord SavesEmail Sync
Timeline · 5 updates
  1. investigating Oct 01, 2025, 04:04 PM UTC

    Onspring's data processing (queue) service is experiencing issues at this time. Users may be experiencing temporary performance delays as a result. We are actively working towards providing a resolution as quickly as possible.

  2. investigating Oct 01, 2025, 04:05 PM UTC

    We are continuing to investigate this issue.

  3. identified Oct 01, 2025, 08:48 PM UTC

    A fix for the current data processing issue has been identified and is being prepared for deployment.

  4. monitoring Oct 01, 2025, 11:04 PM UTC

    The fix has been implemented successfully and we're closely monitoring our data processing as it returns to stable operations. Thank you for your patience as we work through this matter.

  5. resolved Oct 02, 2025, 04:31 PM UTC

    After monitoring overnight and this morning, our data processing service has resumed stable operations. We appreciate your patience as we worked through this matter.

Read the full incident report →

Major June 17, 2025

Onspring Data Processing Issue

Detected by Pingoru
Jun 17, 2025, 05:31 PM UTC
Resolved
Jun 18, 2025, 03:47 PM UTC
Duration
22h 15m
Affected: InstancesFormula CalculationsEmail MessagingTriggers / OutcomesImports / Data ConnectorsSearch IndexingRecord SavesEmail Sync
Timeline · 4 updates
  1. investigating Jun 17, 2025, 05:31 PM UTC

    Onspring's data processing (queue) service is experiencing issues at this time. Users may be experiencing temporary performance delays as a result. We are actively working towards providing a resolution as quickly as possible.

  2. investigating Jun 17, 2025, 09:43 PM UTC

    We are continuing to investigate this issue and are making progress. We will provide another update as soon as one is available. Thank you for your patience as we work to resolve this matter.

  3. monitoring Jun 18, 2025, 12:48 AM UTC

    We've successfully addressed the data processing backlog that was impacting system performance. The queue is now processing items normally and we're seeing a return to stable operations. We'll continue to monitor to ensure everything stays on track.

  4. resolved Jun 18, 2025, 03:47 PM UTC

    After monitoring overnight and this morning, our data processing service has resumed stable operations. During the final recovery stages this morning, we encountered an issue with a networking environment component that caused 4 minutes of downtime from 8:30 - 8:34AM. This was quickly identified and rectified and we've confirmed there was no data loss as a result. We appreciate your patience as we worked through this matter.

Read the full incident report →