Back to status
Lofenta

Incident history

Every incident, automated or manually filed, with the timeline of updates and the eventual resolution.

Payments now crypto only

major

Lofenta · Sep 14, 2026, 08:37 PM · 54d 19h

Resolved
What happenedCard payments and new subscriptions are temporarily unavailable while we resolve an account matter with our payment provider. Services that are already running are not affected and no action is needed from you. We will confirm here once checkout is back.
ResolutionCard payments have been retired. For privacy reasons, Lofenta now accepts cryptocurrency payments only. Existing services were never affected, and subscriptions and add-ons can be paid in crypto from your dashboard.
  1. InvestigatingSep 14, 2026, 08:37 PM
    Reported. Checkout and new subscriptions are affected while we work with our payment provider.
  2. IdentifiedSep 14, 2026, 08:37 PM
    Cause identified with our payment provider. Existing services keep running normally. We will update this page as soon as payments are restored.
  3. ResolvedNov 8, 2026, 03:03 PM
    Card payments have been retired. For privacy reasons, Lofenta now accepts cryptocurrency payments only. Existing services were never affected, and subscriptions and add-ons can be paid in crypto from your dashboard.

Bacau node offline

critical

Bacau · Aug 18, 2026, 10:38 PM · 29d 4h

Resolved
What happenedOur provider for the Bacau node closed its hosting services. We recovered all data held on that node before the shutdown took effect, so nothing has been lost. Apps that ran on Bacau stay offline until we bring a replacement node online, and we are working on that now.
ResolutionLofenta is running on a new node in Amsterdam provided by our partner TAKEHOST.BIZ. All data was restored from backup and apps are serving again.
  1. InvestigatingAug 18, 2026, 10:43 PM
    Monitoring detected that the Bacau node had stopped responding.
  2. IdentifiedSep 14, 2026, 08:32 PM
    Provider shutdown confirmed. All data from the Bacau node is secured on our side. We are sourcing a replacement node and will post here once it is live and apps are restored.
  3. IdentifiedSep 14, 2026, 08:37 PM
    We have now spoken with the provider directly and they confirmed they will not be continuing to host this node for us. We would like to thank them for hosting us throughout the development of Lofenta. We are looking at options for a replacement node so we can resume service, and we will post the timeline here as soon as it is fixed. We know a lot of you have been waiting for Lofenta to open to everyone, and we are sorry that it will not happen as soon as we hoped. Thank you for your patience while we sort this out.
  4. IdentifiedSep 17, 2026, 01:46 AM
    We have a replacement node online in Amsterdam and we have started migrating the data from Bacau onto it. Apps will come back in batches as their data is restored, and we will confirm here once everything is serving again.
  5. IdentifiedSep 17, 2026, 01:55 AM
    Thanks to our long time partner TAKEHOST.BIZ we have a new node in Amsterdam and Lofenta is reopening. The backup has been copied across and verified, and we are restoring data now. Apps will come back in batches as they are restored, and we will confirm here once everything is serving again.
  6. MonitoringSep 17, 2026, 02:17 AM
    The Amsterdam node is live and the data from Bacau has been restored onto it. Apps are back up and serving, and their databases and files came across intact. A small number still need attention and we are working through those now. We are monitoring everything closely before we call this resolved.
  7. ResolvedSep 17, 2026, 02:49 AM
    Everything is back online. The apps have been restored onto the Amsterdam node and are serving normally, with their databases and files intact. Thank you for your patience while we sorted this out.

Runtime node edge-3 unreachable

major

edge-3 · Nov 7, 2026, 04:19 AM · 8m

Resolved
  1. InvestigatingNov 7, 2026, 04:23 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedNov 7, 2026, 04:28 AM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Nov 3, 2026, 08:44 PM · 19m

Resolved
  1. InvestigatingNov 3, 2026, 08:48 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedNov 3, 2026, 09:04 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Sep 27, 2026, 03:45 AM · 7d 10h

