Incidents | Netgraph Connectivity Platform (global) Incidents reported on status page for Netgraph Connectivity Platform (global) https://status.netgraph-connect.com/ https://d1lppblt9t2x15.cloudfront.net/logos/72b97b4c1e379b55556b431e6a611fd7.png Incidents | Netgraph Connectivity Platform (global) https://status.netgraph-connect.com/ en Captive Portal Service Degradation affecting a subset of customers. https://status.netgraph-connect.com/incident/851157 Tue, 17 Mar 2026 09:06:00 -0000 https://status.netgraph-connect.com/incident/851157#f04187914ff825c3ceff22969e71d22a750d79817cdfa1b22586b09cae203047 The previously reported degradation affecting a subset of Captive Portal customers has now been resolved. Captive Portal Service Degradation affecting a subset of customers. https://status.netgraph-connect.com/incident/851157 Mon, 16 Mar 2026 20:05:00 -0000 https://status.netgraph-connect.com/incident/851157#6a917eb40d86fc1786807c6cd2e90c2332a781c8e1ed5d2eaee1ed82daf9d966 Our monitoring systems have identified an issue impacting certain Captive Portal environments. The root cause has been identified, and remediation actions are underway. We are working to resolve this as quickly as possible and restore full service stability. SAML Login Issue via Captive Portal (Sign In Service via SG) https://status.netgraph-connect.com/incident/828676 Thu, 19 Feb 2026 13:15:00 -0000 https://status.netgraph-connect.com/incident/828676#f1054925ed2897703e2a44c6356a192a810dfcbbd8b89a7e22efb180c547d4a7 The issue affecting SAML authentication via the Captive Portal in the Sign In service has now been resolved. SAML login through the Service Gateway is fully operational again. Admin Portal and Self-Service Portal were not impacted during the incident. SAML Login Issue via Captive Portal (Sign In Service via SG) https://status.netgraph-connect.com/incident/828676 Thu, 19 Feb 2026 06:45:00 -0000 https://status.netgraph-connect.com/incident/828676#5e30f7e42090332aa45869ca9b35a98cc1cad95d1ade7cfcac17fe3a592076ac We are currently experiencing an issue affecting SAML authentication when logging in through the Captive Portal via the Service Gateway in the Sign In service. This issue does not impact SAML login to the Admin Portal or the Self-Service Portal. Those services remain fully operational. Our engineering team is actively investigating the issue. Further updates will be provided as soon as more information becomes available. Self-Provision Email Login Issue for Microsoft Email Domains (Sign In Service) https://status.netgraph-connect.com/incident/828681 Wed, 18 Feb 2026 21:19:00 -0000 https://status.netgraph-connect.com/incident/828681#d6b1523ce6d19cd60f5f6f1deab6162d0d823c8f71ecbe17f0fb53214d3989ac Yesterday, we experienced email delivery issues affecting the Self-Provision login flow in the Sign In Captive Portal for recipients using Microsoft-hosted email domains (e.g., @outlook.com, @hotmail.com, @live.com, @msn.com). Emails were temporarily rejected with bounce messages referencing sender reputation. Our infrastructure showed no reputation degradation, and monitoring indicated normal sending behavior. The issue appears to have been related to temporary filtering or rate-limiting within Microsoft’s email protection systems. Delivery has since returned to normal, and no further impact is currently observed. We continue to monitor delivery performance closely. Self-Provision Email Login Issue for Microsoft Email Domains (Sign In Service) https://status.netgraph-connect.com/incident/828681 Wed, 18 Feb 2026 09:04:00 -0000 https://status.netgraph-connect.com/incident/828681#9b5163c4e18670bb1769191419c72856fdb584d9f40abd0694f6fdc82aff044d We are currently experiencing an issue affecting Self-Provision login via email in the Captive Portal for users with Microsoft-based email addresses. The issue appears to impact addresses under common Microsoft domains, including but not limited to: @outlook.com @hotmail.com @live.com @msn.com @outlook.se @hotmail.se Users with email addresses from other providers are not affected. Our team is actively investigating the issue. We will provide updates as soon as more information becomes available.