MNS Status · Incident

Timeline

1. Resolved Fri 30 Oct 2026, 10:55 (+04)

   This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

   MNS Operations

2. Investigating Fri 30 Oct 2026, 10:16 (+04)

   Incident INC-2026-0017 has been re-opened: one or more previously-affected components are no longer operational.

   MNS Operations

3. Resolved Fri 30 Oct 2026, 00:53 (+04)

   This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

   MNS Operations

4. Investigating Fri 30 Oct 2026, 00:16 (+04)

   Incident INC-2026-0017 has been re-opened: one or more previously-affected components are no longer operational.

   MNS Operations

5. Resolved Thu 29 Oct 2026, 21:24 (+04)

   This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

   MNS Operations

6. Investigating Thu 29 Oct 2026, 20:54 (+04)

   Incident INC-2026-0017 has been re-opened: one or more previously-affected components are no longer operational.

   MNS Operations

7. Resolved Thu 29 Oct 2026, 17:28 (+04)

   This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

   MNS Operations

8. Investigating Thu 29 Oct 2026, 16:35 (+04)

   Incident INC-2026-0017 has been re-opened: one or more previously-affected components are no longer operational.

   MNS Operations

9. Resolved Thu 29 Oct 2026, 14:57 (+04)

   This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

   MNS Operations

10. Investigating Thu 29 Oct 2026, 14:25 (+04)

    Incident INC-2026-0017 has been re-opened: one or more previously-affected components are no longer operational.

    MNS Operations

11. Resolved Mon 12 Oct 2026, 09:33 (+04)

    This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

    MNS Operations

12. Investigating Sat 10 Oct 2026, 10:14 (+04)

    Incident INC-2026-0017 has been re-opened: one or more previously-affected components are no longer operational.

    MNS Operations

13. Resolved Thu 8 Oct 2026, 21:38 (+04)

    This incident (INC-2026-0017) has been resolved automatically: all affected components have been operational for the required dwell period.

    MNS Operations

14. Investigating Thu 8 Oct 2026, 21:28 (+04)

    We are investigating an issue affecting 1 component(s). Severity: MAJOR. This incident (INC-2026-0017) was detected automatically and is being monitored.

    MNS Operations

All times are Mauritius time (UTC+04). The offset is printed on every timestamp on this page. Machine-readable ISO-8601 values with the offset are available in /status.json and the Atom feed, so nothing has to be inferred.