LIKE MAGIC Outage History

LIKE MAGIC is up right now

LIKE MAGIC had 8 outages in the last 2 years totaling 37h 56m of downtime — averaging 0.3 incidents per month.

There were 8 LIKE MAGIC outages since June 13, 2025 totaling 37h 56m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.likemagic.tech

Minor March 17, 2026

Task Due Notifications Unavailable

Detected by Pingoru
Mar 17, 2026, 05:28 AM UTC
Resolved
Mar 17, 2026, 08:33 AM UTC
Duration
3h 4m
Affected: Backoffice
Timeline · 3 updates
  1. investigating Mar 17, 2026, 05:28 AM UTC

    Task due notifications are currently not being sent from Backoffice. Users will not receive reminders for upcoming or overdue tasks. All other Backoffice functionality remains operational, including task creation, viewing and management. We are actively investigating and working to restore notifications.

  2. monitoring Mar 17, 2026, 07:39 AM UTC

    A fix has been deployed and task due notifications are working again. We are monitoring to ensure stability.

  3. resolved Mar 17, 2026, 08:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical December 5, 2025

Mews Outage

Detected by Pingoru
Dec 05, 2025, 09:05 AM UTC
Resolved
Dec 05, 2025, 12:22 PM UTC
Duration
3h 16m
Affected: Mews
Timeline · 4 updates
  1. identified Dec 05, 2025, 09:05 AM UTC

    https://status.mews.com/

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

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

  3. monitoring Dec 05, 2025, 09:38 AM UTC

    Seams Cloudflare has fixed their issue

  4. resolved Dec 05, 2025, 12:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical November 20, 2025

Elevated Häfele API Errors

Detected by Pingoru
Nov 20, 2025, 05:57 PM UTC
Resolved
Nov 21, 2025, 01:32 PM UTC
Duration
19h 34m
Affected: Häfele
Timeline · 6 updates
  1. investigating Nov 20, 2025, 05:57 PM UTC

    We're experiencing an elevated level of API errors against Häfele and have informed them.

  2. investigating Nov 21, 2025, 04:40 AM UTC

    We continue to see a high level of errors from Häfele

  3. identified Nov 21, 2025, 09:06 AM UTC

    A fix is in place and its currently monitored to see if this resolves the issues

  4. monitoring Nov 21, 2025, 09:14 AM UTC

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

  5. monitoring Nov 21, 2025, 09:20 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Nov 21, 2025, 01:32 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 14, 2025

Elevated Häfele Errors

Detected by Pingoru
Nov 14, 2025, 02:42 PM UTC
Resolved
Nov 14, 2025, 04:29 PM UTC
Duration
1h 47m
Affected: Häfele
Timeline · 3 updates
  1. investigating Nov 14, 2025, 02:42 PM UTC

    We're experiencing an elevated level of Häfele errors and have informed Häfele to look into it. Possible impact: - Door opening not working - Encoding of key cards

  2. monitoring Nov 14, 2025, 03:07 PM UTC

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

  3. resolved Nov 14, 2025, 04:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 1, 2025

Post-Incident Update

Detected by Pingoru
Oct 01, 2025, 01:08 PM UTC
Resolved
Oct 01, 2025, 01:58 PM UTC
Duration
49m
Affected: Guest JourneyApaleoBackoffice
Timeline · 2 updates
  1. investigating Oct 01, 2025, 01:08 PM UTC

    The incident at apaleo (https://status.apaleo.com/) has been resolved. Our connection is stable again, and we are currently processing the backlog of events from the past 3 hours. During this catch-up phase, you may experience some delays until all queued events are fully processed. We expect the system to return to normal shortly, and we will confirm once processing is fully up to date.

  2. resolved Oct 01, 2025, 01:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 1, 2025

Apaleo not available

Detected by Pingoru
Oct 01, 2025, 10:09 AM UTC
Resolved
Oct 01, 2025, 12:16 PM UTC
Duration
2h 6m
Affected: Apaleo
Timeline · 4 updates
  1. investigating Oct 01, 2025, 09:08 AM UTC

    We are currently experiencing an outage with the connection to apaleo. At the moment, no data can be retrieved and no updates can be processed. For live updates on the incident, please refer to the apaleo status page: https://status.apaleo.com. We will provide further information as it becomes available.

  2. investigating Oct 01, 2025, 10:09 AM UTC

    The outage with apaleo is still ongoing. We continue to be unable to retrieve or update any data. You can follow the latest status directly here: https://status.apaleo.com.

  3. monitoring Oct 01, 2025, 11:24 AM UTC

    The connection to apaleo has been restored. Data retrieval and updates are working again. We are continuing to monitor the situation closely to ensure everything remains stable. For reference, you can still check the official status page here: https://status.apaleo.com.

  4. resolved Oct 01, 2025, 12:16 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 16, 2025

Performance Degradation – Database

Detected by Pingoru
Sep 16, 2025, 06:21 PM UTC
Resolved
Sep 17, 2025, 01:03 AM UTC
Duration
6h 42m
Affected: Guest JourneyBackofficeLIKE MAGIC API
Timeline · 2 updates
  1. investigating Sep 16, 2025, 06:21 PM UTC

    We are currently experiencing decreased performance on our database. This may cause slower response times for some users. Our team has identified the cause and is working on remediation to restore normal performance.

  2. resolved Sep 17, 2025, 01:03 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 13, 2025

SaltoKS not working

Detected by Pingoru
Jun 13, 2025, 11:28 AM UTC
Resolved
Jun 13, 2025, 12:03 PM UTC
Duration
35m
Affected: Salto KS
Timeline · 4 updates
  1. investigating Jun 13, 2025, 11:28 AM UTC

    We are currently investigating this issue.

  2. monitoring Jun 13, 2025, 11:51 AM UTC

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

  3. monitoring Jun 13, 2025, 11:51 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved Jun 13, 2025, 12:03 PM UTC

    This incident has been resolved.

Read the full incident report →