Resolved
  1. InvestigatingSep 27, 2026, 03:49 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedOct 4, 2026, 02:24 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Sep 23, 2026, 05:19 PM · 9m

Resolved
  1. InvestigatingSep 23, 2026, 05:23 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 23, 2026, 05:29 PM
    Automated probe detected sustained recovery.

Runtime node edge-1 unreachable

major

edge-1 · Sep 5, 2026, 08:55 PM · 23m

Resolved
  1. InvestigatingSep 5, 2026, 08:59 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 09:18 PM
    Automated probe detected sustained recovery.

Runtime node edge-2 unreachable

major

edge-2 · Sep 5, 2026, 08:55 PM · 23m

Resolved
  1. InvestigatingSep 5, 2026, 08:59 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 09:18 PM
    Automated probe detected sustained recovery.

Runtime node edge-1 unreachable

major

edge-1 · Sep 5, 2026, 07:23 PM · 23m

Resolved
  1. InvestigatingSep 5, 2026, 07:27 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 07:46 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Sep 5, 2026, 07:17 PM · 8d 20h

Resolved
  1. InvestigatingSep 5, 2026, 07:21 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 14, 2026, 03:59 PM
    Automated probe detected sustained recovery.

Lofenta platform unreachable

critical

Lofenta · Sep 5, 2026, 07:17 PM · 2h 0m

Resolved
  1. InvestigatingSep 5, 2026, 07:21 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 09:17 PM
    Automated probe detected sustained recovery.

Runtime node edge-2 unreachable

major

edge-2 · Sep 5, 2026, 03:04 PM · 4h 16m

Resolved
  1. InvestigatingSep 5, 2026, 03:08 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 07:20 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Sep 5, 2026, 03:04 PM · 28m

Resolved
  1. InvestigatingSep 5, 2026, 03:08 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 03:32 PM
    Automated probe detected sustained recovery.

Runtime node edge-1 unreachable

major

edge-1 · Sep 5, 2026, 03:04 PM · 4h 16m

Resolved
  1. InvestigatingSep 5, 2026, 03:08 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 07:20 PM
    Automated probe detected sustained recovery.

Lofenta platform unreachable

critical

Lofenta · Sep 5, 2026, 03:04 PM · 28m

Resolved
  1. InvestigatingSep 5, 2026, 03:08 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 03:32 PM
    Automated probe detected sustained recovery.

Lofenta platform unreachable

critical

Lofenta · Sep 5, 2026, 08:47 AM · 3h 12m

Resolved
  1. InvestigatingSep 5, 2026, 08:51 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 11:59 AM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Sep 5, 2026, 08:45 AM · 3h 14m

Resolved
  1. InvestigatingSep 5, 2026, 08:49 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedSep 5, 2026, 11:59 AM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Aug 27, 2026, 04:42 PM · 1h 8m

Resolved
  1. InvestigatingAug 27, 2026, 04:47 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedAug 27, 2026, 05:51 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Aug 26, 2026, 10:37 AM · 21m

Resolved
  1. InvestigatingAug 26, 2026, 10:41 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedAug 26, 2026, 10:58 AM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Aug 14, 2026, 08:14 PM · 1h 7m

Resolved
  1. InvestigatingAug 14, 2026, 08:19 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedAug 14, 2026, 09:22 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Aug 9, 2026, 10:11 PM · 9m

Resolved
  1. InvestigatingAug 9, 2026, 10:15 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedAug 9, 2026, 10:21 PM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Aug 7, 2026, 09:02 PM · 2h 19m

Resolved
  1. InvestigatingAug 7, 2026, 09:06 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedAug 7, 2026, 11:21 PM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Jul 30, 2026, 10:52 AM · 15m

Resolved
  1. InvestigatingJul 30, 2026, 10:56 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 30, 2026, 11:07 AM
    Automated probe detected sustained recovery.

