Cognito Forms Outage History

Cognito Forms is up right now

Cognito Forms had 6 outages in the last 2 years totaling 33h 41m of downtime — averaging 0.2 incidents per month.

There were 6 Cognito Forms outages since July 26, 2024 totaling 33h 41m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cognitoforms.com

Major April 24, 2026

Partial Service Disruption

Detected by Pingoru
Apr 24, 2026, 01:05 PM UTC
Resolved
Apr 24, 2026, 09:03 PM UTC
Duration
7h 57m
Affected: Website and Forms
Timeline · 4 updates
  1. investigating Apr 24, 2026, 01:05 PM UTC

    Some users may be experiencing intermittent issues loading pages or submitting forms. We’re actively investigating and working to restore full service. Thank you for your patience—we’ll keep you updated as we make progress.

  2. identified Apr 24, 2026, 03:18 PM UTC

    Our application and backend systems are operating normally, and we have confirmed this issue did not result from any recent changes on our end. The disruption stems from Microsoft Azure infrastructure responsible for routing traffic, which is causing some requests to fail. We are working directly with Microsoft to resolve the issue as quickly as possible and will provide updates as we learn more.

  3. monitoring Apr 24, 2026, 05:10 PM UTC

    Service has been restored following the earlier issue with upstream infrastructure, and the site should now be accessible for all users. We will continue to monitor to ensure continued stability. Thank you for your patience while we worked through this issue.

  4. resolved Apr 24, 2026, 09:03 PM UTC

    The issue has been resolved, and all systems are operating normally. We appreciate your patience while we worked with our infrastructure partner to restore service.

Read the full incident report →

Critical October 29, 2025

Server Incident

Detected by Pingoru
Oct 29, 2025, 04:26 PM UTC
Resolved
Oct 29, 2025, 11:36 PM UTC
Duration
7h 10m
Affected: Website and Forms
Timeline · 4 updates
  1. investigating Oct 29, 2025, 04:26 PM UTC

    We are actively investigating a service disruption related to a Microsoft Azure outage. Our team is working to restore normal operations as quickly as possible. We apologize for any inconvenience and appreciate your patience.

  2. identified Oct 29, 2025, 06:55 PM UTC

    Our team has implemented an update to help mitigate the issue, and this should improve performance and accessibility for some customers while Azure works to resolve the underlying problem.

  3. monitoring Oct 29, 2025, 09:46 PM UTC

    Microsoft Azure outage is improving. We will continue to monitor the situation.

  4. resolved Oct 29, 2025, 11:36 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 14, 2025

Email Delay

Detected by Pingoru
Jul 14, 2025, 02:50 AM UTC
Resolved
Jul 14, 2025, 01:39 PM UTC
Duration
10h 49m
Affected: Email
Timeline · 4 updates
  1. identified Jul 14, 2025, 02:50 AM UTC

    We’ve identified an issue causing email notification delays for a small group of customers and are actively working to restore normal email operations.

  2. identified Jul 14, 2025, 12:45 PM UTC

    We are continuing to work on a fix for this issue. We apologize for the delay and thank you for your patience.

  3. monitoring Jul 14, 2025, 01:10 PM UTC

    We’ve implemented a fix for the email delay issue and are currently monitoring the results to ensure everything is working as expected.

  4. resolved Jul 14, 2025, 01:39 PM UTC

    Notification emails are now sending as normal. All queued emails are being processed and delivered. We appreciate your patience during this time.

Read the full incident report →

Minor May 12, 2025

Response Times Slower Than Usual

Detected by Pingoru
May 12, 2025, 02:20 PM UTC
Resolved
May 12, 2025, 05:53 PM UTC
Duration
3h 33m
Timeline · 2 updates
  1. investigating May 12, 2025, 02:20 PM UTC

    Please be aware that response times to support tickets may be slower than normal for the time being.

  2. resolved May 12, 2025, 05:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 1, 2025

Website Outage

Detected by Pingoru
Apr 01, 2025, 06:40 PM UTC
Resolved
Apr 01, 2025, 07:53 PM UTC
Duration
1h 13m
Affected: Website and Forms
Timeline · 4 updates
  1. investigating Apr 01, 2025, 06:40 PM UTC

    We are currently investigating reports of an outage affecting the ability for some customers to access our website.

  2. identified Apr 01, 2025, 06:57 PM UTC

    We experienced degraded performance due to an unexpected spike in traffic that impacted server availability. Our team has identified the root cause and is actively working to restore full performance.

  3. monitoring Apr 01, 2025, 07:13 PM UTC

    The issue has been fully resolved, and the website is performing normally. We’re continuing to monitor closely and are reviewing options to prevent similar issues in the future. Thank you for your patience.

  4. resolved Apr 01, 2025, 07:53 PM UTC

    This incident has been resolved. We’ve identified and are implementing safeguards to help prevent similar issues in the future. Thank you for your patience and understanding.

Read the full incident report →

Minor July 26, 2024

Exporting Entries and Downloading Files Delay

Detected by Pingoru
Jul 26, 2024, 04:12 PM UTC
Resolved
Jul 26, 2024, 07:09 PM UTC
Duration
2h 57m
Timeline · 4 updates
  1. investigating Jul 26, 2024, 04:12 PM UTC

    Users may experience delays when exporting entries or downloading files from the Entries page. The export or download should be completed and you'll receive an email once this is complete. Our engineers are actively looking into addressing this issue and we'll keep you updated as we know more.

  2. identified Jul 26, 2024, 04:16 PM UTC

    The issue has been identified and a fix is being worked on.

  3. monitoring Jul 26, 2024, 05:54 PM UTC

    Our engineers have released a fix for this and we will continue monitoring.

  4. resolved Jul 26, 2024, 07:09 PM UTC

    This incident has been resolved.

Read the full incident report →