Gecko Outage History

Gecko had 8 outages in the last 2 years totaling 40h 21m of downtime, averaging 0.3 incidents per month.

There were 8 Gecko outages since January 29, 2025 totaling 40h 21m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.geckoform.com

Major July 21, 2026

Outage with Engagement Widget

Detected by Pingoru: Jul 21, 2026, 09:28 AM UTC
Resolved: Jul 21, 2026, 11:05 AM UTC
Duration: 1h 36m

Timeline · 2 updates

investigating Jul 21, 2026, 09:28 AM UTC

We are currently experiencing an outage affecting all Engagement widgets, rendering them unavailable. This is only affecting the Engagement widget - users with Chat widget are still operational. We are currently investigating the issue.
resolved Jul 21, 2026, 11:05 AM UTC

This incident has now been resolved and all Engagement widgets are now working as expected. If you are still experiencing an issue with your Engagement widget, please reach out to a member of the Customer Success team.

Read the full incident report →

Major July 8, 2026

Chat Widget Outage

Detected by Pingoru: Jul 08, 2026, 12:20 PM UTC
Resolved: Jul 08, 2026, 02:18 PM UTC
Duration: 1h 57m

Timeline · 3 updates

investigating Jul 08, 2026, 12:20 PM UTC

We are currently experiencing an outage with our chat widget where incoming messages are not being recieved by the Gecko systems. We are investigating the issue.
monitoring Jul 08, 2026, 01:23 PM UTC

We identified an issue affecting our Pusher service caused by updating our security tokens, which have now been updated. The live chat widget and bots should now be operating as expected. We are continuing to monitor the situation.
resolved Jul 08, 2026, 02:18 PM UTC

This incident has now been resolved. If you are still experiencing issues with the live chat widget and bots, please reach out to a member of the Customer Success team.

Read the full incident report →

Notice February 23, 2026

Imports/broadcasts are currently backlogged

Detected by Pingoru: Feb 23, 2026, 04:18 PM UTC
Resolved: Feb 23, 2026, 06:28 PM UTC
Duration: 2h 10m

Timeline · 3 updates

investigating Feb 23, 2026, 04:18 PM UTC

We are currently seeing issues related to imports, and broadcasts being backlogged due to excessive queue items from earlier in the day, our team are actively working on the issue, and we will update asap.
identified Feb 23, 2026, 05:25 PM UTC

We have identified the issue, broadcasts and imports that are due to run after 5pm will be running as normal, we are now going to process the backlogged work.
resolved Feb 23, 2026, 06:28 PM UTC

Everything is now processing normally, and we expect any items that had failed to be re-tried and resolve themselves as the normal work schedules run.

Read the full incident report →

Major February 12, 2026

Known issue for Chatbots with Knowledge Bases

Detected by Pingoru: Feb 12, 2026, 05:24 PM UTC
Resolved: Feb 13, 2026, 09:44 AM UTC
Duration: 16h 19m

Timeline · 2 updates

monitoring Feb 12, 2026, 05:24 PM UTC

We are currently aware of an issue with a third-party vendor that is impacting chatbots using Knowledge Bases. We are actively monitoring the situation. In the meantime, to avoid “Sorry, something went wrong” responses (which occur when the bot is unable to access your Knowledge Base), we recommend temporarily removing Knowledge Base integrations from your bot configuration. Once the vendor’s status has returned to normal, you can re-enable them. If you require any assistance, please reach out to a member of the Customer Success team.
resolved Feb 13, 2026, 09:44 AM UTC

This incident has now been resolved. If you are still experiencing issues with chatbots not responding as expected when using knowledge bases, please contact a member of the Customer Success team for assistance.

Read the full incident report →

Major November 18, 2025

Gecko Forms, PreChat Forms & AI ChatBot are not operating as expected due to Cloudflare outage

Detected by Pingoru: Nov 18, 2025, 11:51 AM UTC
Resolved: Nov 18, 2025, 03:22 PM UTC
Duration: 3h 30m

Timeline · 3 updates

investigating Nov 18, 2025, 11:51 AM UTC

