SurveySparrow Outage History

SurveySparrow is up right now

SurveySparrow had 27 outages in the last 2 years totaling 7h 44m of downtime, averaging 1.1 incidents per month.

There were 27 SurveySparrow outages since January 7, 2026 totaling 7h 44m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.surveysparrow.com

Minor October 15, 2026

ASIA PACIFIC (Mumbai): Responses & Analytics Service Performance Degradation

Detected by Pingoru
Oct 15, 2026, 05:30 AM UTC
Resolved
Oct 15, 2026, 05:31 AM UTC
Duration
49s
Affected: ASIA PACIFIC (MUMBAI) (Responses & Analytics)
Timeline · 2 updates
  1. investigating Oct 15, 2026, 05:30 AM UTC

    We are currently experiencing performance degradation in our ASIA PACIFIC (Mumbai) region, affecting **Responses & Analytics** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Oct 15, 2026, 05:31 AM UTC

    The issue affecting **Responses & Analytics** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor October 13, 2026

Sydney: Builder Service Performance Degradation

Detected by Pingoru
Oct 13, 2026, 10:01 PM UTC
Resolved
Oct 13, 2026, 10:01 PM UTC
Duration
44s
Affected: AP SOUTHEAST (SYDNEY) (Builder)
Timeline · 2 updates
  1. investigating Oct 13, 2026, 10:01 PM UTC

    We are currently experiencing performance degradation in our Sydney region, affecting **Builder** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Oct 13, 2026, 10:01 PM UTC

    The issue affecting **Builder** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor October 2, 2026

US EAST (North Virginia): Builder Service Performance Degradation

Detected by Pingoru
Oct 02, 2026, 07:43 AM UTC
Resolved
Oct 02, 2026, 07:45 AM UTC
Duration
1m
Affected: US EAST (NORTH VIRGINIA) (Builder)
Timeline · 2 updates
  1. investigating Oct 02, 2026, 07:43 AM UTC

    We are currently experiencing performance degradation in our US EAST (North Virginia) region, affecting **Builder** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Oct 02, 2026, 07:45 AM UTC

    The issue affecting **Builder** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor August 24, 2026

EU CENTRAL (Frankfurt): API Service Performance Degradation

Detected by Pingoru
Aug 24, 2026, 09:56 PM UTC
Resolved
Aug 24, 2026, 10:06 PM UTC
Duration
9m
Affected: EU CENTRAL (FRANKFURT) (API)
Timeline · 4 updates
  1. investigating Aug 24, 2026, 09:56 PM UTC

    We are currently experiencing performance degradation in our EU CENTRAL (Frankfurt) region, affecting **API** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Aug 24, 2026, 09:59 PM UTC

    The issue affecting **API** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

  3. monitoring Aug 24, 2026, 10:06 PM UTC

    API service has recovered after capacity automatically scaled out. We are monitoring stability and completing root-cause follow-up.

  4. resolved Aug 24, 2026, 10:06 PM UTC

    API service remains fully recovered. Root-cause follow-up is tracked with the owning engineering team.

Read the full incident report →

Minor August 22, 2026

EU WEST(London): Collect Service Performance Degradation

Detected by Pingoru
Aug 22, 2026, 09:48 AM UTC
Resolved
Aug 22, 2026, 10:02 AM UTC
Duration
14m
Affected: EU WEST (LONDON) (Collect responses)
Timeline · 4 updates
  1. investigating Aug 22, 2026, 09:48 AM UTC

    We are currently experiencing performance degradation in our EU WEST(London) region, affecting **Collect** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Aug 22, 2026, 09:51 AM UTC

    The issue affecting **Collect** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

  3. identified Aug 22, 2026, 09:57 AM UTC

    We identified elevated database connection contention in the Collect serving path, which caused delayed response processing. Traffic and latency are recovering, and affected submissions were accepted by the recovery path for replay. We are monitoring recovery and validating response processing before resolving the incident.

  4. resolved Aug 22, 2026, 10:02 AM UTC

    The Collect performance degradation in EU WEST (London) has been resolved. Request latency and database connection availability have returned to normal, the serving pods are healthy, and monitoring confirms sustained recovery. Follow-up work is tracking replay validation and resilience improvements.

Read the full incident report →

Minor August 14, 2026

US EAST (North Virginia): Responses & Analytics Service Performance Degradation

Detected by Pingoru
Aug 14, 2026, 12:25 AM UTC
Resolved
Aug 14, 2026, 12:31 AM UTC
Duration
6m
Affected: US EAST (NORTH VIRGINIA) (Responses & Analytics)
Timeline · 2 updates
  1. investigating Aug 14, 2026, 12:25 AM UTC

    We are currently experiencing performance degradation in our US EAST (North Virginia) region, affecting **Responses & Analytics** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Aug 14, 2026, 12:31 AM UTC

    Responses & Analytics performance has recovered in US EAST. Serving capacity is healthy and the status route has remained normal after automatic scaling. We are tracking preventive follow-up separately.

