LUMASERV logo

Is LUMASERV Down?

Cloud InfrastructureLive status, outages, and incident history

No. LUMASERV is up right now.

Every monitored LUMASERV system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 3m agoLive · every 60s

Know the moment LUMASERV breaks

LUMASERV is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official LUMASERV status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

LUMASERV Status Summary

As of 13:55 UTC on 14 November 2026, LUMASERV is operational. PulsAPI checked LUMASERV's official status page and found 17 of 17 components operational, with no active incidents. The latest incident, "Short packet loss on some internet routes due to upstream emergency maintenance", was on Nov 12, 2026.

Cite as: PulsAPI, “LUMASERV status”, checked 14 November 2026, 13:55 UTC. https://www.pulsapi.com/services/lumaserv

LUMASERV Component Status

The main LUMASERV systems on this page. All 17 are operational right now.

17operational
API components » Cloud API
Operational
API components » docs.nicapi.eu
Operational
API components » NICAPI - Rest [v1]
Operational

14 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking API components » Reseller-Interface [reseller.lumaserv.com], Infrastructure (FRA14, Interxion) » Core Network, Infrastructure (FRA14, Interxion) » DDoS Protection, Infrastructure (FRA14, Interxion) » Power Supply, Managed Services » Backupstorage, Managed Services » CEPH-Storage, Managed Services » Cloud server hosts, Managed Services » Mail Gateway, Managed Services » Managed Web Environments, Registries » DENIC, Registries » EURid, Support Services » Monitoring, and 2 more.

See all of them free

Component statuses may change independently during partial outages.

Recent LUMASERV Outages & Incidents

Incident history from the official LUMASERV status page, including resolution updates.

Short packet loss on some internet routes due to upstream emergency maintenanceResolved Nov 12, 2026Resolved

On November 12 between approx. 09:36 and 09:45 CET, connections to parts of the internet were interrupted or showed packet loss for a few minutes, depending on the route. One of our upstream providers (ZET.NET / AS6204) carried out a short-notice emergency maintenance and took its connection to us offline without first shutting down the routing sessions properly. Our routers needed some time to detect this and to move the traffic to our other upstream providers. Since approx. 09:45 CET all traffic has been running normally via our other upstreams. We are following up with the provider on its maintenance process and are reviewing how to speed up failover on our side.

Service degradation in our Frankfurt cloud environmentResolved Nov 11, 2026 · 8h 33mResolved

This incident has been resolved. --- [2026-11-11T11:13:36.515+01:00] (monitoring) All Services have been recovered, if your service is still unreachable, please contact our support and include your server name. We are currently investigating the root cause and are planning the recovery of the full redundancy. We will give another update when full redundancy is recovered. --- [2026-11-11T10:11:17.638+01:00] (identified) The services that became unreachable after one of our power feeds failed at 08:28 CET are running again. We moved them to other hosts or restarted them on their recovered hosts. Disk access is back to normal. We are now closely monitoring the platform and checking each service for reachability. Some systems may need a little more time until all applications are fully up. If your service is still unreachable, please contact our support and include your server name. We will post the next update no later than 60 minutes from now. --- [2026-11-11T09:37:34.909+01:00] (identified) One of the two power feeds is still down. The data center operator’s technicians are working on it. Current status: Our storage systems are working normally again. Disk access no longer stalls. Full data redundancy is restored. We are now checking and restarting the virtual machines from the servers that are still powered off on other servers. These servers have enough free capacity and working power redundancy. The restarts happen step by step and should take about 10-15 minutes. What this means for you: If your service has been unreachable since 08:28 CET, it will start again automatically during this time. You don’t need to do anything. We will post the next update by 10:15 CET at the latest. --- [2026-11-11T09:20:56.040+01:00] (identified) Since 08:28 CET, one of the two power feeds at our Frankfurt data center has been down. The technicians are on their way to the site. Almost all systems switched over to the second feed without interruption. For a small part of our infrastructure, this failover did not work. We are now connecting these systems to the second feed and bringing them back online. Until their full power redundancy is restored, we will not use them for new workloads. Unfortunately a small part of our storage infrastructure (less than 0.01%) is affected by the redundancy, which can lead to availability issues even with running VM's. We will post an update as soon as the affected systems are back online, and no later than [30] minutes from now. --- [2026-11-11T08:38:15.649+01:00] (investigating) We are currently experiencing service degradation in our cloud environment in Frankfurt. Affected services may be partially unavailable or respond with increased latency. Our team is investigating the cause with high priority. We will post further updates here as soon as we have more information. We apologize for any inconvenience.

Network issues at Frankfurt locationResolved Sep 27, 2026 · 14h 43mResolved

This incident has been resolved. --- [2026-09-28T02:23:21.401+02:00] (monitoring) Since 00:05 UTC, all services in our Frankfurt location are fully reachable again. The cause was the failure of a routing engine in one of our core routers. The redundant routing engine took over automatically. During the switchover, the reachability of our Frankfurt network was affected between approx. 23:52 and 00:05 UTC. The network is currently running stably on the redundant routing engine. We are working on restoring the failed component and are continuing to monitor the situation closely. We will provide a further update once full redundancy has been restored. --- [2026-09-28T02:18:45.801+02:00] (investigating) We are currently experiencing network issues which affect the reachability of our network located in Frankfurt. We will provide updates on this statuspage as soon as possible.

LUMASERV Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a LUMASERV incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live LUMASERV Outage Reports

Problems reported by engineers using LUMASERV. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No LUMASERV problems reported yet.

Something wrong with LUMASERV on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About LUMASERV

LUMASERV's status page at status.lumaserv.com lists 17 components, such as Cloud API, NICAPI - Rest [v1] and Reseller-Interface [reseller.lumaserv.com]. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on LUMASERV's side or yours.

LUMASERV Status FAQ

Is LUMASERV down right now?

The verdict at the top of this page comes from the latest poll of the official LUMASERV status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if LUMASERV is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until LUMASERV recovers.

How do I check LUMASERV uptime history?

PulsAPI tracks LUMASERV uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever LUMASERV changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect LUMASERV outages?

PulsAPI reads the official LUMASERV status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual LUMASERV components?

Yes. PulsAPI monitors 17 individual LUMASERV components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when LUMASERV goes down?

Yes. Create a free account and subscribe to LUMASERV: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with LUMASERV to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot LUMASERV problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor LUMASERV?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so LUMASERV plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track LUMASERV with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services