Urban Sharing Outage History

Urban Sharing is up right now

Urban Sharing had 15 outages in the last 2 years totaling 44m of downtime — averaging 0.6 incidents per month.

There were 15 Urban Sharing outages since October 25, 2024 totaling 44m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.urbansharing.com

Minor October 5, 2026

Disruption in core platform services

Detected by Pingoru
Oct 05, 2026, 10:51 PM UTC
Resolved
Oct 05, 2026, 10:51 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 05, 2026, 10:51 PM UTC

    Type: Incident Duration: 6 hours and 13 minutes Affected Components: UrbanSharing Controller v2, Segway Air Protocol, Omni, Backend Services, Admin Console, Rider API, Fleet API, Auth API, Operations API, MaaS API, Webhook Transmitter, Public Web, GBFS API, MDS API, Smart Stations, Dispatch Console, Crew API, Suggestion Engine, TOMP API Oct 6, 05:04:00 GMT+0 - Resolved - This incident has been resolved. Oct 6, 04:02:00 GMT+0 - Identified - We are continuing to work on a fix for this incident. Oct 6, 01:14:00 GMT+0 - Identified - We have identified the cause and are working on restoring our services. Oct 5, 23:45:00 GMT+0 - Investigating - We are still investigating solutions to remedy the disruption. Oct 5, 22:51:00 GMT+0 - Investigating - Certain core platform services are not responding to requests and failing to maintain availability.

Read the full incident report →

Minor June 24, 2026

System instability

Detected by Pingoru
Jun 24, 2026, 12:59 PM UTC
Resolved
Jun 24, 2026, 01:15 PM UTC
Duration
15m
Affected: Systems (Oslo Bysykkel)Systems (Bergen Bysykkel)Urban Fleet (Backend Services)Systems (Trondheim Bysykkel)Systems (Milan BikeMi)Systems (Verona Bike)Systems (MEVO)Systems (LOVÉLO libre-service)Systems (Tampereen kaupunkipyörät)Systems (London Green Quarter)Systems (Oslo Bysykkel)Systems (BiciPalma)Systems (LOVÉLO libre-service)Systems (Milan bikeMi)Systems (RowerMevo)
Timeline · 2 updates
  1. investigating Jun 24, 2026, 12:59 PM UTC

    We're investigating issues with long running and failed requests across the platform.

  2. resolved Jun 24, 2026, 01:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 3, 2026

Loss of connectivity to Stations

Detected by Pingoru
Jun 03, 2026, 02:30 AM UTC
Resolved
Jun 03, 2026, 02:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 03, 2026, 02:30 AM UTC

    Type: Incident Duration: 7 hours and 20 minutes Affected Components: Smart Stations, Oslo Bysykkel Jun 3, 02:30:00 GMT+0 - Identified - A small subset of stations in Oslo has lost connectivity. Our network partner is actively working on a resolution. Jun 3, 09:50:02 GMT+0 - Resolved - This incident has been resolved by our partner.

Read the full incident report →

Major May 7, 2026

System unavailability

Detected by Pingoru
May 07, 2026, 06:55 AM UTC
Resolved
May 07, 2026, 07:00 AM UTC
Duration
4m
Affected: Systems (Oslo Bysykkel)Systems (Bergen Bysykkel)Urban Crew (Dispatch Console)Urban Fleet (Backend Services)Urban Crew (Crew API)Systems (Trondheim Bysykkel)Systems (Milan BikeMi)Urban Crew (Suggestion Engine)Systems (Verona Bike)Systems (MEVO)Systems (LOVÉLO libre-service)Systems (Tampereen kaupunkipyörät)Systems (London Green Quarter)
Timeline · 2 updates
  1. investigating May 07, 2026, 06:55 AM UTC

    We are currently investigating slow or failing requests across the system.

  2. resolved May 07, 2026, 07:00 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 30, 2026

System Unavailability

