https://yakchat.cronitorstatus.com/historyStatus Page - Incident Feeden-usTue, 19 May 2026 13:23:53 +0000https://yakchat.cronitorstatus.com/history/f0700f7d13622ad4[Unresolved] 2026-05-19 13:23 UTC - "Issue opened on monitor failure." [Investigating] 2026-05-19 13:31 UTC - "Investigating the automatic monitor alert." [Resolved] 2026-05-19 13:37 UTC - "Issue resolved on monitor recovery."Tue, 19 May 2026 13:23:53 +0000https://yakchat.cronitorstatus.com/history/f0700f7d13622ad4https://yakchat.cronitorstatus.com/history/cfe7c6217ddc36e8[Identified] 2026-03-24 18:24 UTC - "Messages stopped posting on the Microsoft Teams Channel by the Bot" [Identified] 2026-03-24 19:45 UTC - "Issue replicated and investigation continuing" [Resolved] 2026-03-24 20:28 UTC - "Microsoft Bot Framework (smba.trafficmanager.net) experienced a major outage/degradation. Issue resolved by Microsoft without YakChat intervention." [Monitoring] 2026-03-24 20:29 UTC - "Confirmation received that Bot framework appears to be working again and customers confirmed working as expected. Continue to monitor." [Resolved] 2026-03-25 10:01 UTC - "Root cause was found within traces and logs to confirm degradation on Microsoft Teams API endpoints and was resolved without intervention from YakChat."Tue, 24 Mar 2026 18:24:00 +0000https://yakchat.cronitorstatus.com/history/cfe7c6217ddc36e8https://yakchat.cronitorstatus.com/history/7ea0886b5b012a3c[Investigating] 2025-11-06 20:48 UTC - "There is an issue with the Microsoft Azure network that is resulting in some customers being unable to access the service. This is currently being investigated by the engineering team." [Monitoring] 2025-11-06 21:07 UTC - "The Azure issue appears to have cleared but we will continue monitoring." [Resolved] 2025-11-06 21:19 UTC [Resolved] 2025-11-06 21:19 UTCThu, 06 Nov 2025 20:48:53 +0000https://yakchat.cronitorstatus.com/history/7ea0886b5b012a3chttps://yakchat.cronitorstatus.com/history/a1d15244fb049887[Unresolved] 2025-08-22 09:52 UTC - "Issue opened on monitor failure." [Resolved] 2025-08-22 10:18 UTC [Resolved] 2025-08-22 10:23 UTC - "The status page was monitoring the incorrect URL. This has been corrected. There was no impact on the live service."Fri, 22 Aug 2025 09:52:27 +0000https://yakchat.cronitorstatus.com/history/a1d15244fb049887https://yakchat.cronitorstatus.com/history/61a11b8dd80e05be[Unresolved] 2025-05-19 15:58 UTC - "Issue opened on monitor failure." [Unresolved] 2025-05-19 16:00 UTC - "This issue currently being investigated by the technical team." [Resolved] 2025-05-19 16:05 UTC - "The issue has been resolved."Mon, 19 May 2025 15:58:15 +0000https://yakchat.cronitorstatus.com/history/61a11b8dd80e05behttps://yakchat.cronitorstatus.com/history/cfcd434b3acfee30[Unresolved] 2025-04-03 11:07 UTC - "Issue opened on monitor failure." [Resolved] 2025-04-03 11:59 UTC - "Issue was related to the service status monitoring connection only after moving the API endpoint. There was no outage of the YakChat API and status monitoring was re-instated on the new API endpoint."Thu, 03 Apr 2025 11:07:44 +0000https://yakchat.cronitorstatus.com/history/cfcd434b3acfee30https://yakchat.cronitorstatus.com/history/99acf4ac0fc1148c[Unresolved] 2025-02-19 09:21 UTC - "Issue opened on monitor failure." [Resolved] 2025-02-19 09:29 UTC - "Issue resolved on monitor recovery."Wed, 19 Feb 2025 09:21:33 +0000https://yakchat.cronitorstatus.com/history/99acf4ac0fc1148chttps://yakchat.cronitorstatus.com/history/4d35bf074b869a9f[Unresolved] 2024-07-18 22:44 UTC - "Issue opened on monitor failure." [Resolved] 2024-07-19 01:54 UTC - "Issue resolved on monitor recovery." [Monitoring] 2024-07-19 07:45 UTC - "There was a major incident with Microsoft Azure and there are ongoing investigations. The YakChat service automatically recovered and is operating normally but we will continue to monitor until Microsoft report that they have resolved the problem." [Resolved] 2024-07-19 07:50 UTC [Monitoring] 2024-07-19 07:51 UTC - "The outage was caused by a a major incident with Microsoft Azure. Microsoft are reporting ongoing investigations into the issue. The YakChat service automatically recovered and is operating normally but we will continue to monitor until Microsoft report that they have resolved the problem." [Resolved] 2024-07-19 16:23 UTC - "Microsoft are stating that the issues in the US Central hub have been mitigated but they are continuing to monitor"Thu, 18 Jul 2024 22:44:54 +0000https://yakchat.cronitorstatus.com/history/4d35bf074b869a9fhttps://yakchat.cronitorstatus.com/history/7b5e3f822f4bdf4e[Identified] 2024-04-23 15:00 UTC - "There is an issue with one of our UK SMS service providers not processing inbound texts. This is an ongoing issue that has been escalated to the service provider and we are doing everything we can to restore service for these numbers as soon as possible." [Monitoring] 2024-04-24 13:13 UTC - "We have been updated that this issue has now been resolved from the UK SMS provider. We will continue to monitor our services to ensure inbound SMS messages are arriving into our platform" [Monitoring] 2024-04-24 13:35 UTC [Resolved] 2024-04-24 14:21 UTC - "We can confirm the issue has been resolved." [Resolved] 2024-04-24 14:21 UTCTue, 23 Apr 2024 15:00:00 +0000https://yakchat.cronitorstatus.com/history/7b5e3f822f4bdf4ehttps://yakchat.cronitorstatus.com/history/74abd5facccca38b[Identified] 2023-12-06 14:30 UTC - "The notification provided when an adaptive card is received in Microsoft Teams chat is different in the new version of Microsoft Teams which affects YakChat new message notifications for personal inboxes only. This maybe resolved in the future by Microsoft Teams but we are working on a workaround which we will make available as soon as possible." [Identified] 2023-12-07 20:22 UTC - "An update was released for YakChat 2.1.12 which will resolve the issue for customers using the latest YakChat application. Please contact us at info@yakchat.com if you wish to upgrade to the latest application in Microsoft Teams." [Resolved] 2023-12-07 20:24 UTCWed, 06 Dec 2023 14:30:22 +0000https://yakchat.cronitorstatus.com/history/74abd5facccca38bhttps://yakchat.cronitorstatus.com/history/9130bfda4aa830d8[Unresolved] 2023-11-28 09:17 UTC - "Issue opened on monitor failure." [Resolved] 2023-11-28 09:27 UTC - "Issue resolved on monitor recovery." [Resolved] 2023-11-28 09:27 UTCTue, 28 Nov 2023 09:17:18 +0000https://yakchat.cronitorstatus.com/history/9130bfda4aa830d8https://yakchat.cronitorstatus.com/history/e894441623823366[Unresolved] 2023-09-13 17:31 UTC - "Issue opened on monitor failure." [Resolved] 2023-09-13 17:41 UTC - "Issue resolved on monitor recovery."Wed, 13 Sep 2023 17:31:31 +0000https://yakchat.cronitorstatus.com/history/e894441623823366https://yakchat.cronitorstatus.com/history/a494b4f3d121a8c2[Unresolved] 2023-07-02 08:02 UTC - "Issue opened on monitor failure." [Identified] 2023-07-02 08:09 UTC [Resolved] 2023-07-02 08:27 UTC - "Issue resolved on monitor recovery."Sun, 02 Jul 2023 08:02:31 +0000https://yakchat.cronitorstatus.com/history/a494b4f3d121a8c2https://yakchat.cronitorstatus.com/history/e17311d1cce4f7a2[Unresolved] 2023-06-26 15:25 UTC - "Issue opened on monitor failure." [Resolved] 2023-06-26 15:35 UTC - "Issue resolved on monitor recovery."Mon, 26 Jun 2023 15:25:19 +0000https://yakchat.cronitorstatus.com/history/e17311d1cce4f7a2https://yakchat.cronitorstatus.com/history/b5422518da5601cc[Unresolved] 2023-05-22 15:30 UTC - "Issue opened on monitor failure." [Resolved] 2023-05-22 15:40 UTC - "Issue resolved on monitor recovery."Mon, 22 May 2023 15:30:51 +0000https://yakchat.cronitorstatus.com/history/b5422518da5601cchttps://yakchat.cronitorstatus.com/history/993b0b8e49bc3068[Unresolved] 2023-05-11 17:28 UTC - "Issue opened on monitor failure." [Resolved] 2023-05-11 17:37 UTC - "Issue resolved on monitor recovery."Thu, 11 May 2023 17:28:04 +0000https://yakchat.cronitorstatus.com/history/993b0b8e49bc3068https://yakchat.cronitorstatus.com/history/076b30b4d4632c1d[Monitoring] 2023-05-11 08:10 UTC - "Various security updates are being applied to the services, no impact to services during update." [Monitoring] 2023-05-11 09:31 UTC - "Deployment has been successful, post-deployment monitoring is continuing for a short period before closing the maintenance" [Resolved] 2023-05-11 09:54 UTC - "All monitoring looks healthy and security updates and various bug fixes have been applied successfully."Thu, 11 May 2023 08:18:48 +0000https://yakchat.cronitorstatus.com/history/076b30b4d4632c1dhttps://yakchat.cronitorstatus.com/history/bfd90bd164505539[Unresolved] 2023-04-13 17:56 UTC - "Issue opened on monitor failure." [Resolved] 2023-04-13 18:06 UTC - "Issue resolved on monitor recovery."Thu, 13 Apr 2023 17:56:34 +0000https://yakchat.cronitorstatus.com/history/bfd90bd164505539https://yakchat.cronitorstatus.com/history/c1dd6f8d134b4760[Unresolved] 2023-04-06 23:41 UTC - "Issue opened on monitor failure." [Resolved] 2023-04-06 23:41 UTC - "Issue resolved on monitor recovery." [Unresolved] 2023-04-06 23:46 UTC - "Incident re-opened on monitor failure." [Resolved] 2023-04-07 00:11 UTC - "Issue resolved on monitor recovery." [Investigating] 2023-04-12 15:09 UTC [Resolved] 2023-04-12 15:10 UTCThu, 06 Apr 2023 23:41:18 +0000https://yakchat.cronitorstatus.com/history/c1dd6f8d134b4760