Incidents reported on status page for Tourpaq™ https://status.tourpaq.com/ en 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/ Thu, 26 Feb 2026 14:33:10 +0000 https://status.tourpaq.com/#15029bc88a3ee9ab3996701837eecc25b99d360e069357cc8fc7d7f9e3ceec9e Elastic Offers recovered https://status.tourpaq.com/ Thu, 26 Feb 2026 14:30:04 +0000 https://status.tourpaq.com/#15029bc88a3ee9ab3996701837eecc25b99d360e069357cc8fc7d7f9e3ceec9e Elastic Offers went down https://status.tourpaq.com/ Tue, 24 Feb 2026 15:30:07 +0000 https://status.tourpaq.com/#1e6a93c97c0edda707c6bf6c3f20e25bb4d6dea8d8dcf70ac2368eec333fdad9 Elastic Offers recovered https://status.tourpaq.com/ Tue, 24 Feb 2026 15:26:58 +0000 https://status.tourpaq.com/#1e6a93c97c0edda707c6bf6c3f20e25bb4d6dea8d8dcf70ac2368eec333fdad9 Elastic Offers went down https://status.tourpaq.com/ Tue, 24 Feb 2026 06:43:12 +0000 https://status.tourpaq.com/#5ebc71a6bd626cd88a111ab4b76df2cccf1c5a554d7cd19dd37713aec7ad4698 AvailPro recovered https://status.tourpaq.com/ Tue, 24 Feb 2026 06:40:08 +0000 https://status.tourpaq.com/#5ebc71a6bd626cd88a111ab4b76df2cccf1c5a554d7cd19dd37713aec7ad4698 AvailPro went down https://status.tourpaq.com/ Tue, 24 Feb 2026 06:30:39 +0000 https://status.tourpaq.com/#48187df39966e3c54818ca87305744ce7cd5b1beb0442054d41af24f81928395 Booking Engine recovered https://status.tourpaq.com/ Tue, 24 Feb 2026 06:28:16 +0000 https://status.tourpaq.com/#48187df39966e3c54818ca87305744ce7cd5b1beb0442054d41af24f81928395 Booking Engine went down https://status.tourpaq.com/ Fri, 13 Feb 2026 13:32:54 +0000 https://status.tourpaq.com/#4e79410bf60aacd03e4d17ca8400fb45646887410f9dfedc51ed0abeef39f6c6 Elastic Offers recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 13:15:59 +0000 https://status.tourpaq.com/#4e79410bf60aacd03e4d17ca8400fb45646887410f9dfedc51ed0abeef39f6c6 Elastic Offers went down https://status.tourpaq.com/ Fri, 13 Feb 2026 13:02:56 +0000 https://status.tourpaq.com/#81c4a4bae830a1781763cd54fddb38be701057c1179302296c6e393b75ab0b0f Elastic Offers recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 12:57:38 +0000 https://status.tourpaq.com/#00ddc9b1deeaee82542599aa696a3a8a3d6fa3a95785ace6737508da29da1d68 Booking Engine recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 12:54:37 +0000 https://status.tourpaq.com/#00ddc9b1deeaee82542599aa696a3a8a3d6fa3a95785ace6737508da29da1d68 Booking Engine went down https://status.tourpaq.com/ Fri, 13 Feb 2026 12:51:55 +0000 https://status.tourpaq.com/#81c4a4bae830a1781763cd54fddb38be701057c1179302296c6e393b75ab0b0f Elastic Offers went down https://status.tourpaq.com/ Fri, 13 Feb 2026 11:38:54 +0000 https://status.tourpaq.com/#20c050a09773b3e420572ca324c055c1d5c16bc68311b3d9d41e008a70f021d8 Elastic Offers recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 11:26:55 +0000 https://status.tourpaq.com/#20c050a09773b3e420572ca324c055c1d5c16bc68311b3d9d41e008a70f021d8 Elastic Offers went down https://status.tourpaq.com/ Fri, 13 Feb 2026 09:35:56 +0000 https://status.tourpaq.com/#02ad8bdf3f86cf8e11e349264d9fe01f3c9918f2a0aa794b52383ce74e16ede2 Elastic Offers recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 09:20:55 +0000 https://status.tourpaq.com/#02ad8bdf3f86cf8e11e349264d9fe01f3c9918f2a0aa794b52383ce74e16ede2 Elastic Offers went down https://status.tourpaq.com/ Fri, 13 Feb 2026 08:42:37 +0000 https://status.tourpaq.com/#ff57b2315811f697dc797f661453fc9d2f523a9faf36d5142980b1cdf4f4ba7f Booking Engine recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 08:39:35 +0000 https://status.tourpaq.com/#ff57b2315811f697dc797f661453fc9d2f523a9faf36d5142980b1cdf4f4ba7f Booking Engine went down https://status.tourpaq.com/ Fri, 13 Feb 2026 08:38:55 +0000 https://status.tourpaq.com/#e8f3aa25a1bbce1037084e475f561bec3f6ac93dbf5548c7fa4987e6fda6e0f7 Elastic Offers recovered https://status.tourpaq.com/ Fri, 13 Feb 2026 08:32:54 +0000 https://status.tourpaq.com/#e8f3aa25a1bbce1037084e475f561bec3f6ac93dbf5548c7fa4987e6fda6e0f7 Elastic Offers went down https://status.tourpaq.com/ Fri, 06 Feb 2026 21:52:20 +0000 https://status.tourpaq.com/#20704ba2ff3f3322d70f2b46dd3c763c14e8b514e61e2964567296ff78a0e0c7 Payments Gateway recovered https://status.tourpaq.com/ Fri, 06 Feb 2026 21:49:16 +0000 https://status.tourpaq.com/#20704ba2ff3f3322d70f2b46dd3c763c14e8b514e61e2964567296ff78a0e0c7 Payments Gateway went down https://status.tourpaq.com/ Sun, 18 Jan 2026 01:16:11 +0000 https://status.tourpaq.com/#7e880ef0cc4de3dab177f8e1b00bd2bd1d00cfcff98e8b81693e799d9dff0057 AvailPro recovered https://status.tourpaq.com/ Sun, 18 Jan 2026 01:15:40 +0000 https://status.tourpaq.com/#5e88530f35adf29bad2cbe24fa2a8f872f5d7ac969f9e86c26ebefca9925b2a0 Booking Engine recovered https://status.tourpaq.com/ Sun, 18 Jan 2026 01:14:09 +0000 https://status.tourpaq.com/#7e880ef0cc4de3dab177f8e1b00bd2bd1d00cfcff98e8b81693e799d9dff0057 AvailPro went down https://status.tourpaq.com/ Sun, 18 Jan 2026 01:13:42 +0000 https://status.tourpaq.com/#5e88530f35adf29bad2cbe24fa2a8f872f5d7ac969f9e86c26ebefca9925b2a0 Booking Engine went down https://status.tourpaq.com/ Fri, 16 Jan 2026 03:04:21 +0000 https://status.tourpaq.com/#d3e122a283ac9bcf0dec9b22f08672408fc290c0b733b3721d7db3aa9a71f6bf Payments Gateway recovered https://status.tourpaq.com/ Fri, 16 Jan 2026 03:01:19 +0000 https://status.tourpaq.com/#d3e122a283ac9bcf0dec9b22f08672408fc290c0b733b3721d7db3aa9a71f6bf Payments Gateway went down https://status.tourpaq.com/ Fri, 16 Jan 2026 02:10:11 +0000 https://status.tourpaq.com/#f94683e9bc5ed849c3e659d49ca96c13b7ed775cab5d67522dd9d8c3aa61f9fd AvailPro recovered https://status.tourpaq.com/ Fri, 16 Jan 2026 02:07:09 +0000 https://status.tourpaq.com/#f94683e9bc5ed849c3e659d49ca96c13b7ed775cab5d67522dd9d8c3aa61f9fd AvailPro 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.