smapOne Outage History

smapOne is up right now

Pingoru has recorded 51 incidents for smapOne: 13 in the last 12 months and 5 in the last 90 days.

Source: status.smapone.com

51incidents recorded
13last 12 months
5last 90 days
4 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct4
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking smapOne 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 202620 of 744 (0%)
June 202610 of 720 (0%)
July 202611 of 744 (0%)
August 202600 of 744 (0%)
September 202610 of 720 (0%)
October 202641 of 510 (0%)

Incidents, newest first

Notice October 21, 2026 Information zur aktuellen PHP-Sicherheitslücke –

Started Oct 21, 2026, 02:00 PM UTC· resolved Oct 21, 2026, 02:00 PM UTC

  1. resolved Oct 21, 2026, 04:26 PM UTC

    Information zur aktuellen PHP-Sicherheitslücke Die smapOne-Plattform ist von den aktuell bekannt gewordenen PHP-Sicherheitslücken nicht betroffen. Der Betrieb unserer Plattform ist uneingeschränkt gewährleistet. Für unsere Kunden besteht kein Handlungsbedarf.

Read the full incident report →

Major October 6, 2026 smapOne platform is partially unavailable 11m smapOne Platform

Started Oct 06, 2026, 07:54 AM UTC· resolved Oct 06, 2026, 08:06 AM UTC

  1. investigating Oct 06, 2026, 07:54 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 Oct 06, 2026, 08:06 AM UTC

    All applications are running again

Read the full incident report →

Minor September 3, 2026 Issue creating new smaps –

Started Sep 03, 2026, 03:30 PM UTC· resolved Sep 03, 2026, 03:30 PM UTC

  1. resolved Sep 07, 2026, 06:07 AM UTC

    From around 5:30 p.m. on Thursday until 9:40 a.m. on Friday, it was difficult to create a smap. The website returned a 404 error, but still allowed smaps to be created via secondary links. After the problem was noticed around 8:15 a.m. on Friday morning, the cause was identified and resolved. As of 9:40 a.m. on Friday, the functionality to create smaps is fully available.

Read the full incident report →

Major July 1, 2026 problems with datasources and databricks 40m smapOne Platform, smapOne Web App

Started Jul 01, 2026, 07:58 AM UTC· resolved Jul 01, 2026, 08:39 AM UTC

  1. investigating Jul 01, 2026, 07:58 AM UTC

    We are currently investigate an issue with our data bricks. There may be problems with updates and synchronisation between data sources.

  2. identified Jul 01, 2026, 08:17 AM UTC

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

  3. monitoring Jul 01, 2026, 08:29 AM UTC

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

  4. resolved Jul 01, 2026, 08:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 24, 2026 Communication between Apps and Backend broken 16m smapOne Web App

Started Jun 24, 2026, 09:07 AM UTC· resolved Jun 24, 2026, 09:24 AM UTC

  1. investigating Jun 24, 2026, 09:07 AM UTC

    We currently see errors in the communication between our Apps and their Backend. This means: - our WebApp is not usable. - Android, iOS and Windows apps work as if they are offline. We are working to find the cause and a solution.

  2. monitoring Jun 24, 2026, 09:17 AM UTC

    We are seeing errors in the network communication between individual Azure regions. The issue appears to have since been resolved by Microsoft.

  3. resolved Jun 24, 2026, 09:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2026 Temporary Platform Outage - Resolved 1h

Started Mar 05, 2026, 07:30 PM UTC· resolved Mar 05, 2026, 08:30 PM UTC

  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 38m smapOne Web App

Started Feb 10, 2026, 05:21 PM UTC· resolved Feb 10, 2026, 05:59 PM UTC

  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 2d smapOne Platform, smapOne Web App

Started Jan 05, 2026, 09:58 AM UTC· resolved Jan 07, 2026, 10:46 AM UTC

  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 5h 23m smapOne Platform, smapOne Web App

Started Oct 29, 2025, 03:58 PM UTC· resolved Oct 29, 2025, 09:21 PM UTC

  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 October 9, 2025 Various timeouts or failed requests 5h 21m smapOne Platform, smapOne Web App