Detected by Pingoru
Apr 30, 2026, 07:20 AM UTC
Resolved
Apr 30, 2026, 07:45 AM UTC
Duration
24m
Affected: Systems (Oslo Bysykkel)Systems (Bergen Bysykkel)Urban Crew (Dispatch Console)Urban Fleet (Backend Services)Urban Crew (Crew API)Systems (Trondheim Bysykkel)Systems (Milan BikeMi)Urban Crew (Suggestion Engine)Systems (Verona Bike)Urban Fleet (Operations API)Systems (MEVO)Systems (LOVÉLO libre-service)Systems (Tampereen kaupunkipyörät)Systems (London Green Quarter)Urban Crew (Crew Analytics API)
Timeline · 2 updates
  1. investigating Apr 30, 2026, 07:20 AM UTC

    We are currently investigating slow or failing requests across the system.

  2. resolved Apr 30, 2026, 07:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Major December 28, 2025

Segway/Omni connectivity outage

Detected by Pingoru
Dec 28, 2025, 06:30 PM UTC
Resolved
Dec 28, 2025, 06:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 28, 2025, 06:30 PM UTC

    Type: Incident Duration: 2 days and 23 hours Affected Components: Segway Air Protocol, Omni, MEVO Dec 28, 18:30:00 GMT+0 - Monitoring - There are connectivity problems on the side of local network provider and a majority of Segway bikes, and a smaller amount of Omni, are offline. We are continuing to monitor and investigate. Dec 28, 21:15:00 GMT+0 - Monitoring - Most connections have been restored. There are still some unresponsive devices. Dec 31, 17:30:00 GMT+0 - Resolved - Remaining devices are now online.

Read the full incident report →

Minor July 3, 2025

Connectivity issue with Segway/Omni iot

Detected by Pingoru
Jul 03, 2025, 04:30 AM UTC
Resolved
Jul 03, 2025, 04:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jul 03, 2025, 04:30 AM UTC

    Type: Incident Duration: 4 hours and 55 minutes Affected Components: Segway Air Protocol, Omni, MEVO, Tampereen kaupunkipyörät Jul 3, 09:25:00 GMT+0 - Resolved - This incident has been resolved. Jul 3, 04:30:00 GMT+0 - Identified - An outage with the network provider is causing issues communicating with Segway and Omni iot controllers.

Read the full incident report →

Major June 13, 2025

Public websites unavailable due to certificate issue

Detected by Pingoru
Jun 13, 2025, 12:24 PM UTC
Resolved
Jun 13, 2025, 12:24 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 13, 2025, 12:24 PM UTC

    Type: Incident Duration: 28 minutes Affected Components: Payment Services, LOVÉLO libre-service, Public Web, Oslo Bysykkel, Bergen Bysykkel, Trondheim Bysykkel, Milan BikeMi, Verona Bike, MEVO, London Green Quarter Jun 13, 12:52:15 GMT+0 - Resolved - This incident has been resolved. Jun 13, 12:24:23 GMT+0 - Identified - Automatic refresh of SSL certificates for public websites have failed and websites are unavailable due to expired certificates. We are working on restoring access.

Read the full incident report →

Minor June 12, 2025

Communication issues with UrbanSharing Controller v2 iot's

Detected by Pingoru
Jun 12, 2025, 06:00 PM UTC
Resolved
Jun 12, 2025, 06:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 12, 2025, 06:00 PM UTC

    Type: Incident Duration: 1 hour and 30 minutes Affected Components: Bergen Bysykkel, Trondheim Bysykkel, UrbanSharing Controller v2 Jun 12, 19:30:00 GMT+0 - Resolved - This incident has been resolved. Jun 12, 18:45:00 GMT+0 - Monitoring - We've implemented a workaround which fixes most controller communications. The system-provider incident is still ongoing, and some instability and slowness should still be expected, but general operation has resumed. Jun 12, 18:00:00 GMT+0 - Identified - An incident with our system-provider is causing communication issues with vehicles of the UrbanSharing Controller type. Affects Bergen and Trondheim systems. We're awaiting resolution, and investigating internal workarounds in the meantime.

Read the full incident report →

Major June 11, 2025

Partial outage of network communication

Detected by Pingoru
Jun 11, 2025, 07:00 AM UTC
Resolved
Jun 11, 2025, 07:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 11, 2025, 07:00 AM UTC

    Type: Incident Duration: 6 hours and 30 minutes Affected Components: Segway Air Protocol, Omni, MEVO, LOVÉLO libre-service, Tampereen kaupunkipyörät Jun 11, 13:30:00 GMT+0 - Resolved - This incident has been resolved by the network operator. Jun 11, 07:00:00 GMT+0 - Investigating - We are currently investigating communication problems with Omni and Segway iot controllers