Runtime node edge-1 unreachable

major

edge-1 · Jul 28, 2026, 07:27 AM · 8h 26m

Resolved
  1. InvestigatingJul 28, 2026, 07:31 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 28, 2026, 03:53 PM
    Automated probe detected sustained recovery.

Runtime node edge-2 unreachable

major

edge-2 · Jul 28, 2026, 07:27 AM · 8h 26m

Resolved
  1. InvestigatingJul 28, 2026, 07:31 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 28, 2026, 03:53 PM
    Automated probe detected sustained recovery.

Lofenta platform unreachable

critical

Lofenta · Jul 26, 2026, 10:31 PM · 11m

Resolved
  1. InvestigatingJul 26, 2026, 10:35 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 26, 2026, 10:43 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Jul 19, 2026, 03:40 AM · 9m

Resolved
  1. InvestigatingJul 19, 2026, 03:44 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 19, 2026, 03:50 AM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jul 13, 2026, 06:10 PM · 1d 5h

Resolved
What happenedThe Tulcea (Romania) runtime node had been going unreachable on and off because of network instability at that location, and on 13 July it stopped responding for good.
ResolutionWe have removed the Tulcea node from our fleet. Its network had become unreliable, dropping off repeatedly over the past weeks and then staying unreachable, so we chose to retire it rather than keep serving apps from an unstable location. Every project that was running on Tulcea has been moved to a healthy node in the same region. We restored each app and its data from the latest backup, brought the services back up, and repointed the domains to the new node, so your apps are back online and there is nothing you need to redeploy on your side. Automated monitoring for the Tulcea node has been turned off. We are sorry for the interruption, and we are watching node health more closely so we can act sooner next time.
  1. InvestigatingJul 13, 2026, 06:14 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 14, 2026, 11:42 PM
    Resolved. The unstable Tulcea node has been removed. Every affected project was migrated to a healthy node in the same region, restored from its latest backup with its data and domains, and is back online. Monitoring for the retired node is now off.

Runtime node edge-3 unreachable

major

edge-3 · Jul 12, 2026, 05:05 PM · 39m

Resolved
  1. InvestigatingJul 12, 2026, 05:09 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 12, 2026, 05:44 PM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jul 12, 2026, 04:10 PM · 2h 13m

Resolved
  1. InvestigatingJul 12, 2026, 04:14 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 12, 2026, 06:24 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Jul 12, 2026, 02:12 PM · 2h 22m

Resolved
  1. InvestigatingJul 12, 2026, 02:16 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 12, 2026, 04:34 PM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Jul 12, 2026, 12:48 PM · 55m

Resolved
  1. InvestigatingJul 12, 2026, 12:52 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 12, 2026, 01:44 PM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Jul 11, 2026, 05:29 PM · 12m

Resolved
  1. InvestigatingJul 11, 2026, 05:33 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 11, 2026, 05:41 PM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jul 9, 2026, 12:46 AM · 54m

Resolved
  1. InvestigatingJul 9, 2026, 12:50 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 9, 2026, 01:41 AM
    Automated probe detected sustained recovery.

Runtime node edge-3 unreachable

major

edge-3 · Jul 9, 2026, 12:30 AM · 3h 4m

Resolved
  1. InvestigatingJul 9, 2026, 12:34 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 9, 2026, 03:35 AM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jul 8, 2026, 02:03 AM · 18m

Resolved
  1. InvestigatingJul 8, 2026, 02:07 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 8, 2026, 02:22 AM
    Automated probe detected sustained recovery.

Upstream network problems at our Tulcea (RO) location

major

Tulcea (RO) · Jul 6, 2026, 07:27 PM · 5h 17m