Read the full incident report →

Minor August 11, 2026

Canada: Collect Service Performance Degradation

Detected by Pingoru
Aug 11, 2026, 06:34 PM UTC
Resolved
Aug 11, 2026, 06:35 PM UTC
Duration
59s
Affected: CA CENTRAL (CANADA) (Collect Responses)
Timeline · 3 updates
  1. investigating Aug 11, 2026, 06:34 PM UTC

    We are currently experiencing performance degradation in our CANADA region, affecting **Collect** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Aug 11, 2026, 06:35 PM UTC

    The issue affecting **Collect** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

  3. resolved Aug 11, 2026, 06:35 PM UTC

    Collect performance recovered at 00:05 IST after EUI web capacity scaled automatically. Root cause was a short burst of form-render traffic exhausting application database-pool availability on the two-pod baseline; database health remained normal. Capacity and pool-resilience follow-up is in progress.

Read the full incident report →

Minor August 3, 2026

EU WEST (London): Builder Service Performance Degradation

Detected by Pingoru
Aug 03, 2026, 11:19 AM UTC
Resolved
Aug 03, 2026, 11:20 AM UTC
Duration
29s
Affected: EU WEST (LONDON) (Builder)
Timeline · 3 updates
  1. investigating Aug 03, 2026, 11:19 AM UTC

    We are currently experiencing performance degradation in our EU WEST(London) region, affecting **Builder** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. monitoring Aug 03, 2026, 11:19 AM UTC

    Builder performance recovered after additional application capacity was added. We are monitoring service stability before resolving the incident.

  3. resolved Aug 03, 2026, 11:20 AM UTC

    Recovery was confirmed at 16:50 IST. Builder validation across three active UK tenant domains returned HTTP 200, and post-recovery telemetry remained at normal latency with no errors. The incident is resolved.

Read the full incident report →

Minor July 26, 2026

Sydney: Ticket Management Service Performance Degradation

Detected by Pingoru
Jul 26, 2026, 08:37 AM UTC
Resolved
Jul 26, 2026, 08:37 AM UTC
Duration
32s
Affected: AP SOUTHEAST (SYDNEY) (Ticket Management)
Timeline · 2 updates
  1. investigating Jul 26, 2026, 08:37 AM UTC

    We are currently experiencing performance degradation in our SYDNEY region, affecting **Ticket Management** services. Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Jul 26, 2026, 08:37 AM UTC

    The issue affecting **Ticket Management** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor July 26, 2026

Sydney: API Service Performance Degradation

Detected by Pingoru
Jul 26, 2026, 08:36 AM UTC
Resolved
Jul 26, 2026, 08:37 AM UTC
Duration
37s
Affected: AP SOUTHEAST (SYDNEY) (API)
Timeline · 2 updates
  1. investigating Jul 26, 2026, 08:36 AM UTC

    We are currently experiencing performance degradation in our Sydney region, affecting **API** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Jul 26, 2026, 08:37 AM UTC

    The issue affecting **API** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor July 7, 2026

US EAST(North Virginia): API Service Performance Degradation

Detected by Pingoru
Jul 07, 2026, 06:03 PM UTC
Resolved
Jul 07, 2026, 06:07 PM UTC
Duration
3m
Affected: US EAST (NORTH VIRGINIA) (API)
Timeline · 2 updates
  1. investigating Jul 07, 2026, 06:03 PM UTC

    We are currently experiencing performance degradation in our US EAST (North Virginia) region, affecting **API** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Jul 07, 2026, 06:07 PM UTC

    The issue affecting **API** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor July 7, 2026

US EAST (North Virginia): Collect Service Performance Degradation

Detected by Pingoru
Jul 07, 2026, 06:02 PM UTC
Resolved
Jul 07, 2026, 06:07 PM UTC
Duration
5m
Affected: US EAST (NORTH VIRGINIA) (Collect responses)
Timeline · 2 updates
  1. investigating Jul 07, 2026, 06:02 PM UTC

    We are currently experiencing performance degradation in our US EAST (North Virginia) region, affecting **Collect** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Jul 07, 2026, 06:07 PM UTC

    The issue affecting **Collect** services has been fully resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor July 6, 2026

EU CENTRAL (Frankfurt): Builder Service Performance Degradation