Started Oct 09, 2025, 08:30 AM UTC· resolved Oct 09, 2025, 01:52 PM UTC

  1. investigating Oct 09, 2025, 08:30 AM UTC

    We've investigated currently appearing time outs and connectivity issues. The problem is a general problem with Microsoft Azure. Unfortunately, we are dependend on Microsoft Azure to run our product, so we need to wait for their fix. As long as it takes for Microsoft Azure to fix the issue, you hardly can reach our platform and send new data. We also expect that automated workflows will fail. We will inform you as soon as Microsoft Azure is stable again.

  2. investigating Oct 09, 2025, 09:52 AM UTC

    We are continuing to investigate this issue.

  3. identified Oct 09, 2025, 10:59 AM UTC

    Update from the Microsoft Azure Status Page: https://azure.status.microsoft/en-us/status/ ---- Azure Front Door capacity issue in multiple regions Impact Statement: Starting at 07:40 UTC on 09 October 2025, Azure customers using Azure Front Door (AFD) may experience intermittent delays or timeouts when accessing their services. This includes the ability to access the Azure and Entra Portals. Current Status: Our monitoring detected a significant capacity loss of about 30% of Azure Front Door instances, predominantly across Europe, Middle East, and Africa. We understand that this is due to a dependency on some underlying Kubernetes instances that crashed. We have ruled out any deployments that could have triggered this event. We have been restarting these underlying Kubernetes instances, and AFD instances are coming back online. Customers should start seeing recovery as we bring these instances back online, and we expect full mitigation within the next 90 minutes. ---- So we expect that our platform will be fully reachable again within the next 90 minutes.

  4. resolved Oct 09, 2025, 01:52 PM UTC

    Microsoft Azure has largely resolved the issue. As stated on their website, it is not yet fully stable again. Therefore, there may be occasional problems with the accessibility of our platform. Since we assume general availability and cannot exert any further influence, we are closing the case for now. The latest information on this issue can be found on the Microsoft Azure Status Page: https://azure.status.microsoft/en-us/status/

Read the full incident report →

Major September 23, 2025 App issues with code scanner module 2d

Started Sep 23, 2025, 07:40 AM UTC· resolved Sep 25, 2025, 08:01 AM UTC

  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 14m smapOne Platform

Started Jul 15, 2025, 09:00 AM UTC· resolved Jul 15, 2025, 09:15 AM UTC

  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 →

Major May 8, 2025 smapOne Platform is not available 37m smapOne Platform

Started May 08, 2025, 07:51 AM UTC· resolved May 08, 2025, 08:29 AM UTC

  1. investigating May 08, 2025, 07:51 AM UTC

    We are experiencing a peak load that is making our systems slow. We are currently looking for the source and working on a solution.

  2. monitoring May 08, 2025, 08:20 AM UTC

    We have found the source that has slowed down our systems. We were able to stabilize the platform. We are continuing to monitor the behavior and the stability.

  3. resolved May 08, 2025, 08:29 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 21, 2025 Problems with sending E-Mails and Reports 1h 20m smapOne Platform

Started Feb 21, 2025, 08:42 AM UTC· resolved Feb 21, 2025, 10:03 AM UTC

  1. investigating Feb 21, 2025, 08:42 AM UTC

    We are currently investigate the problems.

  2. investigating Feb 21, 2025, 08:43 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 21, 2025, 08:48 AM UTC

    We are continuing to investigate this issue.

  4. monitoring Feb 21, 2025, 09:49 AM UTC

    We experienced a problem with emails and webhooks triggered from Data records: These notifications were not sent. What Happened? Our last release caused errors concerning tasks that are done in the background. What Have We Done? We rolled back to the version before and requeued all pending emails and webhooks. It will take a while to process all of them. We will inform you, when all are processed. What Should You Do? Please be patient. We will process all outstanding notifications. Contact: You can reach us anytime in the community or contact our support directly via email at [email protected]. We are here to assist you! Thank you once again for your understanding and patience.

  5. resolved Feb 21, 2025, 10:03 AM UTC

    All pending emails and webhooks have been processed. If you experience further issues please contact our support at [email protected]

Read the full incident report →

Minor February 7, 2025 Problem downloading multiple pdf reports via data access link 1h 58m smapOne Platform

Started Feb 07, 2025, 01:16 PM UTC· resolved Feb 07, 2025, 03:15 PM UTC

  1. identified Feb 07, 2025, 01:16 PM UTC

    Who is affected? Everyone who uses external data access links to download of multiple pdf reports for a smap version. Workaround: The Creator of the smap can still download all reports. With the external data access link, each pdf can still be downloaded individually via the detailpage of a data record. We are in the process of solving it as quickly as possible

  2. resolved Feb 07, 2025, 03:15 PM UTC

    This incident has been resolved.

Read the full incident report →