Resolved
What happenedOne of our runtime locations, Tulcea (Romania), is losing packets on its upstream provider network. Apps hosted there may load slowly or be intermittently unreachable. The fault is on the provider network, not the apps themselves. We have reported it to the provider and are monitoring.
ResolutionUpstream connectivity recovered on its own and has held steady. We notified the provider (no response) and will keep monitoring the Tulcea region for any recurrence.
  1. InvestigatingJul 6, 2026, 07:27 PM
    We detected upstream network problems at our Tulcea location and are investigating with the provider.
  2. MonitoringJul 7, 2026, 12:45 AM
    Upstream connectivity to the Tulcea region has recovered and stayed stable. We reported the packet loss to the upstream provider and are keeping the region under close watch before we close this out.
  3. ResolvedJul 7, 2026, 12:45 AM
    Connectivity has held steady since recovery, so we are marking this resolved. The provider never confirmed a cause, so we will keep watching Tulcea for any recurrence.

Runtime node edge-3 unreachable

major

edge-3 · Jul 5, 2026, 01:28 PM · 1d 6h

Resolved
  1. InvestigatingJul 5, 2026, 01:32 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 6, 2026, 07:33 PM
    edge-3 is reachable again; the health probe now connects.

Runtime node Tulcea unreachable

major

Tulcea · Jul 5, 2026, 07:13 AM · 8m

Resolved
  1. InvestigatingJul 5, 2026, 07:17 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 5, 2026, 07:22 AM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jul 4, 2026, 02:06 AM · 35m

Resolved
  1. InvestigatingJul 4, 2026, 02:10 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 4, 2026, 02:42 AM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jul 1, 2026, 07:28 AM · 6h 57m

Resolved
  1. InvestigatingJul 1, 2026, 07:32 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJul 1, 2026, 02:25 PM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jun 29, 2026, 10:23 PM · 11m

Resolved
  1. InvestigatingJun 29, 2026, 10:27 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJun 29, 2026, 10:35 PM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jun 29, 2026, 09:28 PM · 15m

Resolved
  1. InvestigatingJun 29, 2026, 09:32 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJun 29, 2026, 09:43 PM
    Automated probe detected sustained recovery.

Runtime node Tulcea unreachable

major

Tulcea · Jun 29, 2026, 12:57 PM · 36m

Resolved
  1. InvestigatingJun 29, 2026, 01:01 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJun 29, 2026, 01:34 PM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Jun 29, 2026, 10:13 AM · 17m

Resolved
What happenedPlanned maintenance. The Bacau node was restarted for a scheduled storage (disk) upgrade. We estimated a 1-2 minute interruption, but it ran to about 17 minutes, longer than planned, and we apologize for that. Projects on the node recovered automatically once it came back.
ResolutionMaintenance completed. The node and all projects on it are back to normal operation.
  1. InvestigatingJun 29, 2026, 10:17 AM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJun 29, 2026, 10:30 AM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Jun 24, 2026, 11:16 PM · 12m

Resolved
What happenedPlanned maintenance. The Bacau node was restarted for a scheduled storage (disk) upgrade. We estimated a 1-2 minute interruption, but it ran to about 12 minutes, longer than planned, and we apologize for that. Projects on the node recovered automatically once it came back.
ResolutionMaintenance completed. The node and all projects on it are back to normal operation.
  1. InvestigatingJun 24, 2026, 11:20 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJun 24, 2026, 11:28 PM
    Automated probe detected sustained recovery.

Runtime node Bacau unreachable

major

Bacau · Jun 23, 2026, 04:12 PM · 11m

Resolved
What happenedThis interruption came from an upstream network issue at our hosting provider (ISP), not from Lofenta or your projects. Connectivity to the Bacau node dropped for about 12 minutes and was restored automatically once the upstream network recovered.
ResolutionConnectivity was restored once the upstream network recovered. No action was needed on projects.
  1. InvestigatingJun 23, 2026, 04:16 PM
    Automated probe detected 5 consecutive failures.
  2. ResolvedJun 23, 2026, 04:23 PM
    Automated probe detected sustained recovery.