Incidents reported on status page for Tourpaq™ https://status.tourpaq.com/ en https://status.tourpaq.com/ Sun, 31 May 2026 07:42:34 +0000 https://status.tourpaq.com/#88b52ad95d797fdbfbb3cc6ca8562d1a4eb0071462629a7d1a6810e5bef1035d Booking Engine recovered https://status.tourpaq.com/ Sun, 31 May 2026 07:31:46 +0000 https://status.tourpaq.com/#88b52ad95d797fdbfbb3cc6ca8562d1a4eb0071462629a7d1a6810e5bef1035d Booking Engine went down https://status.tourpaq.com/ Tue, 12 May 2026 09:15:37 +0000 https://status.tourpaq.com/#3b0db65ff7036b69b9a9199ee21b69c05e31aae1c8606b0fb2aed18d37149606 Booking Engine recovered https://status.tourpaq.com/ Tue, 12 May 2026 09:06:37 +0000 https://status.tourpaq.com/#3b0db65ff7036b69b9a9199ee21b69c05e31aae1c8606b0fb2aed18d37149606 Booking Engine went down https://status.tourpaq.com/ Mon, 04 May 2026 09:22:12 +0000 https://status.tourpaq.com/#c8feac60c8ea61d5ba9559c21d041e7caed2849a60eda69b1d1088440a5f839f AvailPro recovered https://status.tourpaq.com/ Mon, 04 May 2026 09:20:14 +0000 https://status.tourpaq.com/#c8feac60c8ea61d5ba9559c21d041e7caed2849a60eda69b1d1088440a5f839f AvailPro went down https://status.tourpaq.com/ Sat, 25 Apr 2026 18:20:55 +0000 https://status.tourpaq.com/#596c9b20e142205f5e0ed995d6ede9ba97f296616d31a95cea5c2f504a5a4e17 Elastic Offers recovered https://status.tourpaq.com/ Sat, 25 Apr 2026 18:18:25 +0000 https://status.tourpaq.com/#596c9b20e142205f5e0ed995d6ede9ba97f296616d31a95cea5c2f504a5a4e17 Elastic Offers went down https://status.tourpaq.com/ Sun, 19 Apr 2026 00:24:03 +0000 https://status.tourpaq.com/#b1eaf0c9baf0575c6a8a0811fd72ca1be74fea2d55aeda5ea041eab9e7adfb93 Elastic Offers recovered https://status.tourpaq.com/ Sun, 19 Apr 2026 00:21:24 +0000 https://status.tourpaq.com/#b1eaf0c9baf0575c6a8a0811fd72ca1be74fea2d55aeda5ea041eab9e7adfb93 Elastic Offers went down https://status.tourpaq.com/ Fri, 20 Mar 2026 10:49:16 +0000 https://status.tourpaq.com/#36cb5fa0bd80f675a432e29c2240dde90fd60376fd0f8dfd94370409203afc0e Payments Gateway recovered https://status.tourpaq.com/ Fri, 20 Mar 2026 10:46:19 +0000 https://status.tourpaq.com/#36cb5fa0bd80f675a432e29c2240dde90fd60376fd0f8dfd94370409203afc0e Payments Gateway went down https://status.tourpaq.com/ Thu, 12 Mar 2026 16:37:13 +0000 https://status.tourpaq.com/#38b5cab096c18197d06d46d0e3a57e1647e115fb6d01227f8e49eb1dc1eeb980 AvailPro recovered https://status.tourpaq.com/ Thu, 12 Mar 2026 16:35:39 +0000 https://status.tourpaq.com/#4a25e6bdde629c4997b4ae59aa68d0719ba47d2a583c7547abf2088129ad1c09 Email / SMS Services recovered https://status.tourpaq.com/ Thu, 12 Mar 2026 16:31:13 +0000 https://status.tourpaq.com/#38b5cab096c18197d06d46d0e3a57e1647e115fb6d01227f8e49eb1dc1eeb980 AvailPro went down https://status.tourpaq.com/ Thu, 12 Mar 2026 16:29:43 +0000 https://status.tourpaq.com/#4a25e6bdde629c4997b4ae59aa68d0719ba47d2a583c7547abf2088129ad1c09 Email / SMS Services went down https://status.tourpaq.com/incident/624418 Wed, 23 Jul 2025 08:57:00 -0000 https://status.tourpaq.com/incident/624418#cd94289e28faeda01ea6a7b63d7cf723e2c7738154a5d59b6c3a7ac69e731acc We experienced a brief outage due to an AKS autoscaling issue, which was identified and resolved. All systems are fully operational. https://status.tourpaq.com/incident/624418 Wed, 23 Jul 2025 08:54:00 -0000 https://status.tourpaq.com/incident/624418#1f003d54f96ed71dd6ab0c0933de6b86317e04f1fe334c7da2939434854f9def We're currently experiencing an outage due to aks autoscaling. The issue is under investigation. https://status.tourpaq.com/incident/575564 Thu, 22 May 2025 12:37:00 -0000 https://status.tourpaq.com/incident/575564#92cdfb995f5ba6a9c6c5893c8d4f4e596ec8173de9449d85fb547c435052720b The issue has been mitigated. The database lock was cleared and error rates returned to normal. All systems are currently operating as expected. https://status.tourpaq.com/incident/575564 Thu, 22 May 2025 12:30:00 -0000 https://status.tourpaq.com/incident/575564#1b49a55864f76ae8fcecbfb7a1cdec08884907b9339e659f425d479fb7205e07 The database connection pool was exhausted due to a spike in queries. This led to resource saturation (CPU/memory or disk I/O), preventing the database from handling new connections. Immediate Actions Taken: Restarted SQL Server Increased connection timeout threshold to prevent cascading failures https://status.tourpaq.com/incident/575564 Thu, 22 May 2025 12:18:00 -0000 https://status.tourpaq.com/incident/575564#dab78bfeaeb33a161f40b580b054781b35cc3c25ccff84f3493488aac2203cd0 The production database became unresponsive, causing application-level timeouts and service degradation across all services. Users experienced slow response times, failed authentication, and in some cases, complete service outages. https://status.tourpaq.com/incident/567383 Fri, 16 May 2025 12:00:00 -0000 https://status.tourpaq.com/incident/567383#6193d84d2628fa76c689e69620917d5546c4989c6669f0eabfdd50c4dae655f3 The AKS node pool has fully recovered. All services are now up and running as expected. Impact: Service degradation has been resolved. Systems are operating normally. https://status.tourpaq.com/incident/567383 Fri, 16 May 2025 11:56:00 -0000 https://status.tourpaq.com/incident/567383#b4ca36790142a65ba85746110d89ea5f1e2c7eced518bf7060ce763a41ecc8f8 The issue causing the AKS node pool crash has been identified and corrected. However, services remain degraded as we wait for the node pool to fully recover. Current Impact: Partial service degradation. Some workloads may be unavailable or slow to respond. https://status.tourpaq.com/incident/567383 Fri, 16 May 2025 11:48:00 -0000 https://status.tourpaq.com/incident/567383#7de7735d31360bbd31b778407c494332d2ffc425b51f2b14eba96d5f3eb063ed One important AKS node pool has crashed. Our team is actively investigating the root cause. https://status.tourpaq.com/incident/564102 Wed, 14 May 2025 11:55:00 -0000 https://status.tourpaq.com/incident/564102#e10c3465eccce189a4c967b54d6bc9d7fb880091ee484c998c8e0d77aefd8ad8 The issue has been mitigated. The database lock was cleared and error rates returned to normal. All systems are currently operating as expected. https://status.tourpaq.com/incident/564102 Wed, 14 May 2025 11:41:00 -0000 https://status.tourpaq.com/incident/564102#03b2fcfcc412d6fcf6c6c0bb428f8c98027aad9cdd2a542fa76347d04ba87eda On 14/05/2025 14:41 EEST, a database lock occurred, which led to a cascade of application errors across multiple services. Investigation is in progress. https://status.tourpaq.com/incident/555370 Tue, 29 Apr 2025 09:27:00 -0000 https://status.tourpaq.com/incident/555370#c2b9552797b4752bf8e3e371bcdb0c403f6c706ee77d08db67d1e787bf7d4a55 The issue impacting services in the Azure West Europe region has been fully resolved. All systems are now operating normally. We will continue to monitor performance closely. Thank you for your patience during this incident. https://status.tourpaq.com/incident/555370 Tue, 29 Apr 2025 09:17:00 -0000 https://status.tourpaq.com/incident/555370#9dd058238dc7728a4fec35489277859de4b609552b374fef2aea531ada2557c3 We are currently experiencing service disruptions affecting our infrastructure in the Azure West Europe region. Our team is actively investigating and working with Microsoft to resolve the issue. We expect services to return to normal within the next 5–10 minutes. We appreciate your patience and will provide another update shortly. https://status.tourpaq.com/incident/542964 Thu, 10 Apr 2025 06:42:00 -0000 https://status.tourpaq.com/incident/542964#5fc82770a8b2dbb4afc349dac2194bc773f98eb93402c2e7e7860e1c445f4d65 The issue has been mitigated. The database lock was cleared, error rates returned to normal, and Kubernetes has stabilized. All systems are currently operating as expected. https://status.tourpaq.com/incident/542964 Thu, 10 Apr 2025 06:35:00 -0000 https://status.tourpaq.com/incident/542964#1b29dc7d7c9a203ce0810321a5e9e047c52263793b3a79917b0177fa40a55ac9 On 04/10/2025 09:35 EEST, a critical database lock occurred, which led to a cascade of application errors across multiple services. Due to the increased error rate and failing health checks, Kubernetes initiated a full node recycling process in an attempt to recover. This aggressive recovery mechanism caused widespread disruption, including temporary downtime and service instability. Root cause analysis points to the locked database as the initial trigger, compounded by insufficient error handling and aggressive liveness probe configurations.