Read the full incident report →

Minor May 15, 2025

Impaired communication between IOT bridges and Core systems

Detected by Pingoru
May 15, 2025, 10:00 PM UTC
Resolved
May 15, 2025, 10:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved May 15, 2025, 10:00 PM UTC

    Type: Incident Duration: 15 hours and 31 minutes Affected Components: Pashley TD, Segway Air Protocol, Tampereen kaupunkipyörät, Backend Services, LINKA IoT, Omni, Oslo Bysykkel, MEVO, LOVÉLO libre-service, London Green Quarter May 16, 13:31:20 GMT+0 - Resolved - The issue looks to be resolved. There are still some vehicles with old state that need to be updated. May 16, 11:00:00 GMT+0 - Monitoring - A fix has been implemented and we're monitoring for further issues. May 15, 22:00:00 GMT+0 - Investigating - We are currently investigating an issue affecting around 10% of traffic between iot bridge components and core backend systems, causing vehicle states to not update promptly and correctly.

Read the full incident report →

Minor March 24, 2025

Connectivity problems with Segway/Omni bikes

Detected by Pingoru
Mar 24, 2025, 08:09 PM UTC
Resolved
Mar 24, 2025, 08:09 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 24, 2025, 08:09 PM UTC

    Type: Incident Duration: 10 hours and 58 minutes Affected Components: Segway Air Protocol, Omni, MEVO, LOVÉLO libre-service Mar 25, 07:08:00 GMT+0 - Resolved - This incident has been resolved. Partner network provider in Gdansk has resolved the connectivity. Mar 24, 20:09:50 GMT+0 - Investigating - We are currently investigating connectivity problems with Segway and Omni IOT's. Affects mainly MEVO, Gdansk.

Read the full incident report →

Minor January 10, 2025

Some Omni controllers are unresponsive

Detected by Pingoru
Jan 10, 2025, 02:00 PM UTC
Resolved
Jan 10, 2025, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Jan 10, 2025, 02:00 PM UTC

    Type: Incident Duration: 2 hours and 3 minutes Affected Components: Omni, LOVÉLO libre-service Jan 10, 16:20:00 GMT+0 - Resolved - This incident has been resolved. Jan 10, 14:51:51 GMT+0 - Identified - Confirmed local outage with connectivity provider. Awaiting fix. Jan 10, 14:00:00 GMT+0 - Investigating - We have received reports of around 200 Omni locks being unresponsive and are investigating. Currently signs point towards network connectivity issues.

Read the full incident report →

Major December 11, 2024

Vehicle connectivity outage

Detected by Pingoru
Dec 11, 2024, 09:45 AM UTC
Resolved
Dec 11, 2024, 09:45 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 11, 2024, 09:45 AM UTC

    Type: Incident Duration: 1 day Affected Components: Segway Air Protocol, Omni, MEVO Dec 12, 09:45:00 GMT+0 - Resolved - We consider this resolved from our view, however some vehicles are still unresponsive and recovering. Dec 11, 14:19:36 GMT+0 - Monitoring - Majority (90%) of Segway E-Bikes are back online. Mechanical Omni bikes are still largely unresponsive (70% unresponsive). Dec 11, 11:26:52 GMT+0 - Monitoring - Connectivity looks to be slowly re-establishing, with around 55% vehicles back online, and rising. Dec 11, 09:45:00 GMT+0 - Investigating - We are currently investigating a drop in connectivity with some vehicles, leading to lock and unlock commands failing. Signs currently point towards network provider issues.

Read the full incident report →

Major October 25, 2024

Telit VPN outage

Detected by Pingoru
Oct 25, 2024, 12:03 PM UTC
Resolved
Oct 25, 2024, 12:03 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 25, 2024, 12:03 PM UTC

    Type: Incident Duration: 3 hours and 12 minutes Affected Components: Segway Air Protocol, Omni, MEVO, LOVÉLO libre-service, Tampereen kaupunkipyörät Oct 25, 15:15:00 GMT+0 - Resolved - This incident has been resolved. Telit has restored connectivity and vehicles should start coming back online. Oct 25, 12:03:00 GMT+0 - Identified - Telit VPN is having an outage, affecting vehicle communications with some controllers. Affects Omni and Segway bikes.

Read the full incident report →