Locomote Outage History

Locomote is up right now

Pingoru has recorded 48 incidents for Locomote: 1 in the last 12 months and 0 in the last 90 days.

Source: status.locomote.com

48incidents recorded
1last 12 months
0last 90 days
24 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Locomote in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 520 (0%)

Incidents, newest first

Notice February 26, 2026 In-App Support Chat Temporarily Unavailable 1d

Started Feb 26, 2026, 10:54 PM UTC· resolved Feb 27, 2026, 10:54 PM UTC

  1. resolved Feb 26, 2026, 11:02 PM UTC

    In-App Support Chat Temporarily Unavailable

  2. postmortem Feb 26, 2026, 11:03 PM UTC

    ## What happened? A recent platform update caused our in-app support chat to stop loading for logged-in users. Customers attempting to use the chat widget would not have seen it appear. ## Who was affected? Any logged-in user for companies serviced directly by Webjet Business Travel with live chat support enabled. ## How long was it down? The issue was introduced approximately 11:12 PM AEDT on 26 February and resolved 9:54 AM AEDT on 27 February. ## What did we do? We identified the issue and rolled back the change. The support chat widget is now fully operational. ## Was any data lost? No. No customer data was affected. Chat history and account information remain intact. ## What if I need help? If you were unable to reach us via chat during this window and still need assistance, please contact our support team directly via the live chat widget.

Read the full incident report →

Major March 18, 2025 Workflow loading issue 1h 32m Travel Management Platform

Started Mar 18, 2025, 09:59 PM UTC· resolved Mar 18, 2025, 11:31 PM UTC

  1. identified Mar 18, 2025, 09:59 PM UTC

    The issue has been identified and a fix is being worked on.

  2. identified Mar 18, 2025, 10:14 PM UTC

    Workflow loading issue has been resolved. We're investigating a secondary issue with reporting access for admins.

  3. monitoring Mar 18, 2025, 11:31 PM UTC

    Reporting auth issue is now also resolved, we are monitoring for any further issues.

  4. resolved Mar 19, 2025, 12:02 AM UTC

    Reporting auth issue is now also resolved, we are monitoring for any further issues.

  5. postmortem Mar 20, 2025, 02:01 PM UTC

    We apologise for any disruption this caused by our recent partial outage, which affected workflow and report loading. The root cause of the issue was preparatory work recently put in place for planned future upgrades, which revealed a configuration mismatch between our production and development/test environments that allowed this issue to bypass both manual and automated testing. We’ve since adjusted our test environments to align with the production configuration in question, and confirmed the issue is now correctly caught in automated tests. We are confident this class of problem is now remediated.

Read the full incident report →