We are currently experiencing an issue with our AI chatbots not responding as expected. This is also affecting any Gecko Forms and Prechat Forms using Cloudflare captcha. We believe this is due to Cloudflare Global Network experiencing issues. We are currently investigating the issue.
monitoring Nov 18, 2025, 02:31 PM UTC

The issue has been identified as a global outage with Cloudflare. We have identified a workaround for AI chatbots and are monitoring the situation at https://www.cloudflarestatus.com
resolved Nov 18, 2025, 03:22 PM UTC

We are now seeing a return to normal functionality but will continue to monitor the situation further. Please reach out to a member of the customer success team if you are still experiencing issues.

Read the full incident report →

Notice November 8, 2025

Interruption to email sending

Detected by Pingoru: Nov 08, 2025, 04:00 PM UTC
Resolved: Nov 08, 2025, 04:00 PM UTC
Duration: –

Timeline · 1 update

resolved Nov 09, 2025, 03:38 PM UTC

Earlier today, a system update temporarily affected the ability to send emails. The issue was identified and resolved promptly, and all email delivery services are now back to normal. These emails have been stuck in a "processing" state and can be filtered on the messages section within the product. We have made the decision not to mass-resend emails due to events and timely communication. If you would like emails resent, please contact [email protected]

Read the full incident report →

Minor June 2, 2025

IBM Watson Degraded Service

Detected by Pingoru: Jun 02, 2025, 08:25 PM UTC
Resolved: Jun 03, 2025, 04:40 AM UTC
Duration: 8h 15m

Affected: APIAPI

Timeline · 2 updates

monitoring Jun 02, 2025, 08:25 PM UTC

We are currently monitoring an issue with IBM Watson Cloud, which is impacting IBM Watson ChatBots. As a result: • All IBM Watson Bots are currently displaying a Technical Difficulties message. • All Hybrid Bots (IBM Watson + AI) are temporarily running in full AI-only mode. • All AI-only Bots remain fully operational and are not affected by this issue. We’ll continue to monitor the situation closely. For live updates, you can visit IBM’s status page: https://cloud.ibm.com/status We’ll keep you informed with any developments.
resolved Jun 03, 2025, 04:40 AM UTC

We can confirm that the issue with IBM Watson has now been resolved. • IBM ChatBots have returned to full service. • Hybrid Bots are once again utilising both AI and IBM Watson as expected. Thank you for your patience while IBM acknowledged and resolved the issue on their side. We’ll continue to monitor the situation closely over the next 24 hours and will keep you informed if anything changes.

Read the full incident report →

Major January 29, 2025

Intermittent Issues with Engage Platform

Detected by Pingoru: Jan 29, 2025, 08:34 AM UTC
Resolved: Jan 29, 2025, 03:06 PM UTC
Duration: 6h 32m

Affected: Website

Timeline · 5 updates

investigating Jan 29, 2025, 08:34 AM UTC

We are experiencing intermittent issues with the engage platform serving a 404 error after logging in. We are currently investigating the issue. Apologies for the inconvenience caused.
monitoring Jan 29, 2025, 08:45 AM UTC

The issue seems to be related to Amazon Web Services, who are our main provider of web services. Our team have changed some configuration to work around the issue, and we believe the issue is now resolved - we will continue to monitor the situation. If you are still experiencing issues, please reach out to a member of the Customer Success team.
monitoring Jan 29, 2025, 09:06 AM UTC

We are still experiencing errors with Engage forms and are actively working on restoring functionality. Our team is exploring workarounds to mitigate the impact of the ongoing AWS outage. We will provide updates as soon as we have more information.
monitoring Jan 29, 2025, 09:54 AM UTC

Services are returning to normal following our implemented workarounds and recent fixes from AWS. Testing across forms, events, and both US and UK customers has shown positive results. Our team is continuing to monitor for any further issues. Ongoing incident at AWS can be tracked here: https://health.aws.amazon.com/health/status
resolved Jan 29, 2025, 03:06 PM UTC

This incident has been resolved.

Read the full incident report →