Home
Services
DNSNET

DNSNET dns-net.de Live · Operational

Is DNSNET down right now? Live status and outage tracker

No, DNSNET is up.

No outage detected, and no user reports in the last hour.

Reports, last hour: 0
Usual at this hour: Almost none
Vs the hour before: –

User reports, last 24 hours, one bar per 15 minutes. Dashed line: the usual level. 96 normal · 0 elevated · 0 outage

Not working for you?

Last spike 12 h ago · Updated 2 min ago · Data refreshes every 5 minutes

01 · User reports

0 reports in the last hour

From a public outage-reporting feed, counted in 15-minute windows. The verdict above is based on these.

Last 24 hours

DNSNET outages and problems

User reports, last 24 hours

74 reports in total, counted in 15-minute windows

No problem reports came in for DNSNET in the last hour, and at this time of day there are usually almost none. Over the last 24 hours there were 74 reports. The last spike in reports was 12 h ago and lasted 17 min. These are user reports from Germany, where most people report DNSNET problems.

NormalClose to the usual level24 h · 74 reports
ElevatedMore than 1.5 times the usual levelNone in this chart
OutageMore than twice the usual level and far above the day's averageNone in this chart
Usual levelWhat a usual day sees at that timeAlmost none at this time of day

Reports, last hour

Quiet

Uptime, 24 h

100.00%

No outage windows

Last outage

None

In the last 24 hours

Busiest 15 minutes

8 reports, 12 h ago

DNSNET status card: No, DNSNET is up. User reports over the last 24 hours. — **Share this status**The picture people see when this page is shared: the answer and the last 24 hours of reports.
Image

In the past 24 hours, 74 user reports came in for DNSNET. Counting only the 15-minute windows with a spike big enough to count as an outage, that comes to 100.00% uptime for the day.

The busiest 15-minute window had 8 reports, about 12 hours ago. That stays below our outage threshold, so it doesn't count as downtime.

No problems detected in the last 24 hoursReports for DNSNET stayed at their usual level the whole time.

This month

DNSNET in November 2026

Problem reports in November (since 4 November): 75

Monthly report for November 2026

People who report a problem with DNSNET to the outage-report feed behind this page can tag what is affected. These are the categories they can pick; the feed shows no counts per category:

Email
Landline internet
Billing
Wi-Fi
Internet Zuhause über 5G/LTE

Last 30 days

DNSNET problem spikes, last 30 days

Since 4 November, DNSNET had no outage spikes, but 1 period of elevated reports.

Elevated reports

Wed 4 Nov, 14:25–14:42

Lasted 17 min

11peak reports

A spike is a sharp rise in problem reports from users, kept exactly as this page showed it at the time. This history starts on 4 November 2026. Monthly reports for all services

Troubleshooting

How to fix DNSNET not working

DNSNET is up on our end, so if it won't work for you, the problem is most likely on your side. Work through these in order:

Your browser tries to reach dns-net.de over your own connection, right now. Nothing is sent to us or stored.

Refresh the DNSNET connection
On the affected phone or laptop, turn Wi-Fi off, wait 10 seconds, turn it on, and reconnect to your DNSNET network name. On Windows 11 use Settings > Network & internet > Wi-Fi; on iPhone use Settings > Wi-Fi.
Power cycle the fiber gear
Unplug power from the router and, if you have a separate fiber ONT, unplug that too. Wait 30 seconds. If there is a separate ONT, power it before the router and test again after 5 minutes.
Test past wireless
Connect one computer to the router with an Ethernet cable and switch off that computer's Wi-Fi. On Windows 11, right-click Start, choose Terminal, and run ping 1.1.1.1; on macOS, open Applications > Utilities > Terminal and run ping -c 4 1.1.1.1. If the ping works but websites still do not open by name, run nslookup dns-net.de.
Check the FRITZ!Box log
If your line uses a FRITZ!Box, open http://fritz.box and sign in. Check Internet > Online-Monitor for the connection state, then System > Ereignisse for entries about PPPoE or the physical line; do not change access data unless support tells you to.

While DNSNET is down: what to use instead

