INVERS Outage History

INVERS is up right now

Pingoru has recorded 48 incidents for INVERS: 38 in the last 12 months and 2 in the last 90 days.

Source: status.invers.com

48incidents recorded
38last 12 months
2last 90 days
3 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking INVERS 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 202611 of 720 (0%)
May 2026316 of 744 (2%)
June 2026211 of 720 (2%)
July 202622 of 744 (0%)
August 202615 of 744 (1%)
September 202611 of 720 (0%)
October 202600 of 533 (0%)

Incidents, newest first

Minor September 2, 2026 General issues (Increased request failure rate) 1h 11m CloudBoxx REST API (Classic), Login, FleetControl, OneAPI REST API and 7 more

Started Sep 02, 2026, 11:22 AM UTC· resolved Sep 02, 2026, 12:33 PM UTC

  1. investigating Sep 02, 2026, 11:22 AM UTC

    We are currently experiencing issues with our services. Our incident response team is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. investigating Sep 02, 2026, 11:27 AM UTC

    Some services are expecting a higher failure rate than usual (20%), meaning ~80% of requests are unaffected. Retries can resolve temporary issues. This also affects event transmission which can lead to events being slightly delayed.

  3. investigating Sep 02, 2026, 11:34 AM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 02, 2026, 11:55 AM UTC

    Our partners were able to determine the source of the error, and both they and INVERS are working with all available teams to resolve the issue.

  5. investigating Sep 02, 2026, 12:13 PM UTC

    The root cause has been traced to a connectivity issue at our hosting provider. Their engineering team has identified the affected area and is actively working to restore full functionality. INVERS teams remain in close coordination with them to accelerate the fix. As previously noted, the impact is limited — roughly 80% of requests continue to process normally, and retries resolve most temporary failures. Delayed event transmission remains the main secondary effect.

  6. identified Sep 02, 2026, 12:14 PM UTC

    The issue has been identified and a fix is being implemented.

  7. monitoring Sep 02, 2026, 12:16 PM UTC

    Failure rate and event transmission has recovered.

  8. monitoring Sep 02, 2026, 12:17 PM UTC

    We are continuing to monitor for any further issues.

  9. resolved Sep 02, 2026, 12:33 PM UTC

    The incident has been resolved. Failure rate and event transmission is back to normal and stable.

  10. postmortem Sep 16, 2026, 07:51 AM UTC

    The incident report \(post mortem\) is available from [https://help.invers.com/incident-reports/](https://help.invers.com/incident-reports/).

Read the full incident report →

Notice August 27, 2026 API issues detected 5h 14m CloudBoxx REST API (Classic), CloudBoxx 1020 (LTE-M / 2G), OneAPI REST API, CloudBoxx 4G (LTE / 2G) and 1 more

Started Aug 27, 2026, 07:21 AM UTC· resolved Aug 27, 2026, 12:36 PM UTC

  1. monitoring Aug 27, 2026, 07:21 AM UTC

    Our monitoring detected issues from 06:58–07:08 UTC. The situation has recovered and the investigation is ongoing.

  2. monitoring Aug 27, 2026, 07:49 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Aug 27, 2026, 12:36 PM UTC

    This incident has been resolved. A detailed post-incident report will follow shortly.

  4. postmortem Aug 31, 2026, 09:02 AM UTC

    The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Minor July 23, 2026 OneAPI and Insights Events (RabbitMQ) issues 19m OneAPI Event Consumers, Anomaly Detection, Driving Analysis

Started Jul 23, 2026, 01:02 AM UTC· resolved Jul 23, 2026, 01:21 AM UTC

  1. identified Jul 23, 2026, 01:02 AM UTC

    We are currently experiencing issues with our OneAPI and Insights Events Message Queue. Our incident response team is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. monitoring Jul 23, 2026, 01:15 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 23, 2026, 01:21 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 16, 2026 General issues 2h 2m CloudBoxx REST API (Classic), Login, FleetControl, OneAPI REST API and 7 more

Started Jul 16, 2026, 04:55 PM UTC· resolved Jul 16, 2026, 06:57 PM UTC

  1. identified Jul 16, 2026, 04:55 PM UTC

    We are currently experiencing issues with our services. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. monitoring Jul 16, 2026, 05:10 PM UTC

    Communication issues between our Datacenters have been resolved everything is back to normal. We keep monitoring the situation.

  3. resolved Jul 16, 2026, 06:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 29, 2026 Monitoring cellular connectivity issues with provider Orange in France only 3h 20m CloudBoxx 4G (LTE / 2G)

Started Jun 29, 2026, 07:55 AM UTC· resolved Jun 29, 2026, 11:15 AM UTC

  1. investigating Jun 29, 2026, 07:55 AM UTC

    We received reports of cellular connectivity issues. Our partner confirmed that there is an issue on some data sessions. The 24/7 teams of INVERS and the partner are working on it, we post new updates once available.

  2. investigating Jun 29, 2026, 08:22 AM UTC

    The mobile carrier Orange is working on a solution, and the relevant teams remain involved.

  3. identified Jun 29, 2026, 09:12 AM UTC

    The values are back to near-standard performance. This issue affected, and continues to affect, only older CloudBoxx 4G devices in France.

  4. monitoring Jun 29, 2026, 09:38 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. monitoring Jun 29, 2026, 09:47 AM UTC

    The issue with Orange in France has been resolved; we are keeping the status at "monitoring" for now and will continue to monitor whether the service remains stable. Most devices were not noticeably affected because they switched to alternative mobile networks in France.

  6. resolved Jun 29, 2026, 11:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 18, 2026 Service Restrictions with the Mobile Carrier “Orange” in France 7h 40m CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started Jun 18, 2026, 07:13 AM UTC· resolved Jun 18, 2026, 02:53 PM UTC

  1. investigating Jun 18, 2026, 07:13 AM UTC

    The relevant internal INVERS teams and those of the connectivity provider are already looking into the issue and are working together to find a solution. This affects only 3G and 4G devices in France.

  2. investigating Jun 18, 2026, 08:43 AM UTC

    Our Carrier Partner is actively investigating the issue. We are closely coordinating with them and continuously monitoring the situation.

  3. investigating Jun 18, 2026, 10:56 AM UTC

    Our Carrier Partner continues to actively investigate the issue. We are closely coordinating with them and monitoring the situation.

  4. identified Jun 18, 2026, 12:47 PM UTC

    The issue has been identified and a fix is being implemented.

  5. monitoring Jun 18, 2026, 01:52 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. monitoring Jun 18, 2026, 01:55 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Jun 18, 2026, 02:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 28, 2026 Monitoring cellular connectivity issues 2h 26m CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started May 28, 2026, 08:46 AM UTC· resolved May 28, 2026, 11:12 AM UTC

  1. investigating May 28, 2026, 08:46 AM UTC

    We received reports of cellular connectivity issues. Our partner confirmed that there is an issue on some data sessions. The 24/7 teams of INVERS and the partner are working on it, we post new updates once available.

  2. identified May 28, 2026, 08:53 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 28, 2026, 08:56 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. monitoring May 28, 2026, 09:16 AM UTC

    The systems remain stable; if this continues, we will close the incident in about 30 minutes.

  5. resolved May 28, 2026, 11:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Major May 19, 2026 Cellular connectivity issues 13h 6m CloudBoxx 1020 (LTE-M / 2G), CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started May 19, 2026, 06:55 PM UTC· resolved May 20, 2026, 08:01 AM UTC

  1. investigating May 19, 2026, 06:55 PM UTC

    We currently experience cellular connectivity issues. We are investigating.

  2. investigating May 19, 2026, 07:06 PM UTC

    We currently experience cellular connectivity issues with one of our providers. All CloudBoxxes connected via this provider are affected.

  3. investigating May 19, 2026, 07:25 PM UTC

    We are seeing improvements regarding the communication success rate. We will keep monitoring the connectivity metrics.

  4. identified May 19, 2026, 08:22 PM UTC

    Due to scheduled maintenance at a connectivity provider, all devices connected to that provider have been switched over to the alternative connectivity provider. There were brief interruptions during the switchover process. The situation has since stabilized, and the emergency teams and the connectivity team are working on the remaining unstable units.

  5. identified May 19, 2026, 08:52 PM UTC

    The situation regarding the remaining units continues to stabilize.

  6. identified May 19, 2026, 09:37 PM UTC

    It's taking longer for the remaining units to reconnect, but our teams are still on top of the situation

  7. monitoring May 19, 2026, 10:03 PM UTC

    The metrics are almost back to normal levels. The teams will continue to monitor the metrics and mark this incident as resolved if it remains stable over the next few hours.

  8. monitoring May 19, 2026, 10:05 PM UTC

    We are continuing to monitor for any further issues.

  9. resolved May 20, 2026, 08:01 AM UTC

    This incident has been resolved.

  10. postmortem May 26, 2026, 07:38 AM UTC

    The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Minor May 12, 2026 Adding vehicles and setup problems 26m CloudBoxx REST API (Classic), OneAPI REST API, SmartControl

Started May 12, 2026, 11:54 AM UTC· resolved May 12, 2026, 12:20 PM UTC

  1. investigating May 12, 2026, 11:54 AM UTC

    Setups are currently not being processed

  2. monitoring May 12, 2026, 11:59 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 12, 2026, 12:20 PM UTC

    This incident has been resolved

Read the full incident report →

Minor April 14, 2026 FleetControl issues: Delayed event processing for some vehicles 31m FleetControl

Started Apr 14, 2026, 02:53 PM UTC· resolved Apr 14, 2026, 03:24 PM UTC

  1. monitoring Apr 14, 2026, 02:53 PM UTC

    We are experiencing an issue regarding event processing for FleetControl. For some vehicles the event log is not up-to-date and doesn't display the most recent events. We have identified the issue and implemented a fix. The event log is catching up.

  2. resolved Apr 14, 2026, 03:24 PM UTC

    Event processing is all caught up and the FleetControl event log displays the most recent events for all vehicles again.

Read the full incident report →

Minor March 16, 2026 [ONLY BELGIUM] Connectivity issues with Proximus Belgium 2h 40m CloudBoxx 1020 (LTE-M / 2G), CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started Mar 16, 2026, 12:10 PM UTC· resolved Mar 16, 2026, 02:50 PM UTC

  1. identified Mar 16, 2026, 12:10 PM UTC

    We are currently experiencing issues with Proximus Belgium. CloudBoxxes should change network so impact should be minimal.

  2. identified Mar 16, 2026, 12:10 PM UTC

    We are currently experiencing issues with Proximus Belgium. CloudBoxxes should change network so impact should be minimal.

  3. identified Mar 16, 2026, 01:42 PM UTC

    Most CloudBoxxes switched network. We are working on a solution with our SIM provider.

  4. resolved Mar 16, 2026, 02:50 PM UTC

    Our devices connected to alternative networks.

Read the full incident report →

Notice March 10, 2026 Monitoring cellular connectivity issues on some CloudBoxx 4G devices 2h 33m CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started Mar 10, 2026, 04:27 PM UTC· resolved Mar 10, 2026, 07:01 PM UTC

  1. investigating Mar 10, 2026, 04:27 PM UTC

    We are seeing problems with some mobile connections in our graphs. This has been confirmed by the connectivity provider, who is working on a solution. We will post updates here when there is any news.

  2. identified Mar 10, 2026, 05:27 PM UTC

    According to feedback from our connectivity providers, the cellular connectivity issues are currently due to ongoing maintenance at a partner, which was initially announced without any expected impact. The pattern of restrictions we see in the log files matches the way maintenance is carried out. We will check how long this maintenance is planned to last and post an update here.

  3. monitoring Mar 10, 2026, 05:49 PM UTC

    There have been no further incidents for almost an hour. We are now setting the incident to “Monitoring” and will close it if it remains unchanged during the observation period.

  4. resolved Mar 10, 2026, 07:01 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 25, 2026 CloudBoxx 1020 connectivity service degradation 8h 29m CloudBoxx 1020 (LTE-M / 2G)

Started Feb 25, 2026, 10:30 AM UTC· resolved Feb 25, 2026, 07:00 PM UTC

  1. investigating Feb 25, 2026, 11:06 AM UTC

    Our monitoring systems detected a service degradation of CloudBoxx 1020 connectivity. We are investigating with our partners.

  2. investigating Feb 25, 2026, 01:33 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 25, 2026, 03:40 PM UTC

    We are continuing to investigate this issue.

  4. identified Feb 25, 2026, 05:34 PM UTC

    Our connectivity partner has identified a packet loss in the interconnection to our servers. They will switchover the traffic to another route which is part of our geo-redundant setup.

  5. monitoring Feb 25, 2026, 06:20 PM UTC

    The traffic switchover was successful and we are seeing huge improvements in our metrics. We continue monitoring for further issues.

  6. monitoring Feb 25, 2026, 06:32 PM UTC

    All values returned to normal. We continue monitoring.

  7. resolved Feb 25, 2026, 07:00 PM UTC

    No further issues occurred during the monitoring period. We consider this incident as resolved.

Read the full incident report →

Minor February 25, 2026 Cellular connectivity issues in A1 networks (Austria, Slovenia, Croatia and North Macedonia) 53m CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started Feb 25, 2026, 09:54 AM UTC· resolved Feb 25, 2026, 10:48 AM UTC

  1. investigating Feb 25, 2026, 09:54 AM UTC

    Our monitoring system detected cellular connectivity issues in several A1 networks in Austria, Slovenia, Croatia and North Macedonia. We are investigating with our partners.

  2. monitoring Feb 25, 2026, 10:04 AM UTC

    The metrics returned to normal value. We continue monitoring for further issues.

  3. resolved Feb 25, 2026, 10:48 AM UTC

    No further issues occurred during the monitoring period. We consider this incident as resolved.

Read the full incident report →

Notice February 25, 2026 Temporary problems in the network of vodafone.de (only Germany) 6h 34m CloudBoxx 1020 (LTE-M / 2G), CloudBoxx 4G (LTE / 2G), CloudBoxx 3G (3G / 2G)

Started Feb 25, 2026, 12:15 AM UTC· resolved Feb 25, 2026, 06:49 AM UTC

  1. monitoring Feb 25, 2026, 01:04 AM UTC

    There are temporary problems in the above-mentioned provider / country. The CloudBoxx units will log into other available networks. We are monitoring reliability with the specialist teams here and involving our connectivity partners. It only affects this provider in this country.

  2. monitoring Feb 25, 2026, 01:05 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Feb 25, 2026, 06:49 AM UTC

    No further issues occurred during the monitoring period. We consider this incident as resolved.

Read the full incident report →

Minor February 12, 2026 Damage Detection Activation delayed 5h 8m Damage Detection Activation/Deactivation

Started Feb 12, 2026, 01:45 PM UTC· resolved Feb 12, 2026, 06:53 PM UTC

  1. identified Feb 12, 2026, 01:45 PM UTC

    We are currently experiencing a delay for the activation process of Damage Detection. In rare cases these might even fail. We identified the issue and implemented a fix. Our team will process all remaining activations once this is solved.

  2. monitoring Feb 12, 2026, 04:47 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 12, 2026, 06:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026 Monitoring issues with setting up vehicles with the smartcontrol app 30m SmartControl, Damage Detection Activation/Deactivation

Started Feb 11, 2026, 04:03 PM UTC· resolved Feb 11, 2026, 04:33 PM UTC

  1. identified Feb 11, 2026, 04:03 PM UTC

    We are currently analyzing reported cases and investigating whether there is a general problem. We will post here when there are new findings.

  2. monitoring Feb 11, 2026, 04:12 PM UTC

    We can confirm a previous problem with adding vehicles to the fleet using the SmartControl app and with activating and deactivating damage detection modules. A fix has been implemented and we are continuing to monitor the situation.

  3. resolved Feb 11, 2026, 04:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 11, 2026 Cellular connectivity issues in the Netherlands 1h 45m CloudBoxx 1020 (LTE-M / 2G)

Started Feb 11, 2026, 02:53 PM UTC· resolved Feb 11, 2026, 04:39 PM UTC

  1. investigating Feb 11, 2026, 02:53 PM UTC

    We currently experience cellular connectivity issues affecting CloudBoxx 1020 devices in the Netherlands. We are investigating.

  2. identified Feb 11, 2026, 04:06 PM UTC

    The data communication in NL KPN network is degraded. We are temporary blocking this network. The CloudBoxxes will switch to other available networks.

  3. monitoring Feb 11, 2026, 04:25 PM UTC

    Almost all devices switched to other networks and the performance is back to normal values. We continue monitoring.

  4. resolved Feb 11, 2026, 04:39 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 10, 2026 Problems with cellular provider KPN (Only relevant for devices in the Netherlands!) 3h 3m CloudBoxx 1020 (LTE-M / 2G)

Started Feb 10, 2026, 05:15 PM UTC· resolved Feb 10, 2026, 08:19 PM UTC

  1. investigating Feb 10, 2026, 05:15 PM UTC

    There are problems in the Netherlands with the provider KPN. Devices are switching to other networks, which may cause brief interruptions. Our partners have been informed and are looking into this issue. We will close the incident here once everything is working again.

  2. resolved Feb 10, 2026, 08:19 PM UTC

    This incident has been resolved.

Read the full incident report →

Major February 2, 2026 FleetControl login issues 1h 19m FleetControl, OneAPI REST API, OneAPI Event Consumers, SmartControl

Started Feb 02, 2026, 01:07 PM UTC· resolved Feb 02, 2026, 02:27 PM UTC

  1. investigating Feb 02, 2026, 01:07 PM UTC

    We are currently experiencing issues with our FleetControl service. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. investigating Feb 02, 2026, 01:14 PM UTC

    SmartControl is affected as well. We escalated to further teams.

  3. investigating Feb 02, 2026, 01:18 PM UTC

    Our OneAPI is affected as well. Currently all requests fail. We are working on it with highest priority.

  4. investigating Feb 02, 2026, 01:20 PM UTC

    We are continuing to investigate this issue.

  5. investigating Feb 02, 2026, 01:35 PM UTC

    We are still continuing to investigate this issue and will provide an update as soon as we have more information.

  6. investigating Feb 02, 2026, 01:50 PM UTC

    The issue is still under investigation, and our team is actively working toward a resolution. We’ll provide further updates shortly.

  7. identified Feb 02, 2026, 01:58 PM UTC

    A possible root cause has been identified, and our team is currently investigating further.

  8. monitoring Feb 02, 2026, 01:59 PM UTC

    All of our systems are functional again and we keep monitoring them.

  9. monitoring Feb 02, 2026, 02:08 PM UTC

    The systems are slowly recovering but are not yet fully performing as expected. We are continuing to monitor and work on improvements.

  10. monitoring Feb 02, 2026, 02:16 PM UTC

    All of our systems are now fully operational and we continue to monitor them.

  11. monitoring Feb 02, 2026, 02:19 PM UTC

    We are continuing to monitor for any further issues.

  12. resolved Feb 02, 2026, 02:27 PM UTC

    The systems remain stable and we are closing the incident. We apologize for any inconvenience caused by this incident.

  13. postmortem Feb 06, 2026, 09:55 AM UTC

    The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Notice December 17, 2025 CloudBoxx Events (RabbitMQ) issues (only affects one message queue from one customer) 57m CloudBoxx Events, Trackings, Heartbeats (Classic)

Started Dec 17, 2025, 09:25 AM UTC· resolved Dec 17, 2025, 10:23 AM UTC

  1. investigating Dec 17, 2025, 09:25 AM UTC

    We are currently experiencing issues with our CloudBoxx Events Message Queue. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. identified Dec 17, 2025, 09:32 AM UTC

    It only affects one message queue from one customer, who has been informed; other customers are not affected.

  3. monitoring Dec 17, 2025, 09:37 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Dec 17, 2025, 10:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 13, 2025 Speeding Events Delay 5h 22m OneAPI Event Consumers

Started Dec 13, 2025, 11:44 AM UTC· resolved Dec 13, 2025, 05:07 PM UTC

  1. investigating Dec 13, 2025, 11:44 AM UTC

    We are currently experiencing issues with our OneAPI and Insights Events Message Queue. Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. identified Dec 13, 2025, 11:55 AM UTC

    Speeding Events delivery is delayed due to slow response times from a third party API

  3. monitoring Dec 13, 2025, 02:08 PM UTC

    Speeding Event delay has recovered back to normal. We will continue monitoring for it to remain stable.

  4. resolved Dec 13, 2025, 05:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 5, 2025 Delays in processing support tickets via the ticket system 6m Ticket system

Started Dec 05, 2025, 09:06 AM UTC· resolved Dec 05, 2025, 09:12 AM UTC

  1. identified Dec 05, 2025, 09:06 AM UTC

    There are currently delays in processing support tickets via the ticket system (support.invers.com). Our partner (ticket system provider) has been informed. Support via telephone or direct email is not affected.

  2. monitoring Dec 05, 2025, 09:09 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Dec 05, 2025, 09:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 1, 2025 Cloudboxx (REST API) issues 44m CloudBoxx REST API (Classic), CloudBoxx Events, Trackings, Heartbeats (Classic)

Started Dec 01, 2025, 04:06 PM UTC· resolved Dec 01, 2025, 04:50 PM UTC

  1. investigating Dec 01, 2025, 04:06 PM UTC

    We are currently experiencing issues with our CloudBoxx REST API and CloudBoxx Events (RabbitMQ). Our emergency standby staff is investigating. We’ll post an update with details and scope of the incident as soon as possible.

  2. monitoring Dec 01, 2025, 04:19 PM UTC

    Services have already recovered, we are investigating the incident cause.

  3. resolved Dec 01, 2025, 04:50 PM UTC

    This incident has been resolved.

  4. postmortem Dec 09, 2025, 12:35 PM UTC

    The incident report \(post mortem\) is available from our support team at [[email protected]](mailto:[email protected]).

Read the full incident report →

Minor November 19, 2025 Speeding Detection slower than usual due to upstream service 3h 11m OneAPI Event Consumers

Started Nov 19, 2025, 05:17 PM UTC· resolved Nov 19, 2025, 08:28 PM UTC

  1. investigating Nov 19, 2025, 05:17 PM UTC

    We are currently experiencing degradation of Speeding Detection due to degradation of an external upstream service. We are closely monitoring the situation.

  2. monitoring Nov 19, 2025, 05:23 PM UTC

    We are closely monitoring the situation.

  3. resolved Nov 19, 2025, 08:28 PM UTC

    Systems remain stable, and our metrics are back to normal. We will close this incident.

Read the full incident report →