Motus Outage History

Motus is up right now

Pingoru has recorded 53 incidents for Motus: 0 in the last 12 months and 0 in the last 90 days.

Source: status.motus.com

53incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AugSepOct0
Share of hours with an open incident, any severity
0%50%100%AugSepOct0%
Pingoru began tracking Motus in August 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 517 (0%)

Incidents, newest first

Critical August 1, 2025 We're experiencing a partial outage that is impacting access to the mobile app and motus.com. 22h 56m Motus.com, Mobile Applications

Started Aug 01, 2025, 02:24 PM UTC· resolved Aug 02, 2025, 01:20 PM UTC

  1. investigating Aug 01, 2025, 02:24 PM UTC

    We are aware of a technical concern and our team is working to resolve it as quickly as possible. We will share live status updates here. Thank you for your patience!

  2. monitoring Aug 02, 2025, 02:33 AM UTC

    We have resolved the problem and are monitoring the our services for errors.

  3. resolved Aug 02, 2025, 01:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 1, 2025 Issues with Mobile Application 2h 2m Mobile Applications

Started Jul 01, 2025, 01:08 PM UTC· resolved Jul 01, 2025, 03:10 PM UTC

  1. investigating Jul 01, 2025, 01:08 PM UTC

    We are currently experiencing issues with our Mobile App. You are able to review and submit your mileage within the Motus Portal. Login into https://www.motus.com. We will share live status updates here. Thank you for your patience!

  2. identified Jul 01, 2025, 02:00 PM UTC

    We are working on restoring service and most users should be able to use the mobile application without errors.

  3. monitoring Jul 01, 2025, 02:54 PM UTC

    We are seeing improvements in available and will continue to monitor the service availability.

  4. resolved Jul 01, 2025, 03:10 PM UTC

    This incident has been resolved.

Read the full incident report →