Major January 24, 2025 Various timeouts on some requests 4h 49m smapOne Platform

Started Jan 24, 2025, 10:47 AM UTC· resolved Jan 24, 2025, 03:36 PM UTC

  1. investigating Jan 24, 2025, 10:47 AM UTC

    There are currently various malfunctions such as unreachable pages. We are looking for the cause and are trying to find a quick solution.

  2. resolved Jan 24, 2025, 03:36 PM UTC

    The system has been stable for several hours. The case is closed. We have been following the reports over the last few hours. We suspect external reasons for the few cases of malfunction in the morning.

Read the full incident report →

Minor January 23, 2025 Problem with downloading single pdf reports via preview API routes 3d 21h smapOne Platform

Started Jan 23, 2025, 03:39 PM UTC· resolved Jan 27, 2025, 12:57 PM UTC

  1. identified Jan 23, 2025, 03:39 PM UTC

    Who is affected? Automations that are downloading pdf reports for single data records via preview routes (like /Backend/preview/Smaps/[smapid]/Versions/[version]/Records/[recordid].Pdf) since 20.1.25 from 9:32 am Error behavior: Due to an internal change pdf is not recognized as a valid data record export format. Workaround: use /Backend/intern/Smaps/[smapid]/Versions/[version]/Data/[recordid].Pdf instead We are in the process of solving it as quickly as possible

  2. identified Jan 23, 2025, 03:58 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Jan 27, 2025, 12:57 PM UTC

    The issue has now been fixed, and the preview routes are functioning as expected.

Read the full incident report →

Major December 17, 2024 smapOne Community Forum is unavailable 1d 13h smapLand Community Forum

Started Dec 17, 2024, 07:14 PM UTC· resolved Dec 19, 2024, 08:20 AM UTC

  1. investigating Dec 17, 2024, 07:14 PM UTC

    The smapOne Community Forum 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 Dec 19, 2024, 08:20 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 9, 2024 Problems with file names when downloading reports –

Started Dec 09, 2024, 11:00 AM UTC· resolved Dec 09, 2024, 11:00 AM UTC

  1. resolved Dec 09, 2024, 03:24 PM UTC

    Who is affected? Automations that download reports (pdfs, Word) and were executed in the period from 12:00 -15:20, and where the file name for the reports was taken from the header data of the smapOne platform. Error behavior: Due to a change in the format in which the header data is transferred, the reports may have been saved with the wrong file name. Details: The format of the header was changed from “Content-Disposition”: “inline; filename=>” to “Content-Disposition”: “attachment; filename=>”. The change has been reverted and all downloads work as usual again.

Read the full incident report →

Major November 15, 2024 Emails and WebHooks for Datarecords won't be send 19m smapOne Platform

Started Nov 15, 2024, 12:53 PM UTC· resolved Nov 15, 2024, 01:13 PM UTC

  1. identified Nov 15, 2024, 12:53 PM UTC

    We detected a problem with our background worker for data records at 12:45 p.m.. Therefore, emails for data records won't be triggered as well as webhooks belonging to the respective automations. The problem seems to be live since 10:45 a.m. and is relevant for every data record. The issue will be fixed in 10 minutes. Emails which have queued for the time since the issue will be triggered manually from our side. We will keep you in the loop.

  2. monitoring Nov 15, 2024, 01:02 PM UTC

    The issue has been fixed. Every new data record will be sent as usual or with a short delay due to the amount of waiting emails. The emails from the time of the incident have been triggered again and will now be sent by our system. This may take up to two hours until every email has been sent and web hooks react accordingly.

  3. resolved Nov 15, 2024, 01:13 PM UTC

    The incident had been resolved. All emails from the start of the incident now have been sent. All webhooks will have been triggered as expected. All newly created data records work as usual again.

Read the full incident report →

Notice October 24, 2024 Issue with 3rd party login 54m smapOne Platform

Started Oct 24, 2024, 09:10 AM UTC· resolved Oct 24, 2024, 10:04 AM UTC

  1. identified Oct 24, 2024, 09:10 AM UTC

    We’ve detected an issue for users who registered themselves during the past 23 hours via 3rd party login, meaning using Microsoft login with Entra ID. These users are not able to login currently via Microsoft. All other users registered by 23.10.2024, 11 a.m. and earlier are not affected by this incident. We’re currently working on a fix and are kindly asking for a short amount of patience. We’ll keep you updated.

  2. resolved Oct 24, 2024, 10:04 AM UTC

    The issue has been resolved. Everyone can log in again.

Read the full incident report →