Incidents reported on status page for Insite LMS https://status.insitelms.net/ https://d1lppblt9t2x15.cloudfront.net/logos/4c3962e07e2e6073cd3dcd334a64e0bc.png https://status.insitelms.net/ en https://status.insitelms.net/ Fri, 21 Nov 2025 20:03:06 +0000 https://status.insitelms.net/#fcccea52f37a65d37059a9cf669398348e8ba91e7afed7998f4d43617d6cbb07 Insite LMS Web recovered https://status.insitelms.net/ Fri, 21 Nov 2025 19:59:06 +0000 https://status.insitelms.net/#fcccea52f37a65d37059a9cf669398348e8ba91e7afed7998f4d43617d6cbb07 Insite LMS Web went down https://status.insitelms.net/ Wed, 29 Oct 2025 21:01:38 +0000 https://status.insitelms.net/#e7395fcd681a699ce902723055f14bfe1853b159d7893bf1b73455a65593f705 Report API recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:56:36 +0000 https://status.insitelms.net/#e7395fcd681a699ce902723055f14bfe1853b159d7893bf1b73455a65593f705 Report API went down https://status.insitelms.net/ Wed, 29 Oct 2025 20:55:51 +0000 https://status.insitelms.net/#0e62fb9c46c9bf628038f335c64e5131e63cb5b7bc813b55cc7207067ff83ff7 API recovered https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:55:00 -0000 https://status.insitelms.net/incident/753840#71647849ebe143d86393173e35dd1ee3439efbd323905872aeb0dcdfea0b4f1c The issue seems to be resolved. Smaller hickups may still occur, but we are successfully able to access all our systems. We will post the Azure post mortem once it is available under https://docs.insitelms.net/general-information/hosting-information We apologize for any inconveniences and hope, Microsoft will be able to fix their Front Door deployments. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 20:53:00 -0000 https://status.insitelms.net/incident/753840#3d6f95625a7f340c8916cfc0df638407042938c5eef6a4ac5a93b1ff13f999fe We are seeing recovery. Thank you all for your patience! https://status.insitelms.net/ Wed, 29 Oct 2025 20:46:17 +0000 https://status.insitelms.net/#cbcc1e6120faebe6362ccd718b39f5d62f31915925086231d9f3333777b6d453 Import API recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:43:34 +0000 https://status.insitelms.net/#5bce7d18b0bba61e0ffb8ca503763fac78ab23357c491e8561fd774351fa9686 Sync API recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:32:03 +0000 https://status.insitelms.net/#eae8650d0b33b5b794c9c41f9e2210d4e6c0e3f36008a341d5fd9f5d53a1c66b Report API recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:31:32 +0000 https://status.insitelms.net/#930fd77ddbe98cc186664610a655fce0659ccb5fef2613c0c907dcf43ad99e46 portal.insitelms.net recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:31:32 +0000 https://status.insitelms.net/#9ee80951fafacf675e2a11babc2dee8161073ebedd1a38fc6add37e74f000a6a Insite LMS Web recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:29:02 +0000 https://status.insitelms.net/#0e62fb9c46c9bf628038f335c64e5131e63cb5b7bc813b55cc7207067ff83ff7 API went down https://status.insitelms.net/ Wed, 29 Oct 2025 20:26:14 +0000 https://status.insitelms.net/#668cf95c8ba4edb2dd4e668e8aacdfcf76c27e5259d58ad794fca60c8c356122 Public API recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:26:08 +0000 https://status.insitelms.net/#3850cd9cfcced3ee6bd4c2463a444259440ded2af5db5e97b6e2b35f3424e9db E-Mail Interface recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:23:20 +0000 https://status.insitelms.net/#3c08e5cef1e2f743e445a73e4acb9c323b5acb67917dbd230c8bc97d15caad79 Authenticator API recovered https://status.insitelms.net/ Wed, 29 Oct 2025 20:22:37 +0000 https://status.insitelms.net/#c1de85b124887264a577dfdd4d7d7a65f3d78be3caacf04692226fde483c15f6 API recovered https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 19:21:00 -0000 https://status.insitelms.net/incident/753840#4893227a820eb48347e501359ff9fbeec198e57f4f4d7cf8896fd30f60064bd9 Update from Azure: We initiated the deployment of our ‘last known good’ configuration, which has now successfully been completed. Customers may have begun to see initial signs of recovery. We are currently recovering nodes and routing traffic through healthy nodes, and as we make progress in this workstream, customers will continue to see improvement. At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. We will provide another update on our progress within two hours, or sooner if warranted. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:57:00 -0000 https://status.insitelms.net/incident/753840#01c6bcbfd5c9e75df120d6d9bce44af4b66eadafd9fa3f3da7475beca6d55f33 Update from Azure: We have initiated the deployment of our last known good configuration. This deployment was initially expected to complete within 45 minutes; however, due to protective blocks we have put in place to safeguard the AFD service, we are encountering some delays. While progress is ongoing, these safeguards are extending the overall deployment time. Once the rollout is complete, we will begin recovering nodes and re-routing traffic through healthy nodes to accelerate recovery. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 18:13:00 -0000 https://status.insitelms.net/incident/753840#ae90708fe4a08831807f0773a85cec5a3fe62b15b8ba938296e227ba4952334f An interesting update from Azure: Current status: We have initiated the deployment of our 'last known good' configuration. This is expected to be fully deployed in about 30 minutes from which point customers will start to see initial signs of recovery. Once this is completed, the next stage is to start to recover nodes while we route traffic through these healthy nodes. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 17:20:00 -0000 https://status.insitelms.net/incident/753840#fd5d5a2a4a9264598f6579340113119826eee0d348d6f41fa3f55aa2e4498d2f Microsoft is still working to resolve the Azure Front Door issues, please check their website: https://azure.status.microsoft/en-us/status This is noted on their website at the moment: Starting at approximately 16:00 UTC, we began experiencing Azure Front Door (AFD) issues resulting in a loss of availability of some services. We suspect that an inadvertent configuration change as the trigger event for this issue. We are taking two concurrent actions where we are blocking all changes to the AFD services and at the same time rolling back to our last known good state. We have failed the portal away from AFD to mitigate the portal access issues. Customers should be able to access the Azure management portal directly. We do not have an ETA for when the rollback will be completed, but we will update this communication within 30 minutes or when we have an update. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:38:00 -0000 https://status.insitelms.net/incident/753840#2207822739aae5f61906bb8d47769e38f2ae0ef42b140b8f515b37e00cb97df1 At this stage we see that not just Azure, all big providers are having issues. This seems like a much bigger problem. https://downdetector.com/ https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:22:00 -0000 https://status.insitelms.net/incident/753840#4bc98d8235ff550d689b346a8c371fd5ece68106f0cf7fd8a4ad5628b55e4c91 Finally Microsoft has acknowledged the issue on their official status page: https://azure.status.microsoft/en-us/status https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 16:12:00 -0000 https://status.insitelms.net/incident/753840#63be78f008154314d0dc20d03245cd21ca786e08d1ae6de96604ed1525014898 Azure Front Door, the component to manage all incoming connections is clearly down / having issues. We can't really access the cental Azure portal as well, and reports from around the world show, they are having the same issues. We can only apologize at this stage for the inconvenience. https://status.insitelms.net/ Wed, 29 Oct 2025 16:00:06 +0000 https://status.insitelms.net/#eae8650d0b33b5b794c9c41f9e2210d4e6c0e3f36008a341d5fd9f5d53a1c66b Report API went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:58:15 +0000 https://status.insitelms.net/#3c08e5cef1e2f743e445a73e4acb9c323b5acb67917dbd230c8bc97d15caad79 Authenticator API went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:56:21 +0000 https://status.insitelms.net/#9ee80951fafacf675e2a11babc2dee8161073ebedd1a38fc6add37e74f000a6a Insite LMS Web went down https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/incident/753840 Wed, 29 Oct 2025 15:56:00 -0000 https://status.insitelms.net/incident/753840#428fd2d0d6c35da68559a7d0a2d5043ecfb621c7a07439a3f3a339db027fb8d8 Unfortunately we see Microsoft Azure having issues again: https://statusgator.com/services/azure We are investigating https://status.insitelms.net/ Wed, 29 Oct 2025 15:55:11 +0000 https://status.insitelms.net/#668cf95c8ba4edb2dd4e668e8aacdfcf76c27e5259d58ad794fca60c8c356122 Public API went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:50:51 +0000 https://status.insitelms.net/#5bce7d18b0bba61e0ffb8ca503763fac78ab23357c491e8561fd774351fa9686 Sync API went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:47:32 +0000 https://status.insitelms.net/#c1de85b124887264a577dfdd4d7d7a65f3d78be3caacf04692226fde483c15f6 API went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:47:23 +0000 https://status.insitelms.net/#cbcc1e6120faebe6362ccd718b39f5d62f31915925086231d9f3333777b6d453 Import API went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:47:11 +0000 https://status.insitelms.net/#930fd77ddbe98cc186664610a655fce0659ccb5fef2613c0c907dcf43ad99e46 portal.insitelms.net went down https://status.insitelms.net/ Wed, 29 Oct 2025 15:46:07 +0000 https://status.insitelms.net/#3850cd9cfcced3ee6bd4c2463a444259440ded2af5db5e97b6e2b35f3424e9db E-Mail Interface went down https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 14:19:00 -0000 https://status.insitelms.net/incident/740442#53665694cb90e3062e84c24f94513d9b5bd7c6c19d592dc9088670aaacc76542 All our services are now fully operational again. Thank you for your patience and understanding. If you continue to experience any problems, please don’t hesitate to contact us. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 12:52:00 -0000 https://status.insitelms.net/incident/740442#a1257599d8175972395b1cb3a4937e71c366ba73b7136f20268caf25ebe1cad7 Connection problems are reduced, but Microsoft has still not fully resolved the underlying issue: https://azure.status.microsoft/en-us/status Current Status: As we continue our mitigation efforts, we have successfully recovered 96% of impacted resources, teams are working on recovering the remaining 4% of impacted resources. The next update will be provided within 60 minutes. This message was last updated at 12:40 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:55:00 -0000 https://status.insitelms.net/incident/740442#7c56db409ad635285a430b126d20c427437c4d99d3b60541985fe313064896c2 Microsoft published an update: https://azure.status.microsoft/en-us/status We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 10:38:00 -0000 https://status.insitelms.net/incident/740442#fdcfbf596604b0f6dfeb7ad8a2ead9101a5451992241205bad79bb9f4fbbcb37 Microsoft has confirmed Issues with Azure Front Door: https://azure.status.microsoft/en-us/status Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent issues when accessing their services, this includes the ability to access the Azure Portal. Current Status: Our monitoring detected a significant capacity loss, of about 30% of Azure Front Door instances predominantly across Europe and Africa. At this stage we have ruled out any deployments which could have triggered this event. The next update will be provided within 60 minutes, or as events warrant. This message was last updated at 10:27 UTC on 09 October 2025 https://status.insitelms.net/ Thu, 09 Oct 2025 09:20:39 +0000 https://status.insitelms.net/#d1ffec7531822a1ca5e68167da36829f1735dca3370982c662e962e4f889a703 E-Mail Interface recovered https://status.insitelms.net/ Thu, 09 Oct 2025 09:11:07 +0000 https://status.insitelms.net/#d1ffec7531822a1ca5e68167da36829f1735dca3370982c662e962e4f889a703 E-Mail Interface went down https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 08:40:00 -0000 https://status.insitelms.net/incident/740442#a5a78521721a11bb158a02170b5256df89922f256631a8ff81505c40e4cfa4ec Azure Frontdoor (our central entry point for all connections) fired an alert: Front Door/CDN service has detected global availability drops impacting one or more regions. The issue may cause failures for client requests sent to this Front Door/CDN resource. https://status.insitelms.net/incident/740442 Thu, 09 Oct 2025 08:15:00 -0000 https://status.insitelms.net/incident/740442#59371f34e6c96d5247722dffb1b1bb04f27dfad1059f212bad7ddd703630c45b We are noticing connection issues to our main services. Logins may not work or not work at this stage https://status.insitelms.net/incident/738415 Mon, 06 Oct 2025 07:00:00 -0000 https://status.insitelms.net/incident/738415#2a73eae7cfe0234454e81eea363e729542e2988b0936ff8f15af8569e42c7e3e On October 4*th* and October 6*th*, around midnight, this automatic status page recognized certain Insite LMS services as offline (from 3 minutes to 33 minutes). After analyzing the detailed monitoring options within our Azure environment, these instances could not be confirmed and were thus removed from this status page. https://status.insitelms.net/incident/738415 Mon, 06 Oct 2025 07:00:00 -0000 https://status.insitelms.net/incident/738415#2a73eae7cfe0234454e81eea363e729542e2988b0936ff8f15af8569e42c7e3e On October 4*th* and October 6*th*, around midnight, this automatic status page recognized certain Insite LMS services as offline (from 3 minutes to 33 minutes). After analyzing the detailed monitoring options within our Azure environment, these instances could not be confirmed and were thus removed from this status page. https://status.insitelms.net/incident/738415 Mon, 06 Oct 2025 07:00:00 -0000 https://status.insitelms.net/incident/738415#2a73eae7cfe0234454e81eea363e729542e2988b0936ff8f15af8569e42c7e3e On October 4*th* and October 6*th*, around midnight, this automatic status page recognized certain Insite LMS services as offline (from 3 minutes to 33 minutes). After analyzing the detailed monitoring options within our Azure environment, these instances could not be confirmed and were thus removed from this status page. https://status.insitelms.net/incident/738415 Mon, 06 Oct 2025 07:00:00 -0000 https://status.insitelms.net/incident/738415#2a73eae7cfe0234454e81eea363e729542e2988b0936ff8f15af8569e42c7e3e On October 4*th* and October 6*th*, around midnight, this automatic status page recognized certain Insite LMS services as offline (from 3 minutes to 33 minutes). After analyzing the detailed monitoring options within our Azure environment, these instances could not be confirmed and were thus removed from this status page. https://status.insitelms.net/ Mon, 29 Sep 2025 00:22:00 +0000 https://status.insitelms.net/#7b440905d979e8193bdf2f72d772f2de438731c6d973e7e08527e6d994ce9deb Sync API recovered https://status.insitelms.net/ Mon, 29 Sep 2025 00:19:59 +0000 https://status.insitelms.net/#7b440905d979e8193bdf2f72d772f2de438731c6d973e7e08527e6d994ce9deb Sync API went down https://status.insitelms.net/incident/716586 Mon, 01 Sep 2025 16:28:00 -0000 https://status.insitelms.net/incident/716586#61380166141ff8bfc5be7c8c657406a2fa98d767fc5ee04ffd0b9f33132c5586 The issue with too many requests has been identified and actions were taken to update the backend. All telemetry is back to normal. https://status.insitelms.net/incident/716416 Mon, 01 Sep 2025 11:39:00 -0000 https://status.insitelms.net/incident/716416#4219a536fd86b5a926584edc813e59be84aa9eca336a6d9cc68ffd121f0014de We are observing an unusual spike in requests with error 429. If you are encountering this issue, please try again or send a ticket to our support https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 14:05:00 -0000 https://status.insitelms.net/incident/406119#67807eb79d4da32373b10f07a99105ed151fa64de57792e350b6398217654be2 It seems all services are up and running again. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/406119 Tue, 30 Jul 2024 12:32:00 -0000 https://status.insitelms.net/incident/406119#05a16d371ea0a49627fea327d805020ebc3fd916c855eafaaf3e079a7e064d10 We are part of a global Microsoft Azure Downtime. https://azure.status.microsoft/ We found out that over some networks e.g. mobile hotspot it is working. So not all users are affected. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Thu, 25 Jul 2024 09:31:00 -0000 https://status.insitelms.net/incident/402832#67c15f33632bc9f96f30346b4dc8d2f2be3fbe7c62b3fe89610cc0e2ad85565e The post mortem report is available here: https://docs.insitelms.net/general-information/hosting-information#id-24.07.2024-insite-lms-was-not-available We again want to sincerely apologize for yesterdays outage (the first in many years) and we will do everything we can to avoid such a scenario in the future. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 14:35:00 -0000 https://status.insitelms.net/incident/402832#938f7df2da15c2af941d68cfde37d19e3434ccf5bc2caac22e773e25dc16a5dd Everything is back online. We will publish a Post Mortem within 24h here. We apologize for any inconveniences! Thank you for your patience! https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 13:55:00 -0000 https://status.insitelms.net/incident/402832#4d49d62e3c7a35cea3d84575bee80eb3c985663e822a9c474b12de61a7c945a5 Public API and Testsystems are back online https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 11:48:00 -0000 https://status.insitelms.net/incident/402832#772c04a0cf9ea264df1fa30ecfe88f4a9ca61b226a997d1c95d41705d7acebf5 The web version is now back online with Dashboards, Workday Calendar etc. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 11:48:00 -0000 https://status.insitelms.net/incident/402832#772c04a0cf9ea264df1fa30ecfe88f4a9ca61b226a997d1c95d41705d7acebf5 The web version is now back online with Dashboards, Workday Calendar etc. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 11:48:00 -0000 https://status.insitelms.net/incident/402832#772c04a0cf9ea264df1fa30ecfe88f4a9ca61b226a997d1c95d41705d7acebf5 The web version is now back online with Dashboards, Workday Calendar etc. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 11:48:00 -0000 https://status.insitelms.net/incident/402832#772c04a0cf9ea264df1fa30ecfe88f4a9ca61b226a997d1c95d41705d7acebf5 The web version is now back online with Dashboards, Workday Calendar etc. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 11:48:00 -0000 https://status.insitelms.net/incident/402832#772c04a0cf9ea264df1fa30ecfe88f4a9ca61b226a997d1c95d41705d7acebf5 The web version is now back online with Dashboards, Workday Calendar etc. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 11:48:00 -0000 https://status.insitelms.net/incident/402832#772c04a0cf9ea264df1fa30ecfe88f4a9ca61b226a997d1c95d41705d7acebf5 The web version is now back online with Dashboards, Workday Calendar etc. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:56:00 -0000 https://status.insitelms.net/incident/402832#5f132d5205a7058592700ff9a7b8d2ced438e4de8b2227585c56879217c527e6 Sync is now back We are still working on the web version (including dashboards), Email and Test systems https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:56:00 -0000 https://status.insitelms.net/incident/402832#5f132d5205a7058592700ff9a7b8d2ced438e4de8b2227585c56879217c527e6 Sync is now back We are still working on the web version (including dashboards), Email and Test systems https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:56:00 -0000 https://status.insitelms.net/incident/402832#5f132d5205a7058592700ff9a7b8d2ced438e4de8b2227585c56879217c527e6 Sync is now back We are still working on the web version (including dashboards), Email and Test systems https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:56:00 -0000 https://status.insitelms.net/incident/402832#5f132d5205a7058592700ff9a7b8d2ced438e4de8b2227585c56879217c527e6 Sync is now back We are still working on the web version (including dashboards), Email and Test systems https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:56:00 -0000 https://status.insitelms.net/incident/402832#5f132d5205a7058592700ff9a7b8d2ced438e4de8b2227585c56879217c527e6 Sync is now back We are still working on the web version (including dashboards), Email and Test systems https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:56:00 -0000 https://status.insitelms.net/incident/402832#5f132d5205a7058592700ff9a7b8d2ced438e4de8b2227585c56879217c527e6 Sync is now back We are still working on the web version (including dashboards), Email and Test systems https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:34:00 -0000 https://status.insitelms.net/incident/402832#4754d20396a0ed04bc44d68aa19cc0aee3f86cc26854564e43abbf539bde7fec Import is now back https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:34:00 -0000 https://status.insitelms.net/incident/402832#4754d20396a0ed04bc44d68aa19cc0aee3f86cc26854564e43abbf539bde7fec Import is now back https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:34:00 -0000 https://status.insitelms.net/incident/402832#4754d20396a0ed04bc44d68aa19cc0aee3f86cc26854564e43abbf539bde7fec Import is now back https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:34:00 -0000 https://status.insitelms.net/incident/402832#4754d20396a0ed04bc44d68aa19cc0aee3f86cc26854564e43abbf539bde7fec Import is now back https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:34:00 -0000 https://status.insitelms.net/incident/402832#4754d20396a0ed04bc44d68aa19cc0aee3f86cc26854564e43abbf539bde7fec Import is now back https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:34:00 -0000 https://status.insitelms.net/incident/402832#4754d20396a0ed04bc44d68aa19cc0aee3f86cc26854564e43abbf539bde7fec Import is now back https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:21:00 -0000 https://status.insitelms.net/incident/402832#068ed0d376edfdd483689a44280dce029a3b1dd9179f646dd7f5a428c23ea1d8 Our main datacenter West EU has unexplainable Network issues. We can confirm at this moment that we didn't do any changes to our backend that would explain the network problems Normal Login and Reports are now working. We are still working on the components which are not working at this moment. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:21:00 -0000 https://status.insitelms.net/incident/402832#068ed0d376edfdd483689a44280dce029a3b1dd9179f646dd7f5a428c23ea1d8 Our main datacenter West EU has unexplainable Network issues. We can confirm at this moment that we didn't do any changes to our backend that would explain the network problems Normal Login and Reports are now working. We are still working on the components which are not working at this moment. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:21:00 -0000 https://status.insitelms.net/incident/402832#068ed0d376edfdd483689a44280dce029a3b1dd9179f646dd7f5a428c23ea1d8 Our main datacenter West EU has unexplainable Network issues. We can confirm at this moment that we didn't do any changes to our backend that would explain the network problems Normal Login and Reports are now working. We are still working on the components which are not working at this moment. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:21:00 -0000 https://status.insitelms.net/incident/402832#068ed0d376edfdd483689a44280dce029a3b1dd9179f646dd7f5a428c23ea1d8 Our main datacenter West EU has unexplainable Network issues. We can confirm at this moment that we didn't do any changes to our backend that would explain the network problems Normal Login and Reports are now working. We are still working on the components which are not working at this moment. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:21:00 -0000 https://status.insitelms.net/incident/402832#068ed0d376edfdd483689a44280dce029a3b1dd9179f646dd7f5a428c23ea1d8 Our main datacenter West EU has unexplainable Network issues. We can confirm at this moment that we didn't do any changes to our backend that would explain the network problems Normal Login and Reports are now working. We are still working on the components which are not working at this moment. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 09:21:00 -0000 https://status.insitelms.net/incident/402832#068ed0d376edfdd483689a44280dce029a3b1dd9179f646dd7f5a428c23ea1d8 Our main datacenter West EU has unexplainable Network issues. We can confirm at this moment that we didn't do any changes to our backend that would explain the network problems Normal Login and Reports are now working. We are still working on the components which are not working at this moment. https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 07:00:00 -0000 https://status.insitelms.net/incident/402832#6a6d7cf3174c5668dd0a3a7806d4b8371fb4b8a41bbe2528769ce77efc28a21a Normal login is possible again. Reports, Imports, Sync, Web and Email are not available https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 07:00:00 -0000 https://status.insitelms.net/incident/402832#6a6d7cf3174c5668dd0a3a7806d4b8371fb4b8a41bbe2528769ce77efc28a21a Normal login is possible again. Reports, Imports, Sync, Web and Email are not available https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 07:00:00 -0000 https://status.insitelms.net/incident/402832#6a6d7cf3174c5668dd0a3a7806d4b8371fb4b8a41bbe2528769ce77efc28a21a Normal login is possible again. Reports, Imports, Sync, Web and Email are not available https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 07:00:00 -0000 https://status.insitelms.net/incident/402832#6a6d7cf3174c5668dd0a3a7806d4b8371fb4b8a41bbe2528769ce77efc28a21a Normal login is possible again. Reports, Imports, Sync, Web and Email are not available https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 07:00:00 -0000 https://status.insitelms.net/incident/402832#6a6d7cf3174c5668dd0a3a7806d4b8371fb4b8a41bbe2528769ce77efc28a21a Normal login is possible again. Reports, Imports, Sync, Web and Email are not available https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 07:00:00 -0000 https://status.insitelms.net/incident/402832#6a6d7cf3174c5668dd0a3a7806d4b8371fb4b8a41bbe2528769ce77efc28a21a Normal login is possible again. Reports, Imports, Sync, Web and Email are not available https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 05:30:00 -0000 https://status.insitelms.net/incident/402832#3c23f000757e33b4ac2c912f550b009ee0b235d5ec1db4bfe8167c280530c592 Insite LMS is not available with all components (Please click here to see further updates) https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 05:30:00 -0000 https://status.insitelms.net/incident/402832#3c23f000757e33b4ac2c912f550b009ee0b235d5ec1db4bfe8167c280530c592 Insite LMS is not available with all components (Please click here to see further updates) https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 05:30:00 -0000 https://status.insitelms.net/incident/402832#3c23f000757e33b4ac2c912f550b009ee0b235d5ec1db4bfe8167c280530c592 Insite LMS is not available with all components (Please click here to see further updates) https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 05:30:00 -0000 https://status.insitelms.net/incident/402832#3c23f000757e33b4ac2c912f550b009ee0b235d5ec1db4bfe8167c280530c592 Insite LMS is not available with all components (Please click here to see further updates) https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 05:30:00 -0000 https://status.insitelms.net/incident/402832#3c23f000757e33b4ac2c912f550b009ee0b235d5ec1db4bfe8167c280530c592 Insite LMS is not available with all components (Please click here to see further updates) https://status.insitelms.net/incident/402832 Wed, 24 Jul 2024 05:30:00 -0000 https://status.insitelms.net/incident/402832#3c23f000757e33b4ac2c912f550b009ee0b235d5ec1db4bfe8167c280530c592 Insite LMS is not available with all components (Please click here to see further updates) https://status.insitelms.net/incident/326653 Wed, 14 Feb 2024 11:01:00 -0000 https://status.insitelms.net/incident/326653#43610f736fb72e6db26c99ad31a1d65d4a20902f99e1865c17fdc4f48bd0c7e5 Azure has reported with one component (Front Door), we were investigating, Message from Azure: "We are sorry, your Front Door/CDN profile may be experiencing problems. We're working to determine and address the source of the problem. No additional action is required from you at this time." After ~15 Minutes everything was working again. https://status.insitelms.net/incident/310794 Wed, 10 Jan 2024 13:20:00 -0000 https://status.insitelms.net/incident/310794#e2525d0a30b6792de0a14e9b3a905165c584bdc395c9c4a17b336a56f2433961 An update to 8.3.18 is available and reports work again after switching a project. We apologize for any inconveniences! https://status.insitelms.net/incident/310794 Wed, 10 Jan 2024 12:25:00 -0000 https://status.insitelms.net/incident/310794#c098bca2fe0096260cdf42115d687188278fcae015cf4afdeefbfe94d333aa2c There is a problem with the latest desktop version update, that reports don't work after switching the project. Our engineers are working on it and we hope to provide an update soon! https://status.insitelms.net/incident/291083 Thu, 23 Nov 2023 13:33:00 -0000 https://status.insitelms.net/incident/291083#24683aeae3c61e1022d6c7cdbfebcf2cca5bf0850621e2068b797ed1a38f9419 Our engineers have identified the issue. It was related with large reports (e.g. having 10.000 items selected to print a report) We apologize for any inconveniences and hope all reports are running well! https://status.insitelms.net/incident/291083 Thu, 23 Nov 2023 07:42:00 -0000 https://status.insitelms.net/incident/291083#b6f5320e44d6f202d549294a4eccc743d1c5bbace42cb588ad41f0130ffaa205 We have received feedback from multiple users that reports are not working. We can state that it must be connected to a certain country or use case of reports and it does NOT affect all users. We are working on this issue with high priority and hope we can identify the root cause soon! https://status.insitelms.net/incident/226275 Thu, 29 Jun 2023 15:27:00 -0000 https://status.insitelms.net/incident/226275#ace04f5508b43390fd37353c4787f46daac6ef7ae5976d1f84f0a825f5fce440 We had issues logging in for 15 minutes, system is working again. Some regions may still experience login problems, caches may take a few minutes to restore. https://status.insitelms.net/incident/168081 Wed, 25 Jan 2023 08:31:00 -0000 https://status.insitelms.net/incident/168081#2812b695ccf37b38f5c111efda7a385a1e1ca882de207d7f73bd90632e1b831b MS Azure is still facing Network problems as now indicated on https://status.azure.com/, but Insite LMS is and was available the whole time. https://status.insitelms.net/incident/168081 Wed, 25 Jan 2023 08:31:00 -0000 https://status.insitelms.net/incident/168081#2812b695ccf37b38f5c111efda7a385a1e1ca882de207d7f73bd90632e1b831b MS Azure is still facing Network problems as now indicated on https://status.azure.com/, but Insite LMS is and was available the whole time. https://status.insitelms.net/incident/168081 Wed, 25 Jan 2023 08:31:00 -0000 https://status.insitelms.net/incident/168081#2812b695ccf37b38f5c111efda7a385a1e1ca882de207d7f73bd90632e1b831b MS Azure is still facing Network problems as now indicated on https://status.azure.com/, but Insite LMS is and was available the whole time. https://status.insitelms.net/incident/168081 Wed, 25 Jan 2023 08:31:00 -0000 https://status.insitelms.net/incident/168081#2812b695ccf37b38f5c111efda7a385a1e1ca882de207d7f73bd90632e1b831b MS Azure is still facing Network problems as now indicated on https://status.azure.com/, but Insite LMS is and was available the whole time. https://status.insitelms.net/incident/168081 Wed, 25 Jan 2023 08:31:00 -0000 https://status.insitelms.net/incident/168081#2812b695ccf37b38f5c111efda7a385a1e1ca882de207d7f73bd90632e1b831b MS Azure is still facing Network problems as now indicated on https://status.azure.com/, but Insite LMS is and was available the whole time. https://status.insitelms.net/incident/168058 Wed, 25 Jan 2023 08:13:00 -0000 https://status.insitelms.net/incident/168058#04393ea49c2d44f0bb90b35e333f9b009616202c6abd0a05b9e7ad09a5ee894f As of now, the whole MS landscape including Teams, Azure, Office 365 faces major problems. This problem is also affecting us and we will provide an update as soon as we know more. https://status.azure.com/ is not responding currently https://status.insitelms.net/incident/168058 Wed, 25 Jan 2023 08:13:00 -0000 https://status.insitelms.net/incident/168058#04393ea49c2d44f0bb90b35e333f9b009616202c6abd0a05b9e7ad09a5ee894f As of now, the whole MS landscape including Teams, Azure, Office 365 faces major problems. This problem is also affecting us and we will provide an update as soon as we know more. https://status.azure.com/ is not responding currently https://status.insitelms.net/incident/168058 Wed, 25 Jan 2023 08:13:00 -0000 https://status.insitelms.net/incident/168058#04393ea49c2d44f0bb90b35e333f9b009616202c6abd0a05b9e7ad09a5ee894f As of now, the whole MS landscape including Teams, Azure, Office 365 faces major problems. This problem is also affecting us and we will provide an update as soon as we know more. https://status.azure.com/ is not responding currently https://status.insitelms.net/incident/168058 Wed, 25 Jan 2023 08:13:00 -0000 https://status.insitelms.net/incident/168058#04393ea49c2d44f0bb90b35e333f9b009616202c6abd0a05b9e7ad09a5ee894f As of now, the whole MS landscape including Teams, Azure, Office 365 faces major problems. This problem is also affecting us and we will provide an update as soon as we know more. https://status.azure.com/ is not responding currently https://status.insitelms.net/incident/168058 Wed, 25 Jan 2023 08:13:00 -0000 https://status.insitelms.net/incident/168058#04393ea49c2d44f0bb90b35e333f9b009616202c6abd0a05b9e7ad09a5ee894f As of now, the whole MS landscape including Teams, Azure, Office 365 faces major problems. This problem is also affecting us and we will provide an update as soon as we know more. https://status.azure.com/ is not responding currently https://status.insitelms.net/incident/103909 Thu, 21 Jul 2022 04:59:00 -0000 https://status.insitelms.net/incident/103909#0b2da250c07ab1391b01d2d2f5ad9c5f52b568bb798361f402bd0615368815b9 Many Services were down because of a creater Outage of Microsoft Azure in West Europe DataCenter. Therfore also Login to Insite was not possible https://app.azure.com/h/3TFH-PZ0/a66d4e https://status.insitelms.net/incident/103909 Thu, 21 Jul 2022 04:59:00 -0000 https://status.insitelms.net/incident/103909#0b2da250c07ab1391b01d2d2f5ad9c5f52b568bb798361f402bd0615368815b9 Many Services were down because of a creater Outage of Microsoft Azure in West Europe DataCenter. Therfore also Login to Insite was not possible https://app.azure.com/h/3TFH-PZ0/a66d4e https://status.insitelms.net/incident/103909 Thu, 21 Jul 2022 04:59:00 -0000 https://status.insitelms.net/incident/103909#0b2da250c07ab1391b01d2d2f5ad9c5f52b568bb798361f402bd0615368815b9 Many Services were down because of a creater Outage of Microsoft Azure in West Europe DataCenter. Therfore also Login to Insite was not possible https://app.azure.com/h/3TFH-PZ0/a66d4e https://status.insitelms.net/incident/103909 Thu, 21 Jul 2022 04:59:00 -0000 https://status.insitelms.net/incident/103909#0b2da250c07ab1391b01d2d2f5ad9c5f52b568bb798361f402bd0615368815b9 Many Services were down because of a creater Outage of Microsoft Azure in West Europe DataCenter. Therfore also Login to Insite was not possible https://app.azure.com/h/3TFH-PZ0/a66d4e