Incidents | Netgraph Connetivity Platform (SE) Incidents reported on status page for Netgraph Connetivity Platform (SE) https://status.se.netgraph-connect.com/ https://d1lppblt9t2x15.cloudfront.net/logos/36c91139565c0ef9dec2a7c0e0132ca6.png Incidents | Netgraph Connetivity Platform (SE) https://status.se.netgraph-connect.com/ en Captive Portal Service Degradation affecting a subset of customers. https://status.se.netgraph-connect.com/incident/851163 Tue, 17 Mar 2026 09:06:00 -0000 https://status.se.netgraph-connect.com/incident/851163#1f7eeebd4dbd8dd7a18989629d74757269ce768fc3486fb53e90b98592282030 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.se.netgraph-connect.com/incident/851163 Mon, 16 Mar 2026 20:05:00 -0000 https://status.se.netgraph-connect.com/incident/851163#66799ba049f7c67a97921382fa83597201187fa8b6072f9cdbaf2bbe3fd21f46 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) https://status.se.netgraph-connect.com/incident/828671 Thu, 19 Feb 2026 13:15:00 -0000 https://status.se.netgraph-connect.com/incident/828671#850eccb9262a56b44cf9af1f2b53003024400467f16f502525179c1a85ff2827 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) https://status.se.netgraph-connect.com/incident/828671 Thu, 19 Feb 2026 06:45:00 -0000 https://status.se.netgraph-connect.com/incident/828671#24e4191eb1b044db589fa888dc41a92c1d9141fe184728d9721a754c8e857486 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.se.netgraph-connect.com/incident/828683 Wed, 18 Feb 2026 21:15:00 -0000 https://status.se.netgraph-connect.com/incident/828683#b08265afb56a7ac1a22e452d82fb0e2735c7e60ee9cfd09b55cbc655737009c8 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.se.netgraph-connect.com/incident/828683 Wed, 18 Feb 2026 09:15:00 -0000 https://status.se.netgraph-connect.com/incident/828683#6fb37478a59f11230a1be0942810188376854320f1965f16002557d273004d04 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.