Incidents | Intempt Technologies Incidents reported on status page for Intempt Technologies https://status.intempt.com/ https://d1lppblt9t2x15.cloudfront.net/logos/fdb0546bbb0ed17c478a746dbf72fce6.png Incidents | Intempt Technologies https://status.intempt.com/ en Analytics Services recovered https://status.intempt.com/ Mon, 30 Jun 2025 07:44:50 +0000 https://status.intempt.com/#8a164f1e443f83f1414d247ee2a96c0cb84a709abe5df71564a2267009104f04 Analytics Services recovered Messaging Services recovered https://status.intempt.com/ Sun, 29 Jun 2025 13:28:09 +0000 https://status.intempt.com/#b97ed2af32b19d57a68295d32ad753d7af831d9bf15bd7bafe1db9a9b1da69ad Messaging Services recovered Audience Services recovered https://status.intempt.com/ Sun, 29 Jun 2025 13:19:04 +0000 https://status.intempt.com/#d3fc0b9142f6287c082749f17ec6f1cfe232d778cb3180164d2faf89ee46a75d Audience Services recovered Data Services recovered https://status.intempt.com/ Sun, 29 Jun 2025 13:19:04 +0000 https://status.intempt.com/#cfbb41787f681748c578d3ffddf768a29ea5b3018dc5d74fea2c5ccfe47e4ecd Data Services recovered Experience Services recovered https://status.intempt.com/ Sun, 29 Jun 2025 13:13:47 +0000 https://status.intempt.com/#dcea698bd4c3a490fcfef180a6b54041b8fb60cdc6cb8f3dbad96c2b5a08e379 Experience Services recovered Audience Services went down https://status.intempt.com/ Sun, 29 Jun 2025 12:35:47 +0000 https://status.intempt.com/#d3fc0b9142f6287c082749f17ec6f1cfe232d778cb3180164d2faf89ee46a75d Audience Services went down Messaging Services went down https://status.intempt.com/ Sun, 29 Jun 2025 12:35:09 +0000 https://status.intempt.com/#b97ed2af32b19d57a68295d32ad753d7af831d9bf15bd7bafe1db9a9b1da69ad Messaging Services went down Data Services went down https://status.intempt.com/ Sun, 29 Jun 2025 12:35:09 +0000 https://status.intempt.com/#cfbb41787f681748c578d3ffddf768a29ea5b3018dc5d74fea2c5ccfe47e4ecd Data Services went down Analytics Services went down https://status.intempt.com/ Sun, 29 Jun 2025 12:33:32 +0000 https://status.intempt.com/#8a164f1e443f83f1414d247ee2a96c0cb84a709abe5df71564a2267009104f04 Analytics Services went down Experience Services went down https://status.intempt.com/ Sun, 29 Jun 2025 12:26:33 +0000 https://status.intempt.com/#dcea698bd4c3a490fcfef180a6b54041b8fb60cdc6cb8f3dbad96c2b5a08e379 Experience Services went down Experience Services recovered https://status.intempt.com/ Sun, 29 Jun 2025 09:28:25 +0000 https://status.intempt.com/#2437bf1aa44c974abcdb3228c2757abe84c145d58b3c08c50bcf794ac9f45b01 Experience Services recovered Experience Services went down https://status.intempt.com/ Sun, 29 Jun 2025 09:22:50 +0000 https://status.intempt.com/#2437bf1aa44c974abcdb3228c2757abe84c145d58b3c08c50bcf794ac9f45b01 Experience Services went down Analytics Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 14:38:10 +0000 https://status.intempt.com/#963b9e9d0b0605eccd2ad954d792acfebb97b84c183f13324410c223889e6f3b Analytics Services recovered Analytics Services went down https://status.intempt.com/ Thu, 26 Jun 2025 14:26:39 +0000 https://status.intempt.com/#963b9e9d0b0605eccd2ad954d792acfebb97b84c183f13324410c223889e6f3b Analytics Services went down Messaging Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 06:25:06 +0000 https://status.intempt.com/#2d924a0e0b716da36ef53f2bddb8dbd6b6803f3d51cb75a8e28899014ef5b9f7 Messaging Services recovered Data Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 06:25:06 +0000 https://status.intempt.com/#e0e6205d02678a6060b7284661efee3dda7d42254452d83711094ca6e8e6c764 Data Services recovered Audience Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 06:25:06 +0000 https://status.intempt.com/#544ad084ff019b805caafe553294df8821b3bc59f5bcde9615660ffddea267bc Audience Services recovered Data Services went down https://status.intempt.com/ Thu, 26 Jun 2025 06:16:12 +0000 https://status.intempt.com/#e0e6205d02678a6060b7284661efee3dda7d42254452d83711094ca6e8e6c764 Data Services went down Audience Services went down https://status.intempt.com/ Thu, 26 Jun 2025 06:16:11 +0000 https://status.intempt.com/#544ad084ff019b805caafe553294df8821b3bc59f5bcde9615660ffddea267bc Audience Services went down Messaging Services went down https://status.intempt.com/ Thu, 26 Jun 2025 06:16:11 +0000 https://status.intempt.com/#2d924a0e0b716da36ef53f2bddb8dbd6b6803f3d51cb75a8e28899014ef5b9f7 Messaging Services went down Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:30:00 +0000 https://status.intempt.com/incident/609405#2b42bc109584374badd1d45ea313893884a0e0283d02481c86541b275e37a783 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:30:00 +0000 https://status.intempt.com/incident/609405#2b42bc109584374badd1d45ea313893884a0e0283d02481c86541b275e37a783 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:30:00 +0000 https://status.intempt.com/incident/609405#2b42bc109584374badd1d45ea313893884a0e0283d02481c86541b275e37a783 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:30:00 +0000 https://status.intempt.com/incident/609405#2b42bc109584374badd1d45ea313893884a0e0283d02481c86541b275e37a783 Maintenance completed Messaging Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 05:27:43 +0000 https://status.intempt.com/#a901121a56437d8310743c83ad10f3af17e6fba0819faa495b00244da9c5ede7 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 05:27:43 +0000 https://status.intempt.com/#15e25bc18e16cf51ef67bdccdafb4ff3c45b1ed492936a5ab11ae39f7ae70643 Audience Services recovered Data Services recovered https://status.intempt.com/ Thu, 26 Jun 2025 05:27:43 +0000 https://status.intempt.com/#61d437522c1d96dda6660253f881188f131f8628e8981d3a19e443371eb9be58 Data Services recovered Messaging Services went down https://status.intempt.com/ Thu, 26 Jun 2025 05:14:37 +0000 https://status.intempt.com/#a901121a56437d8310743c83ad10f3af17e6fba0819faa495b00244da9c5ede7 Messaging Services went down Data Services went down https://status.intempt.com/ Thu, 26 Jun 2025 05:14:37 +0000 https://status.intempt.com/#61d437522c1d96dda6660253f881188f131f8628e8981d3a19e443371eb9be58 Data Services went down Audience Services went down https://status.intempt.com/ Thu, 26 Jun 2025 05:14:37 +0000 https://status.intempt.com/#15e25bc18e16cf51ef67bdccdafb4ff3c45b1ed492936a5ab11ae39f7ae70643 Audience Services went down Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:10:00 -0000 https://status.intempt.com/incident/609405#2c5bf6e2663886e6371dd1a0c6436cc5b2f711dd8b5a2819a4021b112ed091ef We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:10:00 -0000 https://status.intempt.com/incident/609405#2c5bf6e2663886e6371dd1a0c6436cc5b2f711dd8b5a2819a4021b112ed091ef We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:10:00 -0000 https://status.intempt.com/incident/609405#2c5bf6e2663886e6371dd1a0c6436cc5b2f711dd8b5a2819a4021b112ed091ef We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/609405 Thu, 26 Jun 2025 05:10:00 -0000 https://status.intempt.com/incident/609405#2c5bf6e2663886e6371dd1a0c6436cc5b2f711dd8b5a2819a4021b112ed091ef We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 20:50:00 +0000 https://status.intempt.com/incident/608439#73344924132aa5071d0afb7dba2d09ab5c770b70037169f97669ce4690d21b2a Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 20:50:00 +0000 https://status.intempt.com/incident/608439#73344924132aa5071d0afb7dba2d09ab5c770b70037169f97669ce4690d21b2a Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 20:50:00 +0000 https://status.intempt.com/incident/608439#73344924132aa5071d0afb7dba2d09ab5c770b70037169f97669ce4690d21b2a Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 20:50:00 +0000 https://status.intempt.com/incident/608439#73344924132aa5071d0afb7dba2d09ab5c770b70037169f97669ce4690d21b2a Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 20:50:00 +0000 https://status.intempt.com/incident/608439#73344924132aa5071d0afb7dba2d09ab5c770b70037169f97669ce4690d21b2a Maintenance completed Data Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 19:45:11 +0000 https://status.intempt.com/#703c23fcecac9a06d5ea380e8d9cacb1b08c26da70a1b4c195254accedc9e9fc Data Services recovered Messaging Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 19:45:10 +0000 https://status.intempt.com/#9cd05f85cf417b6b6f5d410623bd2bd9267b5ea8e3df7f8e8fee0838c180ff27 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 19:45:08 +0000 https://status.intempt.com/#c9d8e69c3c47817c3dd3bc5bc8a406aa1ece391a4d833c3976efe0b3034493af Audience Services recovered Audience Services went down https://status.intempt.com/ Tue, 24 Jun 2025 19:23:06 +0000 https://status.intempt.com/#c9d8e69c3c47817c3dd3bc5bc8a406aa1ece391a4d833c3976efe0b3034493af Audience Services went down Messaging Services went down https://status.intempt.com/ Tue, 24 Jun 2025 19:22:52 +0000 https://status.intempt.com/#9cd05f85cf417b6b6f5d410623bd2bd9267b5ea8e3df7f8e8fee0838c180ff27 Messaging Services went down Data Services went down https://status.intempt.com/ Tue, 24 Jun 2025 19:22:52 +0000 https://status.intempt.com/#703c23fcecac9a06d5ea380e8d9cacb1b08c26da70a1b4c195254accedc9e9fc Data Services went down Messaging Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 18:58:52 +0000 https://status.intempt.com/#0dab814c8edf0f138d5f0744620e39d853f5c5473de0af921cbe11c11e3bd66c Messaging Services recovered Audience Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 18:58:52 +0000 https://status.intempt.com/#e8c09a9ba1a64ba6d479dbaf33a6d37e06925a02aa3755a576b799e9dc9f3d12 Audience Services recovered Data Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 18:58:52 +0000 https://status.intempt.com/#63edbc7751c2dd42156086aa7b1bd4ca395d36f5102df8c7b5eb8cd77cad478e Data Services recovered Audience Services went down https://status.intempt.com/ Tue, 24 Jun 2025 18:52:45 +0000 https://status.intempt.com/#e8c09a9ba1a64ba6d479dbaf33a6d37e06925a02aa3755a576b799e9dc9f3d12 Audience Services went down Messaging Services went down https://status.intempt.com/ Tue, 24 Jun 2025 18:52:45 +0000 https://status.intempt.com/#0dab814c8edf0f138d5f0744620e39d853f5c5473de0af921cbe11c11e3bd66c Messaging Services went down Data Services went down https://status.intempt.com/ Tue, 24 Jun 2025 18:52:45 +0000 https://status.intempt.com/#63edbc7751c2dd42156086aa7b1bd4ca395d36f5102df8c7b5eb8cd77cad478e Data Services went down Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 17:48:00 -0000 https://status.intempt.com/incident/608439#60e12471f4ee8e8c653dfe94d09c05775cc6f6ce7becd1201c882d9a1f5eeb23 We are currently maintaining our CDP. Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 17:48:00 -0000 https://status.intempt.com/incident/608439#60e12471f4ee8e8c653dfe94d09c05775cc6f6ce7becd1201c882d9a1f5eeb23 We are currently maintaining our CDP. Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 17:48:00 -0000 https://status.intempt.com/incident/608439#60e12471f4ee8e8c653dfe94d09c05775cc6f6ce7becd1201c882d9a1f5eeb23 We are currently maintaining our CDP. Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 17:48:00 -0000 https://status.intempt.com/incident/608439#60e12471f4ee8e8c653dfe94d09c05775cc6f6ce7becd1201c882d9a1f5eeb23 We are currently maintaining our CDP. Customer Data Platform update https://status.intempt.com/incident/608439 Tue, 24 Jun 2025 17:48:00 -0000 https://status.intempt.com/incident/608439#60e12471f4ee8e8c653dfe94d09c05775cc6f6ce7becd1201c882d9a1f5eeb23 We are currently maintaining our CDP. Messaging Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 06:26:11 +0000 https://status.intempt.com/#78a2a050ea0cd3566519457b7f7663166e0544631b35b29379ca6e6f852e90b2 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 06:26:10 +0000 https://status.intempt.com/#30731e92423a211184b64a276e9ff6b86b39ef01d40b56ad8badf9ec98abd548 Audience Services recovered Data Services recovered https://status.intempt.com/ Tue, 24 Jun 2025 06:26:10 +0000 https://status.intempt.com/#5803880916967bc23e00ae62161bf810fe580a2bc6734557e54030dc47b1dfbb Data Services recovered Messaging Services went down https://status.intempt.com/ Tue, 24 Jun 2025 06:17:42 +0000 https://status.intempt.com/#78a2a050ea0cd3566519457b7f7663166e0544631b35b29379ca6e6f852e90b2 Messaging Services went down Audience Services went down https://status.intempt.com/ Tue, 24 Jun 2025 06:17:41 +0000 https://status.intempt.com/#30731e92423a211184b64a276e9ff6b86b39ef01d40b56ad8badf9ec98abd548 Audience Services went down Data Services went down https://status.intempt.com/ Tue, 24 Jun 2025 06:17:40 +0000 https://status.intempt.com/#5803880916967bc23e00ae62161bf810fe580a2bc6734557e54030dc47b1dfbb Data Services went down Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:50:00 +0000 https://status.intempt.com/incident/608101#6c3279a9f6917ce394b7c07907a2132a656229ba443ec951bb84bae13dcc6054 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:50:00 +0000 https://status.intempt.com/incident/608101#6c3279a9f6917ce394b7c07907a2132a656229ba443ec951bb84bae13dcc6054 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:50:00 +0000 https://status.intempt.com/incident/608101#6c3279a9f6917ce394b7c07907a2132a656229ba443ec951bb84bae13dcc6054 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:50:00 +0000 https://status.intempt.com/incident/608101#6c3279a9f6917ce394b7c07907a2132a656229ba443ec951bb84bae13dcc6054 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:50:00 +0000 https://status.intempt.com/incident/608101#6c3279a9f6917ce394b7c07907a2132a656229ba443ec951bb84bae13dcc6054 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:00:00 -0000 https://status.intempt.com/incident/608101#eb2b05ba2ac6888a9d1fab8273cbcd1f26421a2003d4d5cc2f445e2836175992 We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:00:00 -0000 https://status.intempt.com/incident/608101#eb2b05ba2ac6888a9d1fab8273cbcd1f26421a2003d4d5cc2f445e2836175992 We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:00:00 -0000 https://status.intempt.com/incident/608101#eb2b05ba2ac6888a9d1fab8273cbcd1f26421a2003d4d5cc2f445e2836175992 We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:00:00 -0000 https://status.intempt.com/incident/608101#eb2b05ba2ac6888a9d1fab8273cbcd1f26421a2003d4d5cc2f445e2836175992 We are updating our Customer Data Platform. Customer Data Platform update https://status.intempt.com/incident/608101 Tue, 24 Jun 2025 05:00:00 -0000 https://status.intempt.com/incident/608101#eb2b05ba2ac6888a9d1fab8273cbcd1f26421a2003d4d5cc2f445e2836175992 We are updating our Customer Data Platform. Messaging Services recovered https://status.intempt.com/ Mon, 23 Jun 2025 14:29:05 +0000 https://status.intempt.com/#0f7b4d0190d9ecc5276f014e73d81e46645f1e3f6090bb57237b0b62c7e1da83 Messaging Services recovered Journey update https://status.intempt.com/incident/607704 Mon, 23 Jun 2025 14:25:17 +0000 https://status.intempt.com/incident/607704#9ca45d580f033732ee640f0db21cd5168f84038e0e122d126c7e6e0f1a04f65d Maintenance completed Messaging Services went down https://status.intempt.com/ Mon, 23 Jun 2025 14:15:35 +0000 https://status.intempt.com/#0f7b4d0190d9ecc5276f014e73d81e46645f1e3f6090bb57237b0b62c7e1da83 Messaging Services went down Journey update https://status.intempt.com/incident/607704 Mon, 23 Jun 2025 14:11:17 -0000 https://status.intempt.com/incident/607704#6d5dac4abdd47d63b04709bb7d0d909acf5c9da45e582b0eead7da3c376c21cb We’re excited to introduce a powerful set of enhancements to our Journey system: Adding journey schedulable actions, with the ability to send email, sms, and push in specific time windows. Messaging Services recovered https://status.intempt.com/ Fri, 20 Jun 2025 13:07:04 +0000 https://status.intempt.com/#4e7b727a5b48b45332bc8e347c871237a4d93024d9bf195674fe057a28895558 Messaging Services recovered Data Services recovered https://status.intempt.com/ Fri, 20 Jun 2025 13:07:04 +0000 https://status.intempt.com/#f1dc137e1f0a7207d6841f97f8e7de010eca3e71bce6b1b3df39ecfbc97ee5b6 Data Services recovered Audience Services recovered https://status.intempt.com/ Fri, 20 Jun 2025 13:07:04 +0000 https://status.intempt.com/#793a8799c5dd5fbd0c8de159d694d6a8167c7b83b6051ba2489246998bb4e858 Audience Services recovered Audience Services went down https://status.intempt.com/ Fri, 20 Jun 2025 12:52:41 +0000 https://status.intempt.com/#793a8799c5dd5fbd0c8de159d694d6a8167c7b83b6051ba2489246998bb4e858 Audience Services went down Data Services went down https://status.intempt.com/ Fri, 20 Jun 2025 12:52:41 +0000 https://status.intempt.com/#f1dc137e1f0a7207d6841f97f8e7de010eca3e71bce6b1b3df39ecfbc97ee5b6 Data Services went down Messaging Services went down https://status.intempt.com/ Fri, 20 Jun 2025 12:52:40 +0000 https://status.intempt.com/#4e7b727a5b48b45332bc8e347c871237a4d93024d9bf195674fe057a28895558 Messaging Services went down Messaging Services recovered https://status.intempt.com/ Fri, 20 Jun 2025 10:12:07 +0000 https://status.intempt.com/#39988623d1b262b57557e9bdb06ea5b490b6b31f3de1eb889fbaa1686631f688 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Fri, 20 Jun 2025 10:12:07 +0000 https://status.intempt.com/#0462099de26c144bbfea23db988169b29dfed39b3ead732c8c616f7f97bb1118 Audience Services recovered Data Services recovered https://status.intempt.com/ Fri, 20 Jun 2025 10:12:07 +0000 https://status.intempt.com/#bba8d2c01a5d831bd3611c30416277f6f99d9d21d7116e2c2c949a16dbbb8039 Data Services recovered Audience Services went down https://status.intempt.com/ Fri, 20 Jun 2025 09:58:35 +0000 https://status.intempt.com/#0462099de26c144bbfea23db988169b29dfed39b3ead732c8c616f7f97bb1118 Audience Services went down Messaging Services went down https://status.intempt.com/ Fri, 20 Jun 2025 09:58:35 +0000 https://status.intempt.com/#39988623d1b262b57557e9bdb06ea5b490b6b31f3de1eb889fbaa1686631f688 Messaging Services went down Data Services went down https://status.intempt.com/ Fri, 20 Jun 2025 09:58:35 +0000 https://status.intempt.com/#bba8d2c01a5d831bd3611c30416277f6f99d9d21d7116e2c2c949a16dbbb8039 Data Services went down Messaging Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 21:32:19 +0000 https://status.intempt.com/#770d450d39d5d87cbbd49211e38f9520e4f049f693050228bd6b4075bd451286 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 21:32:18 +0000 https://status.intempt.com/#bd161bd8bd66c34e28a23cbbe116ee901a6e26f144099e53691391cd4dce9190 Audience Services recovered Data Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 21:32:17 +0000 https://status.intempt.com/#7911b0ac69a95e87c3ed8bf2097cfe8497d30e78086c27164eb259c78dbea9e3 Data Services recovered Messaging Services went down https://status.intempt.com/ Thu, 19 Jun 2025 21:20:43 +0000 https://status.intempt.com/#770d450d39d5d87cbbd49211e38f9520e4f049f693050228bd6b4075bd451286 Messaging Services went down Data Services went down https://status.intempt.com/ Thu, 19 Jun 2025 21:20:43 +0000 https://status.intempt.com/#7911b0ac69a95e87c3ed8bf2097cfe8497d30e78086c27164eb259c78dbea9e3 Data Services went down Audience Services went down https://status.intempt.com/ Thu, 19 Jun 2025 21:20:41 +0000 https://status.intempt.com/#bd161bd8bd66c34e28a23cbbe116ee901a6e26f144099e53691391cd4dce9190 Audience Services went down Messaging Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 20:27:30 +0000 https://status.intempt.com/#99de5be728d445b0340e4c6aa7aec6befa6f82c27ad094029b7b1ebdaad2c23c Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 20:27:29 +0000 https://status.intempt.com/#279a4592bc799dda2384ca9b02cd748d08c911965be6fd321b8bd08b3cb752d4 Audience Services recovered Data Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 20:27:29 +0000 https://status.intempt.com/#2ad6fe944dad2f7f2963a04d40683062121b931555cb07dc21b23c7bff574d6b Data Services recovered Messaging Services went down https://status.intempt.com/ Thu, 19 Jun 2025 20:15:55 +0000 https://status.intempt.com/#99de5be728d445b0340e4c6aa7aec6befa6f82c27ad094029b7b1ebdaad2c23c Messaging Services went down Audience Services went down https://status.intempt.com/ Thu, 19 Jun 2025 20:15:55 +0000 https://status.intempt.com/#279a4592bc799dda2384ca9b02cd748d08c911965be6fd321b8bd08b3cb752d4 Audience Services went down Data Services went down https://status.intempt.com/ Thu, 19 Jun 2025 20:15:55 +0000 https://status.intempt.com/#2ad6fe944dad2f7f2963a04d40683062121b931555cb07dc21b23c7bff574d6b Data Services went down Messaging Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 19:15:52 +0000 https://status.intempt.com/#b69f049c5b7551f184d3609324641fe34d9f2b0e45dddaacdf3f7f67a7c726ce Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 19:15:52 +0000 https://status.intempt.com/#b8ccc03287685ada68a6d0706e6d406e82fabb9a27eebe2528b3a883390492f7 Audience Services recovered Data Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 19:15:52 +0000 https://status.intempt.com/#075d441079f0ab8e8ba40157d013f8de8ab37debc3e009d70d47dddbcc69e74e Data Services recovered Audience Services went down https://status.intempt.com/ Thu, 19 Jun 2025 19:03:56 +0000 https://status.intempt.com/#b8ccc03287685ada68a6d0706e6d406e82fabb9a27eebe2528b3a883390492f7 Audience Services went down Messaging Services went down https://status.intempt.com/ Thu, 19 Jun 2025 19:03:56 +0000 https://status.intempt.com/#b69f049c5b7551f184d3609324641fe34d9f2b0e45dddaacdf3f7f67a7c726ce Messaging Services went down Data Services went down https://status.intempt.com/ Thu, 19 Jun 2025 19:03:56 +0000 https://status.intempt.com/#075d441079f0ab8e8ba40157d013f8de8ab37debc3e009d70d47dddbcc69e74e Data Services went down Messaging Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 17:26:17 +0000 https://status.intempt.com/#5f07d9087fe58e7d23dd7a7a550a249170bea51dae65807cd38719f5547b9214 Messaging Services recovered Data Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 17:26:17 +0000 https://status.intempt.com/#8f8f5497b4edcac4706704a8ec405a27e0d7db73c1ffc16c227ad5598e4c69e4 Data Services recovered Audience Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 17:26:17 +0000 https://status.intempt.com/#be8a8b080abdbf6f953d5435f3c08a933aab69cbac5f5563bacbd7de427f039d Audience Services recovered Data Services went down https://status.intempt.com/ Thu, 19 Jun 2025 17:06:47 +0000 https://status.intempt.com/#8f8f5497b4edcac4706704a8ec405a27e0d7db73c1ffc16c227ad5598e4c69e4 Data Services went down Messaging Services went down https://status.intempt.com/ Thu, 19 Jun 2025 17:06:46 +0000 https://status.intempt.com/#5f07d9087fe58e7d23dd7a7a550a249170bea51dae65807cd38719f5547b9214 Messaging Services went down Audience Services went down https://status.intempt.com/ Thu, 19 Jun 2025 17:06:46 +0000 https://status.intempt.com/#be8a8b080abdbf6f953d5435f3c08a933aab69cbac5f5563bacbd7de427f039d Audience Services went down Data Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 16:49:28 +0000 https://status.intempt.com/#e12bcea8039c629f855927a45539895edc3ffb4bb7e3a17cea2a93a3cbb75f47 Data Services recovered Messaging Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 16:49:28 +0000 https://status.intempt.com/#69f9881643c3725ba7f406cbce4261431907516564f8f9f1904476a07aa3a829 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 19 Jun 2025 16:49:28 +0000 https://status.intempt.com/#481d795516ddd7aeed11ee825428eb1205e98c9666c467cf89dfef403db39d11 Audience Services recovered Data Services went down https://status.intempt.com/ Thu, 19 Jun 2025 16:37:36 +0000 https://status.intempt.com/#e12bcea8039c629f855927a45539895edc3ffb4bb7e3a17cea2a93a3cbb75f47 Data Services went down Audience Services went down https://status.intempt.com/ Thu, 19 Jun 2025 16:37:36 +0000 https://status.intempt.com/#481d795516ddd7aeed11ee825428eb1205e98c9666c467cf89dfef403db39d11 Audience Services went down Messaging Services went down https://status.intempt.com/ Thu, 19 Jun 2025 16:37:36 +0000 https://status.intempt.com/#69f9881643c3725ba7f406cbce4261431907516564f8f9f1904476a07aa3a829 Messaging Services went down Data Services recovered https://status.intempt.com/ Thu, 12 Jun 2025 17:02:55 +0000 https://status.intempt.com/#1236685576cd69cb52e8cebc6e71c05417ac3e82bc8f262f99c13210023b377b Data Services recovered Messaging Services recovered https://status.intempt.com/ Thu, 12 Jun 2025 17:02:54 +0000 https://status.intempt.com/#8d393eb54302c7fea99e8c2f20d15b77d780a504d074c524f56bfd4e4693c727 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 12 Jun 2025 17:02:53 +0000 https://status.intempt.com/#cdc6c89855dfb8f865822c6398480d38416670ce0c8a3eba95dfe3896b33de84 Audience Services recovered Data Services went down https://status.intempt.com/ Thu, 12 Jun 2025 16:55:46 +0000 https://status.intempt.com/#1236685576cd69cb52e8cebc6e71c05417ac3e82bc8f262f99c13210023b377b Data Services went down Messaging Services went down https://status.intempt.com/ Thu, 12 Jun 2025 16:55:46 +0000 https://status.intempt.com/#8d393eb54302c7fea99e8c2f20d15b77d780a504d074c524f56bfd4e4693c727 Messaging Services went down Audience Services went down https://status.intempt.com/ Thu, 12 Jun 2025 16:55:45 +0000 https://status.intempt.com/#cdc6c89855dfb8f865822c6398480d38416670ce0c8a3eba95dfe3896b33de84 Audience Services went down Messaging Services recovered https://status.intempt.com/ Thu, 12 Jun 2025 15:47:19 +0000 https://status.intempt.com/#9b401fb66267ae7bf0f1dc286f22da8d249441f5940584669ff5efbe4f8ca07c Messaging Services recovered Data Services recovered https://status.intempt.com/ Thu, 12 Jun 2025 15:47:19 +0000 https://status.intempt.com/#2f5fc890f4192515488fce1851dbc7da2ff3f644d74803633377382ec00b7d07 Data Services recovered Data Services went down https://status.intempt.com/ Thu, 12 Jun 2025 15:33:48 +0000 https://status.intempt.com/#2f5fc890f4192515488fce1851dbc7da2ff3f644d74803633377382ec00b7d07 Data Services went down Messaging Services went down https://status.intempt.com/ Thu, 12 Jun 2025 15:33:48 +0000 https://status.intempt.com/#9b401fb66267ae7bf0f1dc286f22da8d249441f5940584669ff5efbe4f8ca07c Messaging Services went down Messaging Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 22:01:06 +0000 https://status.intempt.com/#c25e38d13a20248b158e7ede37d722a514692673f17a1e2bc22f41cfb87034e4 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 22:01:06 +0000 https://status.intempt.com/#b8aecd7e2b41ecb08ba158d06ec67ff4f4c4b77efabab00b199949cd8dbf2318 Audience Services recovered Data Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 22:01:05 +0000 https://status.intempt.com/#0129c8411976af7d4a2f1484fd90d31922e50364cd85e3fc483dbbbbe3b0db1e Data Services recovered Fixing blocking webhooks error https://status.intempt.com/incident/601068 Wed, 11 Jun 2025 21:57:21 +0000 https://status.intempt.com/incident/601068#e57195b82ccb63019edfaa03f36999eda4b76343f6e168875ddc99087e5108c7 Maintenance completed Fixing blocking webhooks error https://status.intempt.com/incident/601068 Wed, 11 Jun 2025 21:57:21 +0000 https://status.intempt.com/incident/601068#e57195b82ccb63019edfaa03f36999eda4b76343f6e168875ddc99087e5108c7 Maintenance completed Fixing blocking webhooks error https://status.intempt.com/incident/601068 Wed, 11 Jun 2025 21:57:21 +0000 https://status.intempt.com/incident/601068#e57195b82ccb63019edfaa03f36999eda4b76343f6e168875ddc99087e5108c7 Maintenance completed Messaging Services went down https://status.intempt.com/ Wed, 11 Jun 2025 21:50:50 +0000 https://status.intempt.com/#c25e38d13a20248b158e7ede37d722a514692673f17a1e2bc22f41cfb87034e4 Messaging Services went down Data Services went down https://status.intempt.com/ Wed, 11 Jun 2025 21:50:49 +0000 https://status.intempt.com/#0129c8411976af7d4a2f1484fd90d31922e50364cd85e3fc483dbbbbe3b0db1e Data Services went down Audience Services went down https://status.intempt.com/ Wed, 11 Jun 2025 21:50:49 +0000 https://status.intempt.com/#b8aecd7e2b41ecb08ba158d06ec67ff4f4c4b77efabab00b199949cd8dbf2318 Audience Services went down Fixing blocking webhooks error https://status.intempt.com/incident/601068 Wed, 11 Jun 2025 21:44:21 -0000 https://status.intempt.com/incident/601068#fcfcb20eb8cca1ff57f4fb6b36dc99b608e5eaf4ca026af93b329af32d571ab7 We will be fixing a regression on data flow. To apply these upgrades, core data-flow service must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Fixing blocking webhooks error https://status.intempt.com/incident/601068 Wed, 11 Jun 2025 21:44:21 -0000 https://status.intempt.com/incident/601068#fcfcb20eb8cca1ff57f4fb6b36dc99b608e5eaf4ca026af93b329af32d571ab7 We will be fixing a regression on data flow. To apply these upgrades, core data-flow service must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Fixing blocking webhooks error https://status.intempt.com/incident/601068 Wed, 11 Jun 2025 21:44:21 -0000 https://status.intempt.com/incident/601068#fcfcb20eb8cca1ff57f4fb6b36dc99b608e5eaf4ca026af93b329af32d571ab7 We will be fixing a regression on data flow. To apply these upgrades, core data-flow service must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Messaging Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 21:14:22 +0000 https://status.intempt.com/#c3cb7b2f827414db05a554017be024152ff8e3e57e72ec33e1f278286d109034 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 21:14:21 +0000 https://status.intempt.com/#af313a59434bb4637cc83bbb45ccfd8fd04f3e012b367558959582e9e0fb92fd Audience Services recovered Data Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 21:14:21 +0000 https://status.intempt.com/#0b79bbed0d56340c18cfdf17a4af15a4f4896c396bd1db05829af08076269e2e Data Services recovered Messaging Services went down https://status.intempt.com/ Wed, 11 Jun 2025 17:56:50 +0000 https://status.intempt.com/#c3cb7b2f827414db05a554017be024152ff8e3e57e72ec33e1f278286d109034 Messaging Services went down Data Services went down https://status.intempt.com/ Wed, 11 Jun 2025 17:56:50 +0000 https://status.intempt.com/#0b79bbed0d56340c18cfdf17a4af15a4f4896c396bd1db05829af08076269e2e Data Services went down Audience Services went down https://status.intempt.com/ Wed, 11 Jun 2025 17:56:50 +0000 https://status.intempt.com/#af313a59434bb4637cc83bbb45ccfd8fd04f3e012b367558959582e9e0fb92fd Audience Services went down Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 15:28:00 +0000 https://status.intempt.com/incident/600926#6fc7cba9e9d1fe9d598f3853dbb852edf507de2440a017f0139bdd1db6d7157f Maintenance completed Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 15:28:00 +0000 https://status.intempt.com/incident/600926#6fc7cba9e9d1fe9d598f3853dbb852edf507de2440a017f0139bdd1db6d7157f Maintenance completed Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 15:28:00 +0000 https://status.intempt.com/incident/600926#6fc7cba9e9d1fe9d598f3853dbb852edf507de2440a017f0139bdd1db6d7157f Maintenance completed Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 15:28:00 +0000 https://status.intempt.com/incident/600926#6fc7cba9e9d1fe9d598f3853dbb852edf507de2440a017f0139bdd1db6d7157f Maintenance completed Data Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 15:26:39 +0000 https://status.intempt.com/#2e4dc0fdf686b35d0de4c0f607446c6556a870d3c854409be2d11df35a669521 Data Services recovered Audience Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 15:26:20 +0000 https://status.intempt.com/#bbf4f320105ad84a3541a5fc241c3d6c9709b4c171100b6ce49ae900dac343f6 Audience Services recovered Messaging Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 15:22:33 +0000 https://status.intempt.com/#0cead8f851a2ec8661ceacf9a116c720a998080587c3bef08f869bf52b7dbdf9 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Wed, 11 Jun 2025 15:15:48 +0000 https://status.intempt.com/#0cead8f851a2ec8661ceacf9a116c720a998080587c3bef08f869bf52b7dbdf9 Messaging Services went down Audience Services went down https://status.intempt.com/ Wed, 11 Jun 2025 15:13:50 +0000 https://status.intempt.com/#bbf4f320105ad84a3541a5fc241c3d6c9709b4c171100b6ce49ae900dac343f6 Audience Services went down Data Services went down https://status.intempt.com/ Wed, 11 Jun 2025 15:13:50 +0000 https://status.intempt.com/#2e4dc0fdf686b35d0de4c0f607446c6556a870d3c854409be2d11df35a669521 Data Services went down Messaging Services recovered https://status.intempt.com/ Wed, 11 Jun 2025 15:10:07 +0000 https://status.intempt.com/#fd870605c90c568bb68e0854fb69ce4f0316577cf7c4349528abb701b16499d5 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Wed, 11 Jun 2025 15:04:51 +0000 https://status.intempt.com/#fd870605c90c568bb68e0854fb69ce4f0316577cf7c4349528abb701b16499d5 Messaging Services went down Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 14:58:00 -0000 https://status.intempt.com/incident/600926#cadc5aa51d9559bd05f4dcb3887fb1b96e295d8d9ecd775e55d179ee9cae4269 We will be deploying a new Error Handling flow for journeys. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 14:58:00 -0000 https://status.intempt.com/incident/600926#cadc5aa51d9559bd05f4dcb3887fb1b96e295d8d9ecd775e55d179ee9cae4269 We will be deploying a new Error Handling flow for journeys. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 14:58:00 -0000 https://status.intempt.com/incident/600926#cadc5aa51d9559bd05f4dcb3887fb1b96e295d8d9ecd775e55d179ee9cae4269 We will be deploying a new Error Handling flow for journeys. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Updating data services https://status.intempt.com/incident/600926 Wed, 11 Jun 2025 14:58:00 -0000 https://status.intempt.com/incident/600926#cadc5aa51d9559bd05f4dcb3887fb1b96e295d8d9ecd775e55d179ee9cae4269 We will be deploying a new Error Handling flow for journeys. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Audience Services recovered https://status.intempt.com/ Sat, 07 Jun 2025 17:29:23 +0000 https://status.intempt.com/#11b172329f8807dd2f77aa1c68ca49dcb45ef82c5635948f4ab5b685f51d2b84 Audience Services recovered Audience Services went down https://status.intempt.com/ Sat, 07 Jun 2025 17:23:47 +0000 https://status.intempt.com/#11b172329f8807dd2f77aa1c68ca49dcb45ef82c5635948f4ab5b685f51d2b84 Audience Services went down Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 15:00:03 +0000 https://status.intempt.com/incident/598218#a7977c8e751fce8f8aaf0be349e3dd554478294f396c06450cecc300573d5ee9 Maintenance completed Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 15:00:03 +0000 https://status.intempt.com/incident/598218#a7977c8e751fce8f8aaf0be349e3dd554478294f396c06450cecc300573d5ee9 Maintenance completed Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 15:00:03 +0000 https://status.intempt.com/incident/598218#a7977c8e751fce8f8aaf0be349e3dd554478294f396c06450cecc300573d5ee9 Maintenance completed Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 15:00:03 +0000 https://status.intempt.com/incident/598218#a7977c8e751fce8f8aaf0be349e3dd554478294f396c06450cecc300573d5ee9 Maintenance completed Messaging Services recovered https://status.intempt.com/ Fri, 06 Jun 2025 14:30:27 +0000 https://status.intempt.com/#1387d5568007732e7b6c35a3ce1cc8b77ed8e2ccd2e55b75e1118ab5c00ca337 Messaging Services recovered Data Services recovered https://status.intempt.com/ Fri, 06 Jun 2025 14:30:27 +0000 https://status.intempt.com/#5216290dcabc41fbb7703f8e18ea698c7fd49a4aaf1ecbb8591f84d23654e40f Data Services recovered Audience Services recovered https://status.intempt.com/ Fri, 06 Jun 2025 14:30:24 +0000 https://status.intempt.com/#2cd72a7b4dbbfbd3335d85ea759fb9e1251690c91a052bd1569c73ec879f2fda Audience Services recovered Messaging Services went down https://status.intempt.com/ Fri, 06 Jun 2025 14:18:05 +0000 https://status.intempt.com/#1387d5568007732e7b6c35a3ce1cc8b77ed8e2ccd2e55b75e1118ab5c00ca337 Messaging Services went down Audience Services went down https://status.intempt.com/ Fri, 06 Jun 2025 14:16:44 +0000 https://status.intempt.com/#2cd72a7b4dbbfbd3335d85ea759fb9e1251690c91a052bd1569c73ec879f2fda Audience Services went down Data Services went down https://status.intempt.com/ Fri, 06 Jun 2025 14:16:42 +0000 https://status.intempt.com/#5216290dcabc41fbb7703f8e18ea698c7fd49a4aaf1ecbb8591f84d23654e40f Data Services went down Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 14:00:03 -0000 https://status.intempt.com/incident/598218#fc16c6db817abaa5918abbadfbd2cec93239cfd8b2330f0b60cc3c7f30528702 We’re excited to introduce a powerful set of enhancements to our Journey system: Improved Journey Initialization Agent (Backend): Optimized for better performance and reliability in managing user journey processes. Redesigned Journey Canvas: A fresh, intuitive interface that makes visualizing and editing user journeys more seamless than ever. Expanded Journey Events: We've upgraded existing event tracking and added two key features — Clicked Email and Opened Email — enabling precise monitoring of user interactions with GMAIL links and email opens. Journey Transformer Deletion (Backend): You can now efficiently remove transformer sequences, giving you greater control and flexibility over journey logic. Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 14:00:03 -0000 https://status.intempt.com/incident/598218#fc16c6db817abaa5918abbadfbd2cec93239cfd8b2330f0b60cc3c7f30528702 We’re excited to introduce a powerful set of enhancements to our Journey system: Improved Journey Initialization Agent (Backend): Optimized for better performance and reliability in managing user journey processes. Redesigned Journey Canvas: A fresh, intuitive interface that makes visualizing and editing user journeys more seamless than ever. Expanded Journey Events: We've upgraded existing event tracking and added two key features — Clicked Email and Opened Email — enabling precise monitoring of user interactions with GMAIL links and email opens. Journey Transformer Deletion (Backend): You can now efficiently remove transformer sequences, giving you greater control and flexibility over journey logic. Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 14:00:03 -0000 https://status.intempt.com/incident/598218#fc16c6db817abaa5918abbadfbd2cec93239cfd8b2330f0b60cc3c7f30528702 We’re excited to introduce a powerful set of enhancements to our Journey system: Improved Journey Initialization Agent (Backend): Optimized for better performance and reliability in managing user journey processes. Redesigned Journey Canvas: A fresh, intuitive interface that makes visualizing and editing user journeys more seamless than ever. Expanded Journey Events: We've upgraded existing event tracking and added two key features — Clicked Email and Opened Email — enabling precise monitoring of user interactions with GMAIL links and email opens. Journey Transformer Deletion (Backend): You can now efficiently remove transformer sequences, giving you greater control and flexibility over journey logic. Journey update https://status.intempt.com/incident/598218 Fri, 06 Jun 2025 14:00:03 -0000 https://status.intempt.com/incident/598218#fc16c6db817abaa5918abbadfbd2cec93239cfd8b2330f0b60cc3c7f30528702 We’re excited to introduce a powerful set of enhancements to our Journey system: Improved Journey Initialization Agent (Backend): Optimized for better performance and reliability in managing user journey processes. Redesigned Journey Canvas: A fresh, intuitive interface that makes visualizing and editing user journeys more seamless than ever. Expanded Journey Events: We've upgraded existing event tracking and added two key features — Clicked Email and Opened Email — enabling precise monitoring of user interactions with GMAIL links and email opens. Journey Transformer Deletion (Backend): You can now efficiently remove transformer sequences, giving you greater control and flexibility over journey logic. Messaging Services recovered https://status.intempt.com/ Thu, 05 Jun 2025 16:44:34 +0000 https://status.intempt.com/#3d6363c7fe504e04ff3077f96d24bcac056c88ba7f958c467f22cc6691c946a6 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 05 Jun 2025 16:44:33 +0000 https://status.intempt.com/#b0b789bfb8425a4576166687c8ee5df4bd1d1c01fa056ba757a06404b5ceda2d Audience Services recovered Data Services recovered https://status.intempt.com/ Thu, 05 Jun 2025 16:44:33 +0000 https://status.intempt.com/#efd2ea8bbb66aa6110ec3ea005e3721369da71d0138b5a1e6204d78cff72ff13 Data Services recovered Messaging Services went down https://status.intempt.com/ Thu, 05 Jun 2025 16:33:38 +0000 https://status.intempt.com/#3d6363c7fe504e04ff3077f96d24bcac056c88ba7f958c467f22cc6691c946a6 Messaging Services went down Audience Services went down https://status.intempt.com/ Thu, 05 Jun 2025 16:33:37 +0000 https://status.intempt.com/#b0b789bfb8425a4576166687c8ee5df4bd1d1c01fa056ba757a06404b5ceda2d Audience Services went down Data Services went down https://status.intempt.com/ Thu, 05 Jun 2025 16:33:37 +0000 https://status.intempt.com/#efd2ea8bbb66aa6110ec3ea005e3721369da71d0138b5a1e6204d78cff72ff13 Data Services went down Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 11:10:35 +0000 https://status.intempt.com/incident/584093#6fdc8760c600adc8b93e1a89eca21c8bfce545870a162d0439bfc9717f74d5e2 Maintenance completed Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 11:10:35 +0000 https://status.intempt.com/incident/584093#6fdc8760c600adc8b93e1a89eca21c8bfce545870a162d0439bfc9717f74d5e2 Maintenance completed Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 11:10:35 +0000 https://status.intempt.com/incident/584093#6fdc8760c600adc8b93e1a89eca21c8bfce545870a162d0439bfc9717f74d5e2 Maintenance completed Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 11:10:35 +0000 https://status.intempt.com/incident/584093#6fdc8760c600adc8b93e1a89eca21c8bfce545870a162d0439bfc9717f74d5e2 Maintenance completed Data Services recovered https://status.intempt.com/ Fri, 30 May 2025 11:07:08 +0000 https://status.intempt.com/#67919892d4893b631ab2ac45f31a5bc0ca942954438dd96c22badaf156861697 Data Services recovered Audience Services recovered https://status.intempt.com/ Fri, 30 May 2025 11:07:06 +0000 https://status.intempt.com/#92d632101518195b0464c86f60be896c0ddf360e797189f6f08644f842158e85 Audience Services recovered Messaging Services recovered https://status.intempt.com/ Fri, 30 May 2025 11:04:37 +0000 https://status.intempt.com/#4bf5e952c89d660608f758622938b575c1892776110caa0083fece3164971e76 Messaging Services recovered Audience Services went down https://status.intempt.com/ Fri, 30 May 2025 10:55:33 +0000 https://status.intempt.com/#92d632101518195b0464c86f60be896c0ddf360e797189f6f08644f842158e85 Audience Services went down Data Services went down https://status.intempt.com/ Fri, 30 May 2025 10:55:33 +0000 https://status.intempt.com/#67919892d4893b631ab2ac45f31a5bc0ca942954438dd96c22badaf156861697 Data Services went down Messaging Services went down https://status.intempt.com/ Fri, 30 May 2025 10:46:44 +0000 https://status.intempt.com/#4bf5e952c89d660608f758622938b575c1892776110caa0083fece3164971e76 Messaging Services went down Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 10:43:35 -0000 https://status.intempt.com/incident/584093#679a31e1e58a709fac0831ad43c7630b7e6b3c9a5d53e6a7252f1d7e8165c6ac We will be deploying a new Research Transformer for Journeys and extending our backend message schemas to support additional fields. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 10:43:35 -0000 https://status.intempt.com/incident/584093#679a31e1e58a709fac0831ad43c7630b7e6b3c9a5d53e6a7252f1d7e8165c6ac We will be deploying a new Research Transformer for Journeys and extending our backend message schemas to support additional fields. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 10:43:35 -0000 https://status.intempt.com/incident/584093#679a31e1e58a709fac0831ad43c7630b7e6b3c9a5d53e6a7252f1d7e8165c6ac We will be deploying a new Research Transformer for Journeys and extending our backend message schemas to support additional fields. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Updating data flow https://status.intempt.com/incident/584093 Fri, 30 May 2025 10:43:35 -0000 https://status.intempt.com/incident/584093#679a31e1e58a709fac0831ad43c7630b7e6b3c9a5d53e6a7252f1d7e8165c6ac We will be deploying a new Research Transformer for Journeys and extending our backend message schemas to support additional fields. To apply these upgrades, all data-flow services must be redeployed. No data will be lost. Incoming items will be queued and delivered once the upgrade completes. Tasks update https://status.intempt.com/incident/580457 Mon, 26 May 2025 14:45:00 +0000 https://status.intempt.com/incident/580457#ba9c56dce3c14c83c1069af345efe3a2e181a39809115717bd34a2a77f3dcb84 Maintenance completed Messaging Services recovered https://status.intempt.com/ Mon, 26 May 2025 14:44:15 +0000 https://status.intempt.com/#119915ab46ced6c9965a7a92ada21e4b0dd2663083a31b48de5ac1916f323d38 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Mon, 26 May 2025 14:31:50 +0000 https://status.intempt.com/#119915ab46ced6c9965a7a92ada21e4b0dd2663083a31b48de5ac1916f323d38 Messaging Services went down Tasks update https://status.intempt.com/incident/580457 Mon, 26 May 2025 14:26:00 -0000 https://status.intempt.com/incident/580457#a0a079910d89f0a1123e14b68cea9f73b898d02e47b10d486e8a97a1696206dc The Journeys and Destinations services are being redeployed to apply updates and improvements. Temporary interruptions in functionality may occur during this process. We appreciate your understanding. Audience Services recovered https://status.intempt.com/ Wed, 21 May 2025 13:41:50 +0000 https://status.intempt.com/#779e78dfae00cbc8532fe16391254af44f6248bc7a8f330fce301262cdea9b96 Audience Services recovered Data Services recovered https://status.intempt.com/ Wed, 21 May 2025 13:41:50 +0000 https://status.intempt.com/#b6278460a5e7629cb02002e48d0f8e50d348157eeb90d917407cc4d2f554c365 Data Services recovered Destinations service redeployment https://status.intempt.com/incident/574251 Wed, 21 May 2025 13:40:00 +0000 https://status.intempt.com/incident/574251#ed59f2362a64c9605abf7d0fa9f705bccb78c0d717bcb2602e62cde9865275c9 Maintenance completed Messaging Services recovered https://status.intempt.com/ Wed, 21 May 2025 13:36:12 +0000 https://status.intempt.com/#25e55389c9086e521979d430b9415704d5e99fabc481437464574a6823545798 Messaging Services recovered Data Services went down https://status.intempt.com/ Wed, 21 May 2025 13:31:42 +0000 https://status.intempt.com/#b6278460a5e7629cb02002e48d0f8e50d348157eeb90d917407cc4d2f554c365 Data Services went down Audience Services went down https://status.intempt.com/ Wed, 21 May 2025 13:31:42 +0000 https://status.intempt.com/#779e78dfae00cbc8532fe16391254af44f6248bc7a8f330fce301262cdea9b96 Audience Services went down Messaging Services went down https://status.intempt.com/ Wed, 21 May 2025 13:30:35 +0000 https://status.intempt.com/#25e55389c9086e521979d430b9415704d5e99fabc481437464574a6823545798 Messaging Services went down Destinations service redeployment https://status.intempt.com/incident/574251 Wed, 21 May 2025 13:23:00 -0000 https://status.intempt.com/incident/574251#8f68d4aecb040986524dd81e418f89aca2f6e406ff3690b6c6f96e213b62c515 The Destinations service is being redeployed to apply updates and improvements. Temporary interruptions in functionality may occur during this process. We appreciate your understanding. Messaging Services recovered https://status.intempt.com/ Mon, 19 May 2025 14:38:02 +0000 https://status.intempt.com/#2869e3384d78db7595f136be9be4971e1ab9d421d8a5741e2c76586ba5e4af13 Messaging Services recovered Journeys Updates https://status.intempt.com/incident/571446 Mon, 19 May 2025 14:30:08 +0000 https://status.intempt.com/incident/571446#448056aebf333aba91c199e151c8a26ee3dfe82584ed2dbde6f75f9e309fce29 Maintenance completed Messaging Services went down https://status.intempt.com/ Mon, 19 May 2025 14:25:42 +0000 https://status.intempt.com/#2869e3384d78db7595f136be9be4971e1ab9d421d8a5741e2c76586ba5e4af13 Messaging Services went down Journeys Updates https://status.intempt.com/incident/571446 Mon, 19 May 2025 14:23:08 -0000 https://status.intempt.com/incident/571446#db62c79bfc84d443722564239112c50e639b0f07c86204b94dde4cd29f433821 The Journeys service is being redeployed to apply updates and improvements. Temporary interruptions in functionality may occur during this process. We appreciate your understanding. Messaging Services recovered https://status.intempt.com/ Mon, 19 May 2025 10:13:48 +0000 https://status.intempt.com/#907826d65b05fe95c5c804f09a1a023e0ad4909ecf9258e87ee134fc64a42a71 Messaging Services recovered Journeys Updates https://status.intempt.com/incident/571144 Mon, 19 May 2025 10:10:02 +0000 https://status.intempt.com/incident/571144#18a56ac613788fa4238d058c6b82fcf2598ee26135aa754e1c314ad23cc4a58c Maintenance completed Journeys Updates https://status.intempt.com/incident/571144 Mon, 19 May 2025 10:10:02 +0000 https://status.intempt.com/incident/571144#18a56ac613788fa4238d058c6b82fcf2598ee26135aa754e1c314ad23cc4a58c Maintenance completed Journeys Updates https://status.intempt.com/incident/571144 Mon, 19 May 2025 10:10:02 +0000 https://status.intempt.com/incident/571144#18a56ac613788fa4238d058c6b82fcf2598ee26135aa754e1c314ad23cc4a58c Maintenance completed Data Services recovered https://status.intempt.com/ Mon, 19 May 2025 09:58:04 +0000 https://status.intempt.com/#3a6940020d2e0e04abb1f2869ceca6525b8d217e97fe575779ec0a7b1981e945 Data Services recovered Audience Services recovered https://status.intempt.com/ Mon, 19 May 2025 09:58:04 +0000 https://status.intempt.com/#81c1a330993089465ee40a2e465160a6efeb39399ccda50c4b41f9c05743a5ca Audience Services recovered Audience Services went down https://status.intempt.com/ Mon, 19 May 2025 09:47:34 +0000 https://status.intempt.com/#81c1a330993089465ee40a2e465160a6efeb39399ccda50c4b41f9c05743a5ca Audience Services went down Messaging Services went down https://status.intempt.com/ Mon, 19 May 2025 09:47:34 +0000 https://status.intempt.com/#907826d65b05fe95c5c804f09a1a023e0ad4909ecf9258e87ee134fc64a42a71 Messaging Services went down Data Services went down https://status.intempt.com/ Mon, 19 May 2025 09:47:33 +0000 https://status.intempt.com/#3a6940020d2e0e04abb1f2869ceca6525b8d217e97fe575779ec0a7b1981e945 Data Services went down Journeys Updates https://status.intempt.com/incident/571144 Mon, 19 May 2025 09:40:02 -0000 https://status.intempt.com/incident/571144#c143b728541260d33ed9531a0fd73c7160efb49a21bf077e5bc1bd6b6da5e620 As part of scheduled updates, all services involved in the data processing flow will undergo upgrades. During this period, data collection, processing, and reporting may be temporarily affected. We are working to ensure minimal disruption and will restore full functionality as quickly as possible. Journeys Updates https://status.intempt.com/incident/571144 Mon, 19 May 2025 09:40:02 -0000 https://status.intempt.com/incident/571144#c143b728541260d33ed9531a0fd73c7160efb49a21bf077e5bc1bd6b6da5e620 As part of scheduled updates, all services involved in the data processing flow will undergo upgrades. During this period, data collection, processing, and reporting may be temporarily affected. We are working to ensure minimal disruption and will restore full functionality as quickly as possible. Journeys Updates https://status.intempt.com/incident/571144 Mon, 19 May 2025 09:40:02 -0000 https://status.intempt.com/incident/571144#c143b728541260d33ed9531a0fd73c7160efb49a21bf077e5bc1bd6b6da5e620 As part of scheduled updates, all services involved in the data processing flow will undergo upgrades. During this period, data collection, processing, and reporting may be temporarily affected. We are working to ensure minimal disruption and will restore full functionality as quickly as possible. Audience Services recovered https://status.intempt.com/ Fri, 16 May 2025 11:03:02 +0000 https://status.intempt.com/#bdc4b1439bc8586984744f8fc5f9adc0d1e4837020a36f0b4afa321fb9c81ee1 Audience Services recovered Messaging Services recovered https://status.intempt.com/ Fri, 16 May 2025 11:03:02 +0000 https://status.intempt.com/#5e94c0d267a0a1dbd9ed5b963ebb1c1c2e727661ff2a44b61f517fdad749fc22 Messaging Services recovered Data Services recovered https://status.intempt.com/ Fri, 16 May 2025 11:03:02 +0000 https://status.intempt.com/#64a51e450b586b4bf08bcffa5ce8dad093d613eb8787f23bf9f7693eeee5c19d Data Services recovered Audience Services went down https://status.intempt.com/ Fri, 16 May 2025 10:57:48 +0000 https://status.intempt.com/#bdc4b1439bc8586984744f8fc5f9adc0d1e4837020a36f0b4afa321fb9c81ee1 Audience Services went down Data Services went down https://status.intempt.com/ Fri, 16 May 2025 10:57:33 +0000 https://status.intempt.com/#64a51e450b586b4bf08bcffa5ce8dad093d613eb8787f23bf9f7693eeee5c19d Data Services went down Messaging Services went down https://status.intempt.com/ Fri, 16 May 2025 10:57:32 +0000 https://status.intempt.com/#5e94c0d267a0a1dbd9ed5b963ebb1c1c2e727661ff2a44b61f517fdad749fc22 Messaging Services went down Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 15:00:00 +0000 https://status.intempt.com/incident/564363#31ae0d73814df9bd87937cbfa59e24791848616b37b070f56375a4178770cac9 Maintenance completed Analytics Services recovered https://status.intempt.com/ Wed, 14 May 2025 14:07:48 +0000 https://status.intempt.com/#11d9e414322eee64523a1065f38747ba40ba7e2232873c9922062c2a8cb52701 Analytics Services recovered Analytics Services went down https://status.intempt.com/ Wed, 14 May 2025 14:01:48 +0000 https://status.intempt.com/#11d9e414322eee64523a1065f38747ba40ba7e2232873c9922062c2a8cb52701 Analytics Services went down Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Brand Attribute Deployment https://status.intempt.com/incident/564363 Wed, 14 May 2025 14:00:07 -0000 https://status.intempt.com/incident/564363#270de996d244dcba42b86921f9e5024e69fca06a36def9fb1ccfb8b2abaf935b We are currently deploying the Brand attribute project. This may cause downtime in some of our services. Analytics Services recovered https://status.intempt.com/ Tue, 13 May 2025 14:21:38 +0000 https://status.intempt.com/#c5fdd599190ad18c844eb5de1f70ea55c7a51e857ff56e42fb8f7b2cf4764ea0 Analytics Services recovered Analytics Services went down https://status.intempt.com/ Tue, 13 May 2025 14:09:29 +0000 https://status.intempt.com/#c5fdd599190ad18c844eb5de1f70ea55c7a51e857ff56e42fb8f7b2cf4764ea0 Analytics Services went down Analytics Services recovered https://status.intempt.com/ Mon, 12 May 2025 15:54:10 +0000 https://status.intempt.com/#d561bc17badc973b65c1fda6ff824958608310ba1995a5e090b760e7b5a9db70 Analytics Services recovered Analytics update https://status.intempt.com/incident/560836 Mon, 12 May 2025 15:48:04 +0000 https://status.intempt.com/incident/560836#a59a32b8d10bf1fa5a00097123d66b47fa226de58261d7917acfce91e50d89c2 Maintenance completed Analytics update https://status.intempt.com/incident/560836 Mon, 12 May 2025 15:48:04 +0000 https://status.intempt.com/incident/560836#a59a32b8d10bf1fa5a00097123d66b47fa226de58261d7917acfce91e50d89c2 Maintenance completed Analytics Services went down https://status.intempt.com/ Mon, 12 May 2025 15:45:10 +0000 https://status.intempt.com/#d561bc17badc973b65c1fda6ff824958608310ba1995a5e090b760e7b5a9db70 Analytics Services went down Analytics update https://status.intempt.com/incident/560836 Mon, 12 May 2025 15:38:04 -0000 https://status.intempt.com/incident/560836#dcd305689b4566348306fb5b694e258430ed6cf289ada7f525f83be1012bc04d Analytics update in progress. Recent changes to the analytics payload or UI may temporarily affect reporting accuracy while older data formats are being updated. Analytics update https://status.intempt.com/incident/560836 Mon, 12 May 2025 15:38:04 -0000 https://status.intempt.com/incident/560836#dcd305689b4566348306fb5b694e258430ed6cf289ada7f525f83be1012bc04d Analytics update in progress. Recent changes to the analytics payload or UI may temporarily affect reporting accuracy while older data formats are being updated. Messaging Services recovered https://status.intempt.com/ Mon, 12 May 2025 15:18:28 +0000 https://status.intempt.com/#e776bdbb634857ceac0b5673359b361cc5cea08f2949a04ad53183baaafe8ac5 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Mon, 12 May 2025 15:01:58 +0000 https://status.intempt.com/#e776bdbb634857ceac0b5673359b361cc5cea08f2949a04ad53183baaafe8ac5 Messaging Services went down Messaging Services recovered https://status.intempt.com/ Mon, 12 May 2025 14:44:38 +0000 https://status.intempt.com/#c95c2de60b45c8e32bbf22b63de2d55142d2b8fe27cadc0d978072ffd1170238 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Mon, 12 May 2025 14:08:57 +0000 https://status.intempt.com/#c95c2de60b45c8e32bbf22b63de2d55142d2b8fe27cadc0d978072ffd1170238 Messaging Services went down Messaging Services recovered https://status.intempt.com/ Mon, 12 May 2025 11:50:34 +0000 https://status.intempt.com/#7c21aa85210ba1ba3df610035095bed2674358ef2d52258f12a4888613f97201 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Mon, 12 May 2025 11:50:13 +0000 https://status.intempt.com/#617c5a121164e6a5bb6cb397e9a363595014fb6f072d624cae6c387b868e27fd Audience Services recovered Data Services recovered https://status.intempt.com/ Mon, 12 May 2025 11:50:13 +0000 https://status.intempt.com/#635171c4e8250651ebfe5429e309273ab1fb15fd858130a23c78315fb3fde277 Data Services recovered Audience Services went down https://status.intempt.com/ Mon, 12 May 2025 11:38:35 +0000 https://status.intempt.com/#617c5a121164e6a5bb6cb397e9a363595014fb6f072d624cae6c387b868e27fd Audience Services went down Messaging Services went down https://status.intempt.com/ Mon, 12 May 2025 11:38:34 +0000 https://status.intempt.com/#7c21aa85210ba1ba3df610035095bed2674358ef2d52258f12a4888613f97201 Messaging Services went down Data Services went down https://status.intempt.com/ Mon, 12 May 2025 11:38:34 +0000 https://status.intempt.com/#635171c4e8250651ebfe5429e309273ab1fb15fd858130a23c78315fb3fde277 Data Services went down Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 11:24:00 +0000 https://status.intempt.com/incident/560591#1c0f43cd9f52f171e1197967550608363ee8ef7805e860c8dc3945ae2553a9c0 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 11:24:00 +0000 https://status.intempt.com/incident/560591#1c0f43cd9f52f171e1197967550608363ee8ef7805e860c8dc3945ae2553a9c0 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 11:24:00 +0000 https://status.intempt.com/incident/560591#1c0f43cd9f52f171e1197967550608363ee8ef7805e860c8dc3945ae2553a9c0 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 11:24:00 +0000 https://status.intempt.com/incident/560591#1c0f43cd9f52f171e1197967550608363ee8ef7805e860c8dc3945ae2553a9c0 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 11:24:00 +0000 https://status.intempt.com/incident/560591#1c0f43cd9f52f171e1197967550608363ee8ef7805e860c8dc3945ae2553a9c0 Maintenance completed Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 10:24:30 -0000 https://status.intempt.com/incident/560591#50de345c582ad9b424cafb460da88c28cd0b49015fb4432e84d9422138fa3a2a The customer data platform will be updated with bug fixes. Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 10:24:30 -0000 https://status.intempt.com/incident/560591#50de345c582ad9b424cafb460da88c28cd0b49015fb4432e84d9422138fa3a2a The customer data platform will be updated with bug fixes. Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 10:24:30 -0000 https://status.intempt.com/incident/560591#50de345c582ad9b424cafb460da88c28cd0b49015fb4432e84d9422138fa3a2a The customer data platform will be updated with bug fixes. Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 10:24:30 -0000 https://status.intempt.com/incident/560591#50de345c582ad9b424cafb460da88c28cd0b49015fb4432e84d9422138fa3a2a The customer data platform will be updated with bug fixes. Customer Data Platform update https://status.intempt.com/incident/560591 Mon, 12 May 2025 10:24:30 -0000 https://status.intempt.com/incident/560591#50de345c582ad9b424cafb460da88c28cd0b49015fb4432e84d9422138fa3a2a The customer data platform will be updated with bug fixes. Messaging Services recovered https://status.intempt.com/ Sun, 11 May 2025 19:27:21 +0000 https://status.intempt.com/#711de03f0fca9bccb371ed703ea7b2ea85d197be5f65cfce2a91fbf51c482150 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Sun, 11 May 2025 19:18:52 +0000 https://status.intempt.com/#711de03f0fca9bccb371ed703ea7b2ea85d197be5f65cfce2a91fbf51c482150 Messaging Services went down Messaging Services recovered https://status.intempt.com/ Sun, 11 May 2025 19:05:09 +0000 https://status.intempt.com/#88438298197508078799cbce239715a5dc3bfe56bde4aafae98d2fc8c633d5a4 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Sun, 11 May 2025 18:52:43 +0000 https://status.intempt.com/#88438298197508078799cbce239715a5dc3bfe56bde4aafae98d2fc8c633d5a4 Messaging Services went down Messaging Services recovered https://status.intempt.com/ Sat, 10 May 2025 19:14:58 +0000 https://status.intempt.com/#a0adba37fe7479c3c21c61de58040aab33c3b6eab5cd49da01d8a5e9da3a414f Messaging Services recovered Messaging Services went down https://status.intempt.com/ Sat, 10 May 2025 19:09:27 +0000 https://status.intempt.com/#a0adba37fe7479c3c21c61de58040aab33c3b6eab5cd49da01d8a5e9da3a414f Messaging Services went down Messaging Services recovered https://status.intempt.com/ Sat, 10 May 2025 19:03:37 +0000 https://status.intempt.com/#abbf5bd5e5b7f9a462d1ed1128842dd035f1ee074fc8c36e3d5398111f28549d Messaging Services recovered Messaging Services went down https://status.intempt.com/ Sat, 10 May 2025 18:51:37 +0000 https://status.intempt.com/#abbf5bd5e5b7f9a462d1ed1128842dd035f1ee074fc8c36e3d5398111f28549d Messaging Services went down Experience Services recovered https://status.intempt.com/ Fri, 09 May 2025 16:45:42 +0000 https://status.intempt.com/#9ec3567c910530366761ba95bbe97320785037524ad0f05d46c15eb9fcc5d368 Experience Services recovered Delivering new Experiences https://status.intempt.com/incident/559336 Fri, 09 May 2025 16:40:15 +0000 https://status.intempt.com/incident/559336#e7ff9018fad01ab45d0e925da0d0738e2b42fefe154bcc9f31d3780d1f9ecbe9 Maintenance completed Delivering new Experiences https://status.intempt.com/incident/559336 Fri, 09 May 2025 16:40:15 +0000 https://status.intempt.com/incident/559336#e7ff9018fad01ab45d0e925da0d0738e2b42fefe154bcc9f31d3780d1f9ecbe9 Maintenance completed Experience Services went down https://status.intempt.com/ Fri, 09 May 2025 16:39:42 +0000 https://status.intempt.com/#9ec3567c910530366761ba95bbe97320785037524ad0f05d46c15eb9fcc5d368 Experience Services went down Delivering new Experiences https://status.intempt.com/incident/559336 Fri, 09 May 2025 16:18:15 -0000 https://status.intempt.com/incident/559336#1d2f7cc86b2383484dce9449eea89634af03f09fa6f8fd4400660794a16a9075 Delivering new experiences. Due to structural changes, some services may take a little time to start and function properly. Delivering new Experiences https://status.intempt.com/incident/559336 Fri, 09 May 2025 16:18:15 -0000 https://status.intempt.com/incident/559336#1d2f7cc86b2383484dce9449eea89634af03f09fa6f8fd4400660794a16a9075 Delivering new experiences. Due to structural changes, some services may take a little time to start and function properly. Audience Services recovered https://status.intempt.com/ Wed, 07 May 2025 17:51:30 +0000 https://status.intempt.com/#3fcc9adc325aa7c4ddafc01d3a3cfc51f6f5b92665afb448f49e3683abd7cc02 Audience Services recovered Data Services recovered https://status.intempt.com/ Wed, 07 May 2025 17:51:11 +0000 https://status.intempt.com/#01c6704de76b80b15fb4cef6ac0eeaf3d3a14d88a0fddbd2b085aa996acad910 Data Services recovered Data Services went down https://status.intempt.com/ Wed, 07 May 2025 17:43:44 +0000 https://status.intempt.com/#01c6704de76b80b15fb4cef6ac0eeaf3d3a14d88a0fddbd2b085aa996acad910 Data Services went down Audience Services went down https://status.intempt.com/ Wed, 07 May 2025 17:43:44 +0000 https://status.intempt.com/#3fcc9adc325aa7c4ddafc01d3a3cfc51f6f5b92665afb448f49e3683abd7cc02 Audience Services went down Messaging Services recovered https://status.intempt.com/ Tue, 06 May 2025 12:43:51 +0000 https://status.intempt.com/#055d7d79c3d890b304481c021b1b541f70e996b20c681d460d4d0c6dcb3dfbe4 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Tue, 06 May 2025 12:29:42 +0000 https://status.intempt.com/#055d7d79c3d890b304481c021b1b541f70e996b20c681d460d4d0c6dcb3dfbe4 Messaging Services went down Snippet deployment https://status.intempt.com/incident/557411 Tue, 06 May 2025 12:15:00 +0000 https://status.intempt.com/incident/557411#40e5cf603771cdcf734bb5bb77b1f56e410cb9b8b4308e3a0dcfa36a7b3b6c28 Maintenance completed Snippet deployment https://status.intempt.com/incident/557411 Tue, 06 May 2025 11:15:00 -0000 https://status.intempt.com/incident/557411#012797c8c744ae7969f4e6d3737ab2c0d5b9876419e33babe456397a5cd7b07e 🚧 Maintenance Notice: We're currently performing a Snippet deployment. Some features may be temporarily unavailable. Thank you for your patience. Data/Messaging Services restarts https://status.intempt.com/incident/557260 Tue, 06 May 2025 08:00:00 +0000 https://status.intempt.com/incident/557260#2272c0ad267ce8d120ec69cb7573b8c98f73be15d1b24bfcfc443837d3dab04e Maintenance completed Data/Messaging Services restarts https://status.intempt.com/incident/557260 Tue, 06 May 2025 08:00:00 +0000 https://status.intempt.com/incident/557260#2272c0ad267ce8d120ec69cb7573b8c98f73be15d1b24bfcfc443837d3dab04e Maintenance completed Messaging Services recovered https://status.intempt.com/ Tue, 06 May 2025 07:58:12 +0000 https://status.intempt.com/#8785fd467491b3862074a80f92a613c7c5b66c94246e9f4f70259b73d6c000a1 Messaging Services recovered Data Services recovered https://status.intempt.com/ Tue, 06 May 2025 07:57:45 +0000 https://status.intempt.com/#a6183fa74a2af29c1cb43ec098d725db06835159768b8e38b08b70427f1117bb Data Services recovered Audience Services recovered https://status.intempt.com/ Tue, 06 May 2025 07:57:43 +0000 https://status.intempt.com/#3c9ca6cb9a1c68f78c5469188732115d1fbbbdc0224ca73a77af7968fcebfa0b Audience Services recovered Data Services went down https://status.intempt.com/ Tue, 06 May 2025 07:46:44 +0000 https://status.intempt.com/#a6183fa74a2af29c1cb43ec098d725db06835159768b8e38b08b70427f1117bb Data Services went down Messaging Services went down https://status.intempt.com/ Tue, 06 May 2025 07:46:44 +0000 https://status.intempt.com/#8785fd467491b3862074a80f92a613c7c5b66c94246e9f4f70259b73d6c000a1 Messaging Services went down Audience Services went down https://status.intempt.com/ Tue, 06 May 2025 07:46:43 +0000 https://status.intempt.com/#3c9ca6cb9a1c68f78c5469188732115d1fbbbdc0224ca73a77af7968fcebfa0b Audience Services went down Data/Messaging Services restarts https://status.intempt.com/incident/557260 Tue, 06 May 2025 07:40:00 -0000 https://status.intempt.com/incident/557260#655800bcb091e3d049bfb83333d9295bed721875e2ecb647e7b1785659912741 Releasing Accounts deletion Data/Messaging Services restarts https://status.intempt.com/incident/557260 Tue, 06 May 2025 07:40:00 -0000 https://status.intempt.com/incident/557260#655800bcb091e3d049bfb83333d9295bed721875e2ecb647e7b1785659912741 Releasing Accounts deletion Experience Services recovered https://status.intempt.com/ Fri, 02 May 2025 15:37:17 +0000 https://status.intempt.com/#a3f009e707b3361ff1febaedecb8902c941b8736280ffff6ec88f41f9b66edb2 Experience Services recovered Experience Services went down https://status.intempt.com/ Fri, 02 May 2025 15:28:15 +0000 https://status.intempt.com/#a3f009e707b3361ff1febaedecb8902c941b8736280ffff6ec88f41f9b66edb2 Experience Services went down Experience Services recovered https://status.intempt.com/ Thu, 01 May 2025 12:38:18 +0000 https://status.intempt.com/#7ffa080052dfb6fed3f7f8a3dcce7fa2f30a94f1ef03cbcffe6ce4ee0c23dfa8 Experience Services recovered Experience Services went down https://status.intempt.com/ Thu, 01 May 2025 12:29:55 +0000 https://status.intempt.com/#7ffa080052dfb6fed3f7f8a3dcce7fa2f30a94f1ef03cbcffe6ce4ee0c23dfa8 Experience Services went down Messaging Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 16:36:17 +0000 https://status.intempt.com/#213e3a3ae755cfd1dfda4af68b90d2aa783b44640ee7a87ea3a52e882718db9d Messaging Services recovered Audience Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 16:36:15 +0000 https://status.intempt.com/#241a5bc31aebe88f32041fa6c1a77d3eb3c0f4a261983c65d18ebdfdfd55613a Audience Services recovered Data Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 16:36:14 +0000 https://status.intempt.com/#15c28da9990ec97c618a5a8ae490e676a05ed5e14a780472e2bee6438ff4536a Data Services recovered Experience Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 16:32:15 +0000 https://status.intempt.com/#e3c56f3522c365d75ed09736b98743275ea828056265aee937738cb79efa231e Experience Services recovered Messaging Services went down https://status.intempt.com/ Fri, 25 Apr 2025 16:30:38 +0000 https://status.intempt.com/#213e3a3ae755cfd1dfda4af68b90d2aa783b44640ee7a87ea3a52e882718db9d Messaging Services went down Audience Services went down https://status.intempt.com/ Fri, 25 Apr 2025 16:30:38 +0000 https://status.intempt.com/#241a5bc31aebe88f32041fa6c1a77d3eb3c0f4a261983c65d18ebdfdfd55613a Audience Services went down Data Services went down https://status.intempt.com/ Fri, 25 Apr 2025 16:30:37 +0000 https://status.intempt.com/#15c28da9990ec97c618a5a8ae490e676a05ed5e14a780472e2bee6438ff4536a Data Services went down Experience Services went down https://status.intempt.com/ Fri, 25 Apr 2025 16:26:19 +0000 https://status.intempt.com/#e3c56f3522c365d75ed09736b98743275ea828056265aee937738cb79efa231e Experience Services went down Messaging Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 14:01:57 +0000 https://status.intempt.com/#37317dc88726118988742b5438818ef402c277670fc1e2dc2ffca8be41fe15be Messaging Services recovered Audience Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 14:01:56 +0000 https://status.intempt.com/#27e4600d99c9dbadcae6a9c0400522c82eb167f091e8e0d889a74ed42533ed65 Audience Services recovered Data Services recovered https://status.intempt.com/ Fri, 25 Apr 2025 14:01:56 +0000 https://status.intempt.com/#9d2e3a84b48ec98d27c573146465e3159e92acafc28f277d855dfa12450069a7 Data Services recovered Audience Services went down https://status.intempt.com/ Fri, 25 Apr 2025 13:48:40 +0000 https://status.intempt.com/#27e4600d99c9dbadcae6a9c0400522c82eb167f091e8e0d889a74ed42533ed65 Audience Services went down Data Services went down https://status.intempt.com/ Fri, 25 Apr 2025 13:48:40 +0000 https://status.intempt.com/#9d2e3a84b48ec98d27c573146465e3159e92acafc28f277d855dfa12450069a7 Data Services went down Messaging Services went down https://status.intempt.com/ Fri, 25 Apr 2025 13:48:39 +0000 https://status.intempt.com/#37317dc88726118988742b5438818ef402c277670fc1e2dc2ffca8be41fe15be Messaging Services went down Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 13:10:00 +0000 https://status.intempt.com/incident/551760#91e3d6ba206c5613b72ac437b79af98eb536a0fc9bc8b625261956f27845202b Maintenance completed Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 13:10:00 +0000 https://status.intempt.com/incident/551760#91e3d6ba206c5613b72ac437b79af98eb536a0fc9bc8b625261956f27845202b Maintenance completed Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 13:10:00 +0000 https://status.intempt.com/incident/551760#91e3d6ba206c5613b72ac437b79af98eb536a0fc9bc8b625261956f27845202b Maintenance completed Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 13:10:00 +0000 https://status.intempt.com/incident/551760#91e3d6ba206c5613b72ac437b79af98eb536a0fc9bc8b625261956f27845202b Maintenance completed Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 12:45:00 -0000 https://status.intempt.com/incident/551760#de7dd18dbc71819665c6e206d3c9507b192140c653f8236ecb50d31cd2c5fabe We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 12:45:00 -0000 https://status.intempt.com/incident/551760#de7dd18dbc71819665c6e206d3c9507b192140c653f8236ecb50d31cd2c5fabe We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 12:45:00 -0000 https://status.intempt.com/incident/551760#de7dd18dbc71819665c6e206d3c9507b192140c653f8236ecb50d31cd2c5fabe We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 25 https://status.intempt.com/incident/551760 Fri, 25 Apr 2025 12:45:00 -0000 https://status.intempt.com/incident/551760#de7dd18dbc71819665c6e206d3c9507b192140c653f8236ecb50d31cd2c5fabe We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:25:00 +0000 https://status.intempt.com/incident/551759#1ea3336003f9dd25ecc22b636e21e956cd7ece620c036c677be1db6c39813d49 Maintenance completed Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:25:00 +0000 https://status.intempt.com/incident/551759#1ea3336003f9dd25ecc22b636e21e956cd7ece620c036c677be1db6c39813d49 Maintenance completed Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:25:00 +0000 https://status.intempt.com/incident/551759#1ea3336003f9dd25ecc22b636e21e956cd7ece620c036c677be1db6c39813d49 Maintenance completed Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:25:00 +0000 https://status.intempt.com/incident/551759#1ea3336003f9dd25ecc22b636e21e956cd7ece620c036c677be1db6c39813d49 Maintenance completed Messaging Services recovered https://status.intempt.com/ Tue, 22 Apr 2025 10:24:46 +0000 https://status.intempt.com/#d22ac6daca2fec883810c7d449d635cf88ec7a3573a0149c99e815341e68b37b Messaging Services recovered Data Services recovered https://status.intempt.com/ Tue, 22 Apr 2025 10:24:46 +0000 https://status.intempt.com/#664519e815eb5398c1354a98757ca6e72ab0eed23125e5f23e644b15e962ef29 Data Services recovered Audience Services recovered https://status.intempt.com/ Tue, 22 Apr 2025 10:24:43 +0000 https://status.intempt.com/#e9b660e760629a4f0f53ee54d8dd6bedd11880e065d4b92c1d14808f902e1e97 Audience Services recovered Data Services went down https://status.intempt.com/ Tue, 22 Apr 2025 10:14:55 +0000 https://status.intempt.com/#664519e815eb5398c1354a98757ca6e72ab0eed23125e5f23e644b15e962ef29 Data Services went down Audience Services went down https://status.intempt.com/ Tue, 22 Apr 2025 10:14:55 +0000 https://status.intempt.com/#e9b660e760629a4f0f53ee54d8dd6bedd11880e065d4b92c1d14808f902e1e97 Audience Services went down Messaging Services went down https://status.intempt.com/ Tue, 22 Apr 2025 10:14:55 +0000 https://status.intempt.com/#d22ac6daca2fec883810c7d449d635cf88ec7a3573a0149c99e815341e68b37b Messaging Services went down Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:14:00 -0000 https://status.intempt.com/incident/551759#832141669bbc1d23f7197ae0d9cbd5071cb724f64ddb1831e66ef53d7d37036d We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:14:00 -0000 https://status.intempt.com/incident/551759#832141669bbc1d23f7197ae0d9cbd5071cb724f64ddb1831e66ef53d7d37036d We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:14:00 -0000 https://status.intempt.com/incident/551759#832141669bbc1d23f7197ae0d9cbd5071cb724f64ddb1831e66ef53d7d37036d We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Customer Data Platform update - April 22 https://status.intempt.com/incident/551759 Tue, 22 Apr 2025 10:14:00 -0000 https://status.intempt.com/incident/551759#832141669bbc1d23f7197ae0d9cbd5071cb724f64ddb1831e66ef53d7d37036d We’re currently updating the Customer Data Platform to improve performance and stability. Some features may be temporarily unavailable during this maintenance—thanks for your patience! Experience Services recovered https://status.intempt.com/ Fri, 18 Apr 2025 15:29:26 +0000 https://status.intempt.com/#4a0a8e9987560a076993b77b27f46ecd739b10b1a0734aaad0a88735d018d899 Experience Services recovered Experience Services went down https://status.intempt.com/ Fri, 18 Apr 2025 15:23:26 +0000 https://status.intempt.com/#4a0a8e9987560a076993b77b27f46ecd739b10b1a0734aaad0a88735d018d899 Experience Services went down Messaging Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 09:20:28 +0000 https://status.intempt.com/#e1f067bc71bf8207b5ef566d2fc060161d6507154428d3dc698b98dd62993744 Messaging Services recovered Audience Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 09:20:26 +0000 https://status.intempt.com/#44820e048720bf739babec910d41a874236ae6be76fe5036b115dfa98efbdcb5 Audience Services recovered Data Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 09:20:26 +0000 https://status.intempt.com/#43457aeb22db409f787f6145164a83f41b085ebd3c97c2e269fbed6a2ee57e55 Data Services recovered Audience Services went down https://status.intempt.com/ Thu, 17 Apr 2025 09:04:37 +0000 https://status.intempt.com/#44820e048720bf739babec910d41a874236ae6be76fe5036b115dfa98efbdcb5 Audience Services went down Data Services went down https://status.intempt.com/ Thu, 17 Apr 2025 09:04:37 +0000 https://status.intempt.com/#43457aeb22db409f787f6145164a83f41b085ebd3c97c2e269fbed6a2ee57e55 Data Services went down Messaging Services went down https://status.intempt.com/ Thu, 17 Apr 2025 09:04:37 +0000 https://status.intempt.com/#e1f067bc71bf8207b5ef566d2fc060161d6507154428d3dc698b98dd62993744 Messaging Services went down Production AWS node restart https://status.intempt.com/incident/546695 Thu, 17 Apr 2025 06:24:00 -0000 https://status.intempt.com/incident/546695#f50d4028f2b05891824c965c05c0889cd99c1621c7050e91ab38fa9f276e3e7c On April 17, 2025, from 9:05 AM to 9:25 AM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546695 Thu, 17 Apr 2025 06:24:00 -0000 https://status.intempt.com/incident/546695#f50d4028f2b05891824c965c05c0889cd99c1621c7050e91ab38fa9f276e3e7c On April 17, 2025, from 9:05 AM to 9:25 AM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546695 Thu, 17 Apr 2025 06:24:00 -0000 https://status.intempt.com/incident/546695#f50d4028f2b05891824c965c05c0889cd99c1621c7050e91ab38fa9f276e3e7c On April 17, 2025, from 9:05 AM to 9:25 AM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546695 Thu, 17 Apr 2025 06:24:00 -0000 https://status.intempt.com/incident/546695#f50d4028f2b05891824c965c05c0889cd99c1621c7050e91ab38fa9f276e3e7c On April 17, 2025, from 9:05 AM to 9:25 AM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546695 Thu, 17 Apr 2025 06:24:00 -0000 https://status.intempt.com/incident/546695#f50d4028f2b05891824c965c05c0889cd99c1621c7050e91ab38fa9f276e3e7c On April 17, 2025, from 9:05 AM to 9:25 AM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546695 Thu, 17 Apr 2025 06:24:00 -0000 https://status.intempt.com/incident/546695#f50d4028f2b05891824c965c05c0889cd99c1621c7050e91ab38fa9f276e3e7c On April 17, 2025, from 9:05 AM to 9:25 AM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; The infrastructure recovery status was monitored until complete stabilization. Messaging Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 06:18:02 +0000 https://status.intempt.com/#f08589883e4be52c0471214e1d030c62ec9696ca50a276b4f14a51c8c72c7fd0 Messaging Services recovered Data Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 06:15:11 +0000 https://status.intempt.com/#ebb6ac6db58d91b31b5e29e6468efdfc0470fb8eb580af1bfdd0a6cfe5d65092 Data Services recovered Audience Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 06:14:57 +0000 https://status.intempt.com/#59fec2ae8016e6bef5369e667af44fee41f91974180a62fe74d49cff116b32c4 Audience Services recovered Analytics Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 06:14:29 +0000 https://status.intempt.com/#b9a62e8f6fec23ea9cd5fe6f3b1f860f6297ff55bf13b4a724615e6b5bca27c5 Analytics Services recovered Experience Services recovered https://status.intempt.com/ Thu, 17 Apr 2025 06:13:28 +0000 https://status.intempt.com/#8f42334b396d22e435614c39c00348b53779b31a814cef4c8d437998d1b8532e Experience Services recovered Data Services went down https://status.intempt.com/ Thu, 17 Apr 2025 06:06:38 +0000 https://status.intempt.com/#ebb6ac6db58d91b31b5e29e6468efdfc0470fb8eb580af1bfdd0a6cfe5d65092 Data Services went down Audience Services went down https://status.intempt.com/ Thu, 17 Apr 2025 06:06:37 +0000 https://status.intempt.com/#59fec2ae8016e6bef5369e667af44fee41f91974180a62fe74d49cff116b32c4 Audience Services went down Messaging Services went down https://status.intempt.com/ Thu, 17 Apr 2025 06:06:37 +0000 https://status.intempt.com/#f08589883e4be52c0471214e1d030c62ec9696ca50a276b4f14a51c8c72c7fd0 Messaging Services went down Experience Services went down https://status.intempt.com/ Thu, 17 Apr 2025 06:05:26 +0000 https://status.intempt.com/#8f42334b396d22e435614c39c00348b53779b31a814cef4c8d437998d1b8532e Experience Services went down Analytics Services went down https://status.intempt.com/ Thu, 17 Apr 2025 06:03:29 +0000 https://status.intempt.com/#b9a62e8f6fec23ea9cd5fe6f3b1f860f6297ff55bf13b4a724615e6b5bca27c5 Analytics Services went down Analytics Services recovered https://status.intempt.com/ Tue, 15 Apr 2025 16:29:36 +0000 https://status.intempt.com/#bfb37922d70cddcb272da911d8fbbd21d3d79f48eebcce32ba76bae79c96a084 Analytics Services recovered Analytics Services went down https://status.intempt.com/ Tue, 15 Apr 2025 16:21:05 +0000 https://status.intempt.com/#bfb37922d70cddcb272da911d8fbbd21d3d79f48eebcce32ba76bae79c96a084 Analytics Services went down Analytics Services recovered https://status.intempt.com/ Tue, 15 Apr 2025 14:32:31 +0000 https://status.intempt.com/#e6db5ad52e9ff00d3b2b08d7cfd50fc45c262c95330f3fe5fbf6a31a6d6b2ba8 Analytics Services recovered Analytics Services went down https://status.intempt.com/ Tue, 15 Apr 2025 14:26:44 +0000 https://status.intempt.com/#e6db5ad52e9ff00d3b2b08d7cfd50fc45c262c95330f3fe5fbf6a31a6d6b2ba8 Analytics Services went down Production AWS node restart https://status.intempt.com/incident/546694 Mon, 14 Apr 2025 11:20:00 -0000 https://status.intempt.com/incident/546694#1696d3222a1da93ded2212ed3af29d9d187773f394344a5ee06a6d3f1f4711f5 On April 14, 2025, from 1:20 PM to 2:15 PM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; A ticket was created regarding the node failure; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546694 Mon, 14 Apr 2025 11:20:00 -0000 https://status.intempt.com/incident/546694#1696d3222a1da93ded2212ed3af29d9d187773f394344a5ee06a6d3f1f4711f5 On April 14, 2025, from 1:20 PM to 2:15 PM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; A ticket was created regarding the node failure; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546694 Mon, 14 Apr 2025 11:20:00 -0000 https://status.intempt.com/incident/546694#1696d3222a1da93ded2212ed3af29d9d187773f394344a5ee06a6d3f1f4711f5 On April 14, 2025, from 1:20 PM to 2:15 PM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; A ticket was created regarding the node failure; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546694 Mon, 14 Apr 2025 11:20:00 -0000 https://status.intempt.com/incident/546694#1696d3222a1da93ded2212ed3af29d9d187773f394344a5ee06a6d3f1f4711f5 On April 14, 2025, from 1:20 PM to 2:15 PM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; A ticket was created regarding the node failure; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546694 Mon, 14 Apr 2025 11:20:00 -0000 https://status.intempt.com/incident/546694#1696d3222a1da93ded2212ed3af29d9d187773f394344a5ee06a6d3f1f4711f5 On April 14, 2025, from 1:20 PM to 2:15 PM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; A ticket was created regarding the node failure; The infrastructure recovery status was monitored until complete stabilization. Production AWS node restart https://status.intempt.com/incident/546694 Mon, 14 Apr 2025 11:20:00 -0000 https://status.intempt.com/incident/546694#1696d3222a1da93ded2212ed3af29d9d187773f394344a5ee06a6d3f1f4711f5 On April 14, 2025, from 1:20 PM to 2:15 PM (UTC+3), the production environment was unavailable for approximately one hour due to an unplanned restart of one of the AWS nodes. Immediately after discovering the problem, the on-call engineer promptly contacted the solution architect and informed him of the situation. At that time, there was no way to speed up the recovery, since the node raising process was entirely on the AWS side. It was decided to monitor the process and wait for the infrastructure to be restored. A ticket was also created to analyze the reasons for the restart and prevent similar cases in the future. Actions taken: The incident was recorded and documented; Contact with the architect was established immediately after the incident; A ticket was created regarding the node failure; The infrastructure recovery status was monitored until complete stabilization. Messaging Services recovered https://status.intempt.com/ Mon, 14 Apr 2025 11:14:12 +0000 https://status.intempt.com/#731c995f95905811dd6cf170e372774b29e8ef551cddb17ef7f153fda57dbebb Messaging Services recovered Data Services recovered https://status.intempt.com/ Mon, 14 Apr 2025 11:13:32 +0000 https://status.intempt.com/#d2a69899ccbebb309dee4eea91ec021e548ba401557cdfa7ea16c47f961b83b2 Data Services recovered Experience Services recovered https://status.intempt.com/ Mon, 14 Apr 2025 11:11:23 +0000 https://status.intempt.com/#843567305b4751dd086bb5dd85477a21c8060b97b1dbfd18baaca78218b3aeba Experience Services recovered Data Services went down https://status.intempt.com/ Mon, 14 Apr 2025 10:28:53 +0000 https://status.intempt.com/#d2a69899ccbebb309dee4eea91ec021e548ba401557cdfa7ea16c47f961b83b2 Data Services went down Messaging Services went down https://status.intempt.com/ Mon, 14 Apr 2025 10:28:53 +0000 https://status.intempt.com/#731c995f95905811dd6cf170e372774b29e8ef551cddb17ef7f153fda57dbebb Messaging Services went down Experience Services went down https://status.intempt.com/ Mon, 14 Apr 2025 10:27:17 +0000 https://status.intempt.com/#843567305b4751dd086bb5dd85477a21c8060b97b1dbfd18baaca78218b3aeba Experience Services went down Experience Services recovered https://status.intempt.com/ Mon, 14 Apr 2025 10:23:22 +0000 https://status.intempt.com/#7670b394e069de61d189cc68bb4ef836c7a65e1c4eecbc4745bad89c0ed95fb6 Experience Services recovered Experience Services went down https://status.intempt.com/ Mon, 14 Apr 2025 10:17:22 +0000 https://status.intempt.com/#7670b394e069de61d189cc68bb4ef836c7a65e1c4eecbc4745bad89c0ed95fb6 Experience Services went down Messaging Services recovered https://status.intempt.com/ Fri, 11 Apr 2025 09:10:01 +0000 https://status.intempt.com/#95f428f57935e1a990e6b87cd910d6a90527c322a61a53f81da6c38052aed117 Messaging Services recovered Experience Services recovered https://status.intempt.com/ Fri, 11 Apr 2025 09:09:38 +0000 https://status.intempt.com/#6c0279f1a44a139c3629fc5252d027d258b3e145a3810f02b84a007768ce707d Experience Services recovered Messaging Services went down https://status.intempt.com/ Fri, 11 Apr 2025 08:32:52 +0000 https://status.intempt.com/#95f428f57935e1a990e6b87cd910d6a90527c322a61a53f81da6c38052aed117 Messaging Services went down Experience Services went down https://status.intempt.com/ Fri, 11 Apr 2025 08:31:06 +0000 https://status.intempt.com/#6c0279f1a44a139c3629fc5252d027d258b3e145a3810f02b84a007768ce707d Experience Services went down Experience Services recovered https://status.intempt.com/ Thu, 10 Apr 2025 22:51:09 +0000 https://status.intempt.com/#506da37a1ddfae1484c6ec9b7127a263c37a7c2c13e57fb84ffb58a192b07f38 Experience Services recovered Experience Services went down https://status.intempt.com/ Thu, 10 Apr 2025 22:45:53 +0000 https://status.intempt.com/#506da37a1ddfae1484c6ec9b7127a263c37a7c2c13e57fb84ffb58a192b07f38 Experience Services went down Experience Services recovered https://status.intempt.com/ Thu, 10 Apr 2025 21:53:58 +0000 https://status.intempt.com/#63916c857034180a7a757a96fb6129d0d6ba85c060ed97b1443cfba3b9309542 Experience Services recovered Experience Services went down https://status.intempt.com/ Thu, 10 Apr 2025 21:47:58 +0000 https://status.intempt.com/#63916c857034180a7a757a96fb6129d0d6ba85c060ed97b1443cfba3b9309542 Experience Services went down Messaging Services recovered https://status.intempt.com/ Thu, 10 Apr 2025 08:44:05 +0000 https://status.intempt.com/#324b837916f0469edc036d2d48a9f9a4c2463e825e9e4aa981036d77dbacecc4 Messaging Services recovered Messaging Services went down https://status.intempt.com/ Thu, 10 Apr 2025 08:38:56 +0000 https://status.intempt.com/#324b837916f0469edc036d2d48a9f9a4c2463e825e9e4aa981036d77dbacecc4 Messaging Services went down Experience Services recovered https://status.intempt.com/ Wed, 09 Apr 2025 11:34:19 +0000 https://status.intempt.com/#804d18b27f2a9cea386f471db33a4f82b57dbbd589358d7a53f2235987342c72 Experience Services recovered Experience Services went down https://status.intempt.com/ Wed, 09 Apr 2025 11:23:15 +0000 https://status.intempt.com/#804d18b27f2a9cea386f471db33a4f82b57dbbd589358d7a53f2235987342c72 Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 14:37:24 +0000 https://status.intempt.com/#2ef7f702a23723ecc924016f51f1482eee8ee6f084716760c6d7a93c4fc5ca7d Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 14:32:02 +0000 https://status.intempt.com/#2ef7f702a23723ecc924016f51f1482eee8ee6f084716760c6d7a93c4fc5ca7d Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 13:00:46 +0000 https://status.intempt.com/#49fc8851ca3d41e4d83e6ec3d1a05e77cc7e37501901b8ace6c81f84bfdccded Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 12:34:43 +0000 https://status.intempt.com/#49fc8851ca3d41e4d83e6ec3d1a05e77cc7e37501901b8ace6c81f84bfdccded Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 12:12:48 +0000 https://status.intempt.com/#528a7aae78bb9ddfcd786e68f04cf3273b2073865ed916e1bfcd132c3e0e76af Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 12:03:43 +0000 https://status.intempt.com/#528a7aae78bb9ddfcd786e68f04cf3273b2073865ed916e1bfcd132c3e0e76af Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 11:48:48 +0000 https://status.intempt.com/#57437bd83d7ce6d6007bbca1b06d315aaf158dae5555ee8ef5f4773d7dcd0199 Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 11:37:41 +0000 https://status.intempt.com/#57437bd83d7ce6d6007bbca1b06d315aaf158dae5555ee8ef5f4773d7dcd0199 Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 04:42:24 +0000 https://status.intempt.com/#2430449967b8af504331145e8ba82c50bdd3e6238e3647b5532b1468084194db Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 04:36:54 +0000 https://status.intempt.com/#2430449967b8af504331145e8ba82c50bdd3e6238e3647b5532b1468084194db Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 03:36:28 +0000 https://status.intempt.com/#87d7e125bce03c3e2f0769efa13d369c6c5db4f71e8c05c6e1c97a525bea36f4 Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 03:30:29 +0000 https://status.intempt.com/#87d7e125bce03c3e2f0769efa13d369c6c5db4f71e8c05c6e1c97a525bea36f4 Experience Services went down Experience Services recovered https://status.intempt.com/ Tue, 08 Apr 2025 01:39:27 +0000 https://status.intempt.com/#39815ff926de0998760f80603ebe17dc5644875617b7c65246924941cb63f6c7 Experience Services recovered Experience Services went down https://status.intempt.com/ Tue, 08 Apr 2025 01:33:56 +0000 https://status.intempt.com/#39815ff926de0998760f80603ebe17dc5644875617b7c65246924941cb63f6c7 Experience Services went down Experience Services recovered https://status.intempt.com/ Mon, 07 Apr 2025 20:42:29 +0000 https://status.intempt.com/#577c6b344c4917862d4c54494877e425a421e06de287be4312a6091ac679610b Experience Services recovered Experience Services went down https://status.intempt.com/ Mon, 07 Apr 2025 20:36:26 +0000 https://status.intempt.com/#577c6b344c4917862d4c54494877e425a421e06de287be4312a6091ac679610b Experience Services went down Experience Services recovered https://status.intempt.com/ Mon, 07 Apr 2025 09:48:14 +0000 https://status.intempt.com/#5b4b8cf33f245364ff6a6a96a0a26001d0eaf2d6b3e7dae765a4585085fc8c93 Experience Services recovered Experience Services went down https://status.intempt.com/ Mon, 07 Apr 2025 09:37:13 +0000 https://status.intempt.com/#5b4b8cf33f245364ff6a6a96a0a26001d0eaf2d6b3e7dae765a4585085fc8c93 Experience Services went down Experience Services recovered https://status.intempt.com/ Fri, 04 Apr 2025 15:38:31 +0000 https://status.intempt.com/#74b5fedcc900611e5e4eb59117cd63871c6fd0b049361914fac006b7190f5ceb Experience Services recovered Experience Services went down https://status.intempt.com/ Fri, 04 Apr 2025 15:33:25 +0000 https://status.intempt.com/#74b5fedcc900611e5e4eb59117cd63871c6fd0b049361914fac006b7190f5ceb Experience Services went down Experience Services recovered https://status.intempt.com/ Thu, 03 Apr 2025 12:25:29 +0000 https://status.intempt.com/#386e40d12b94180ffab1de1d24c02d564b911f1b5f7f45e11e7d7d22865985b4 Experience Services recovered Experience Services went down https://status.intempt.com/ Thu, 03 Apr 2025 12:19:28 +0000 https://status.intempt.com/#386e40d12b94180ffab1de1d24c02d564b911f1b5f7f45e11e7d7d22865985b4 Experience Services went down Experience Services recovered https://status.intempt.com/ Thu, 03 Apr 2025 10:31:17 +0000 https://status.intempt.com/#73a6179d7ed22d98c0b8b1da75a86730c8549519fd4d271743988293817800b8 Experience Services recovered Experience Services went down https://status.intempt.com/ Thu, 03 Apr 2025 09:23:06 +0000 https://status.intempt.com/#73a6179d7ed22d98c0b8b1da75a86730c8549519fd4d271743988293817800b8 Experience Services went down Experience Services recovered https://status.intempt.com/ Thu, 03 Apr 2025 08:04:02 +0000 https://status.intempt.com/#0c7d32473a4e5ae324eb68a9d1fbfcc76bcc83131228a4e49aaa6a96f01b9195 Experience Services recovered Experience Services went down https://status.intempt.com/ Thu, 03 Apr 2025 07:57:46 +0000 https://status.intempt.com/#0c7d32473a4e5ae324eb68a9d1fbfcc76bcc83131228a4e49aaa6a96f01b9195 Experience Services went down