Detected by Pingoru
Jul 06, 2026, 01:40 PM UTC
Resolved
Jul 06, 2026, 01:42 PM UTC
Duration
2m
Affected: EU CENTRAL (FRANKFURT) (Builder)
Timeline · 2 updates
  1. investigating Jul 06, 2026, 01:40 PM UTC

    We are currently experiencing performance degradation in our EU CENTRAL (Frankfurt) region, affecting **Builder** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Jul 06, 2026, 01:42 PM UTC

    The issue affecting **Builder** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor July 6, 2026

US East (North Virginia): Delayed submission synchronization

Detected by Pingoru
Jul 06, 2026, 10:14 AM UTC
Resolved
Jul 06, 2026, 11:10 AM UTC
Duration
55m
Affected: US EAST (NORTH VIRGINIA) (Responses & Analytics)
Timeline · 2 updates
  1. investigating Jul 06, 2026, 10:14 AM UTC

    We are currently experiencing delays in submission synchronization for some customers in the US East (North Virginia) region, starting around 15:44 IST on July 6, 2026\. Newly collected responses may take longer than usual to appear in reports, dashboards, exports, or sync-dependent workflows. Response collection remains operational. Our team is actively working through the backlog and monitoring recovery. We will share another update as soon as processing returns to normal.

  2. resolved Jul 06, 2026, 11:21 AM UTC

    The delayed submission synchronization issue in US East (North Virginia) has recovered. Newly collected responses are processing normally again, and reports, dashboards, exports, and sync-dependent workflows have returned to normal operation. We are continuing internal follow-up under SSE-63197 to review the async processing spike observed during the incident window.

Read the full incident report →

Minor June 22, 2026

Intermittent Errors and Increased Latency

Detected by Pingoru
Jun 22, 2026, 03:22 PM UTC
Resolved
Jun 22, 2026, 09:22 PM UTC
Duration
5h 59m
Affected: US EAST (NORTH VIRGINIA) (API)US EAST (NORTH VIRGINIA) (Builder)US EAST (NORTH VIRGINIA) (Collect responses)US EAST (NORTH VIRGINIA) (Responses & Analytics)US EAST (NORTH VIRGINIA) (Ticket Management)US EAST (NORTH VIRGINIA) (Reputation Management)US EAST (NORTH VIRGINIA) (Notifications)US EAST (NORTH VIRGINIA) (Billing)
Timeline · 3 updates
  1. identified Jun 22, 2026, 03:22 PM UTC

    We are currently investigating an issue affecting users accessing the SurveySparrow platform from North America and Europe regions. Some users may experience increased latency, request timeouts, or intermittent errors while using the platform. We have identified that the issue is related to an ongoing disruption affecting our CDN provider, Cloudflare, which is impacting connectivity and performance in the affected regions. Our team is actively monitoring the situation and working with the provider toward resolution. We will provide further updates as more information becomes available.

  2. resolved Jun 22, 2026, 09:22 PM UTC

    The third-party network provider incident has been resolved, and platform metrics have remained stable. We are marking this incident as resolved.

  3. resolved Jun 23, 2026, 02:09 AM UTC

    Cloudflare has resolved the upstream incident and platform metrics have remained stable. We are marking this incident as resolved.

Read the full incident report →

Minor June 19, 2026

EU CENTRAL (Frankfurt): Ticket Management Service Performance Degradation

Detected by Pingoru
Jun 19, 2026, 06:39 AM UTC
Resolved
Jun 19, 2026, 06:40 AM UTC
Duration
41s
Affected: EU CENTRAL (FRANKFURT) (Ticket Management)
Timeline · 2 updates
  1. investigating Jun 19, 2026, 06:39 AM UTC

    We are currently experiencing performance degradation in our EU CENTRAL (Frankfurt) region, affecting **Ticket Management** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved Jun 19, 2026, 06:40 AM UTC

    The issue affecting **Ticket Management** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →

Minor May 21, 2026

ASIA PACIFIC (Mumbai): Builder Service Performance Degradation

Detected by Pingoru
May 21, 2026, 01:00 PM UTC
Resolved
May 21, 2026, 01:01 PM UTC
Duration
57s
Affected: ASIA PACIFIC (MUMBAI) (Builder)
Timeline · 2 updates
  1. investigating May 21, 2026, 01:00 PM UTC

    We are currently experiencing performance degradation in our ASIA PACIFIC (Mumbai) region, affecting **Builder** services.Our team is currently investigating and working to resolve the issue as quickly as possible. We will provide additional updates as we progress.

  2. resolved May 21, 2026, 01:01 PM UTC

    The issue affecting **Builder** services has been resolved, and normal operations have resumed. The system is now operating smoothly, and we are actively monitoring to ensure continued stability.

Read the full incident report →