smapOne Outage History

smapOne is up right now

smapOne had 8 outages in the last 2 years totaling 108h 53m of downtime — averaging 0.3 incidents per month.

There were 8 smapOne outages since June 2, 2025 totaling 108h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.smapone.com

Major May 20, 2026

smapOne platform is partially unavailable

Detected by Pingoru
May 20, 2026, 07:49 AM UTC
Resolved
May 20, 2026, 07:56 AM UTC
Duration
6m
Affected: smapOne Platform
Timeline · 2 updates
  1. investigating May 20, 2026, 07:49 AM UTC

    The smapOne platform has a partial outage. We are working on the solution and we will inform you here as soon as the platform is fully available again.

  2. resolved May 20, 2026, 07:56 AM UTC

    The smapOne platform is still available. We had a small performance spike by deploying a new version.

Read the full incident report →

Major March 6, 2026

Temporary Platform Outage - Resolved

Detected by Pingoru
Mar 06, 2026, 12:22 PM UTC
Resolved
Mar 05, 2026, 07:30 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 06, 2026, 12:22 PM UTC

    Yesterday evening, our platform experienced an outage that resulted in a service disruption of approximately 60 minutes. During this time, the platform was not accessible. In addition, email notifications and webhooks were partially impacted and operated with limitations until approximately 09:00 this morning. The issue has now been fully resolved, and all systems are operating normally again. The root cause was identified as an error in the network configuration of a central system component. Our team has corrected the configuration and taken steps to prevent similar issues in the future. We sincerely apologize for the inconvenience this incident may have caused and appreciate your patience while we worked to restore full service.

Read the full incident report →

Major February 10, 2026

smapOne WebApp is unavailable

Detected by Pingoru
Feb 10, 2026, 05:21 PM UTC
Resolved
Feb 10, 2026, 05:59 PM UTC
Duration
38m
Affected: smapOne Web App
Timeline · 2 updates
  1. investigating Feb 10, 2026, 05:21 PM UTC

    The smapOne webapp has an outage. We are working on the solution and we will inform you here as soon as it is fully available again.

  2. resolved Feb 10, 2026, 05:59 PM UTC

    The smapOne WebApp is available again.

Read the full incident report →

Minor January 5, 2026

Issue by opening from drafts and task in smapOne app

Detected by Pingoru
Jan 05, 2026, 09:58 AM UTC
Resolved
Jan 07, 2026, 10:46 AM UTC
Duration
2d
Affected: smapOne PlatformsmapOne Web App
Timeline · 4 updates
  1. investigating Jan 05, 2026, 09:58 AM UTC

    We are currently experiencing an issue opening drafts and tasks from some smaps in the smapOne app. We are currently investigating the problem and looking for a solution.

  2. identified Jan 05, 2026, 10:39 AM UTC

    The problem has been identified and a bug fix is being developed. A new version of smapOne will be uploaded to the stores later today.

  3. monitoring Jan 05, 2026, 01:35 PM UTC

    The bug fix has been created and the new version has been uploaded to the respective stores. As soon as the version has been successfully checked by the stores, the new versions will be available for download.

  4. resolved Jan 07, 2026, 10:46 AM UTC

    Bugfix is now on all platforms ready for download.

Read the full incident report →

Critical October 29, 2025

smapOne Platform nicht erreichbar

Detected by Pingoru
Oct 29, 2025, 03:58 PM UTC
Resolved
Oct 29, 2025, 09:21 PM UTC
Duration
5h 23m
Affected: smapOne PlatformsmapOne Web App
Timeline · 5 updates
  1. investigating Oct 29, 2025, 03:58 PM UTC

    Derzeit untersuchen wir Meldungen, dass die smapOne Plattform nicht mehr zu erreichen ist. Erste Ergebnisse liefern ebenfalls Informationen, dass Microsoft Azure auch Störungen meldet. Wir untersuchen die Zusammenhänge und halten Sie auf dem Laufenden.

  2. identified Oct 29, 2025, 05:53 PM UTC

    Die Ursache ist ein Fehler in den Microsoft-Systemen. Microsoft ist an einer Lösung dran. Weitere Infos gibt es unter https://azure.status.microsoft/de-de/status

  3. identified Oct 29, 2025, 07:44 PM UTC

    Microsoft ist dabei die Änderungen an ihrer Infrastruktur zurückzurollen und erwartet, dass die Systeme innerhalb der nächsten 3,5 Stunden wieder lauffähig sind. Uns erreichen inzwischen Berichte, dass smapOne von manchen Nutzern wieder erreicht werden kann. Wir informieren, sobald wir mehr wissen oder wieder normal verfügbar sind.

  4. monitoring Oct 29, 2025, 08:44 PM UTC

    Unsere Monitorigdaten deuten darauf hin, dass die smapOne-Umgebung wieder weitestgehend normal erreichbar ist. Die Menge an Anfrage ist wieder in gewohnten Bereich. Selten schlagen noch Anfragen fehl, diese sollten aber bei einem erneuten Versuch funktionieren. Da Microsoft laut ihrer Statuspage den Fehler noch nicht vollständig behoben hat, beobachten wir weiterhin die Situation.

  5. resolved Oct 29, 2025, 09:21 PM UTC

    Der Fehler wurde behoben. Die smapOne steht wieder normal zur Verfügung.

Read the full incident report →

Major September 23, 2025

App issues with code scanner module

Detected by Pingoru
Sep 23, 2025, 07:40 AM UTC
Resolved
Sep 25, 2025, 08:01 AM UTC
Duration
2d
Timeline · 2 updates
  1. investigating Sep 23, 2025, 07:40 AM UTC

    Following a major update to our Code Scanner software, some barcodes are no longer being read correctly. In addition, a few devices are crashing. We are currently working on identifying and fixing the problem.

  2. resolved Sep 25, 2025, 08:01 AM UTC

    Fix for code scanner brick is live in iOS and Android with AppVersion 25.9.22

Read the full incident report →

Major July 15, 2025

Issue by sending data and forwarding tasks

Detected by Pingoru
Jul 15, 2025, 09:00 AM UTC
Resolved
Jul 15, 2025, 09:15 AM UTC
Duration
14m
Affected: smapOne Platform
Timeline · 4 updates
  1. investigating Jul 15, 2025, 09:00 AM UTC

    We've detected issues in sending data and forwarding tasks. We're currently investigating and will solve the issues as soon as possible.

  2. investigating Jul 15, 2025, 09:01 AM UTC

    We've found the issue and will solve it in the next appr. 10 minutes.

  3. identified Jul 15, 2025, 09:02 AM UTC

    We've found the issue and will solve it in the next appr. 10 minutes.

  4. resolved Jul 15, 2025, 09:15 AM UTC

    This incident has been resolved.

Read the full incident report →