Zero Networks incident

Portal Performance Degradation

Minor Resolved View vendor source →

Zero Networks experienced a minor incident on April 4, 2025 affecting Portal Access and Assets Monitoring and 1 more component, lasting 3h 59m. The incident has been resolved; the full update timeline is below.

Started
Apr 04, 2025, 08:01 PM UTC
Resolved
Apr 05, 2025, 12:01 AM UTC
Duration
3h 59m
Detected by Pingoru
Apr 04, 2025, 08:01 PM UTC

Affected components

Portal AccessAssets MonitoringMFA

Update timeline

  1. investigating Apr 04, 2025, 08:01 PM UTC

    We are currently experiencing some instabilities with the Zero Networks Portal, which may be impacting asset connectivity and user authentication. Our team is actively investigating the issue. We will keep you updated as soon as we have more information.

  2. investigating Apr 04, 2025, 09:08 PM UTC

    The issue is still under investigation. Our team is continuing to work on identifying the root cause and will keep you informed as we make progress.

  3. investigating Apr 04, 2025, 10:38 PM UTC

    The issue has now been stabilized, and assets should be successfully connected to the segment server. We are continuing to closely monitor the situation and are still investigating the root cause to prevent future occurrences.

  4. investigating Apr 04, 2025, 11:05 PM UTC

    We are continuing to investigate this issue.

  5. investigating Apr 04, 2025, 11:21 PM UTC

    MFA and portal access are now back to normal. Asset connections are currently stable. However, in the event of a large reconnection, such as following a segment server reboot, you may experience a slight delay in asset reconnections. We’ll continue to monitor the situation closely and keep you informed of any relevant updates.

  6. monitoring Apr 04, 2025, 11:33 PM UTC

    A fix has been implemented, and we are actively monitoring the service performance. Asset connections should now resume quickly, including during reconnection events. A full Root Cause Analysis will be shared in the coming days. Thank you for your patience and understanding.

  7. resolved Apr 05, 2025, 12:01 AM UTC

    This incident has been resolved.