Lofenta

Lofenta Status

All systems operational

This page is served from a separate process so it stays up even when the main app is not.

Showing the last 24 hours. Hover any bucket for details.

24h7d30d90d1y

Platform

Lofenta
71msOperational
24h ago12hnow
24 hours uptime 100.00%
EddyLofenta's built-in AI assistant.
Operational
AnthropicClaude. Powers Eddy's premium tier.
Operational
OpenAIOpenAI models are off while we finish billing setup on our OpenAI account. Anthropic and the free tier are unaffected.
Disabled

Runtime Nodes

Edge
Operational8ms
24h ago12hnow
24 hours uptime 100.00%
edge-1
2msOperational
24h ago12hnow
24 hours uptime 100.00%
edge-2
3msOperational
24h ago12hnow
24 hours uptime 100.00%
edge-3
18msOperational
24h ago12hnow
24 hours uptime 100.00%
Netherlands
Operational16ms
24h ago12hnow
24 hours uptime 100.00%
Amsterdam
16msOperational
24h ago12hnow
24 hours uptime 100.00%

Incident history

Full history →

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.

Probes run every 60 seconds. A bucket is marked disrupted only when there are 2+ failed probes within it.