Mobile hotspot Use your phone’s data connection for email, banking, or work tasks if your fixed connection is out.
Telekom A Telekom SIM or a second fixed line can keep you online when DNSNET is unavailable at home.
Vodafone Vodafone cable, DSL, or mobile data can work as a backup if you already have access to it.
O2 An O2 mobile plan or hotspot can cover basic browsing and messaging until the service works again.

Same time

Problems at the same time as DNSNET

Since 4 November, DNSNET's only spike in problem reports overlapped a spike at another service.

When several services get problem reports at once, something they share, such as a cloud host or a network, can be the real cause. Matching times alone do not prove it.

During the latest spike

DNSNET: Wed 4 Nov, 14:25 to 14:42

60 more services. Red dot: outage. Amber dot: elevated reports.

A spike is a sharp rise in problem reports from users, as the live pages showed it. Times are Central European time.

About

What happens when DNSNET goes down

DNSNET is a German telecom provider with fixed internet and phone service over regional fiber and broadband networks, mainly used by households and businesses in parts of eastern Germany.

Fixed internet is the first thing most people notice: the router may stay synced but pages time out, downloads stall, video calls freeze, or Wi-Fi shows no usable internet. Phone service over the same connection can fail as well, so outgoing calls do not connect and incoming calls may ring nowhere. If TV is part of the package, live channels may buffer or the receiver may show no stream, while other household devices still see the local Wi-Fi. A fiber cut, power issue, routing fault, or equipment failure can hit one town or access network while another area keeps working.

Servers and network

DNSNET IP address, servers and network

Checking dns-net.de from our server…

Questions

DNSNET FAQ

Is DNSNET down right now?

The status at the top of this page shows whether reports for DNSNET are above their usual level, counted in 15 minute windows over the last 24 hours. Users send those reports to a public outage reporting service, and this site does not monitor the provider or collect reports itself. To tell if the problem is only on your side, test one device on Wi-Fi and one by cable, check the router or fiber modem lights, then compare with mobile data.

My DNSNET Glasfaser connection has no internet. What can I try first?

Check the power and link lights on the router and the fiber terminal, because a dark link light points to the line or the terminal. Reseat the Ethernet cable between the terminal and router, but avoid bending or unplugging the thin fiber lead unless support tells you to. If two devices fail on cable and Wi-Fi after a reboot, contact the provider and include the service address.

Why is my DNSNET landline phone dead even though the router is on?

The phone service usually depends on the broadband connection, so a line fault can take voice calls with it. Check that the handset is registered to the router or plugged into the phone port, then restart the router once. If internet works but calls still fail on another handset, report it as a telephony fault.

Can a DNSNET internet fault break the TV service too?

If your TV package runs through the same home connection, picture freezes and channel loading problems can follow the broadband fault. Test a wired device near the router, because weak Wi-Fi can look like a TV service issue. When web pages and TV fail together, treat it as a connection outage.

Why does the DNSNET availability check reject my address?

The rollout is address based, so a nearby connected street does not prove that your building is ready. Check the spelling, house number suffix, and municipality on dns-net.de. If the address is missing, ask the landlord or property manager whether a building agreement exists.

Official channels

Contact DNSNET support

Tip: DNSNET doesn't list a public status page that we know of, so its help centre and the report chart on this page are the best places to check.

For your site

Put the DNSNET status badge on your site

Paste one of these into a web page, a blog post or a README. The badge shows the same status as this page, based on user problem reports. Browsers can keep a copy for up to 4 hours. It links back here.

HTML

<a href="https://isitdownrightnow.app/services/dns-net/"><img src="https://isitdownrightnow.app/badge/dns-net.svg" alt="DNSNET status" height="20"></a>

Markdown, for README files

[![DNSNET status](https://isitdownrightnow.app/badge/dns-net.svg)](https://isitdownrightnow.app/services/dns-net/)

The badge is a plain image: no scripts, no cookies. People who see it on your page load it from our server.

How we track DNSNET

The status on this page comes from user-submitted problem reports for DNSNET, counted in 15-minute windows over the last 24 hours. Each window is compared with the normal level for DNSNET, so a few complaints on a quiet day don't trigger anything, but a sudden jump well above normal does.

When reports climb well above normal, the status here changes to partial outage or major outage and the chart moves with it. DNSNET doesn't publish a public status page that we know of, so user reports are often the quickest sign that something is wrong on their side.