Skip to main content
Operations · Dental IT Support · Internet outage playbook

Dental Office Internet Is Down: What to Check, Who to Call and How to Keep Working

The schedule will not load, the card terminal is spinning and someone at the front desk has asked whether the phones are working too. Patients are in the chairs. Before anyone restarts a box, the useful question is what has actually stopped, because one dead workstation, a carrier outage and a cloud vendor having a bad morning look almost the same from the front desk.

This guide is written for the office manager who has to run the day while technicians investigate. It needs no administrator access and asks for no changes to the network. The first half is for the outage in front of you: how to tell which of three routes you are on, what to do in the first fifteen minutes and who to call. The second half is for the week after: backup internet options for a dental office, why internet failover sometimes fails and how to test it with a short drill your team can record. Patient-care decisions stay with your clinical team and your practice's own downtime procedure; everything here concerns the technology and the communication around it.

In this guide
  1. Start by identifying the scope of the outage
  2. Is it our network, the internet provider or a cloud vendor?
  3. What should a dental office do in the first 15 minutes of an internet outage?
  4. Check visible status without changing the environment
  5. Contact IT and the internet provider with one shared account of the incident
  6. Keep patient-hour communication coordinated
  7. What keeps working when the dental office internet goes down?
  8. Use a backup connection only if the practice has an approved plan
  9. What are the backup internet options for a dental office?
  10. How does internet failover work, and why can it still fail?
  11. Verify recovery with a workflow checklist
  12. Close the incident with one prevention decision
  13. How do you test internet failover without disrupting patients?
  14. Put the outage checklist where staff can find it
  15. Internet outage handoff checklist
  16. What to ask your IT provider about internet outages
  17. Get help with an outage or a backup internet plan
  18. Frequently asked questions
  19. Conclusion

Dental Office Internet Outage Guide

  1. 1Observe the scope
  2. 2Contact the owner
  3. 3Verify the workflow

Start by identifying the scope of the outage

Describe the observation before deciding the cause. "All front-desk computers cannot open two unrelated websites" gives IT more useful information than "the router is broken." Staff do not need to diagnose a firewall, a DNS service or an internet circuit. They need to report a consistent pattern, with times, so the person investigating can rule causes in or out quickly.

Check with a colleague using another approved practice computer. Ask whether the same task fails there. If a second device works, note whether it uses a wired connection or Wi-Fi. Do not connect an unfamiliar personal device to the clinical network simply to conduct a test; it adds a new variable and a new security question in the middle of an incident.

Compare the same task on more than one device

Use a normal, non-sensitive task such as loading the practice website or another familiar public page. A cached page can appear even when the connection is unavailable, so one successful page is not conclusive; try a second site you have not opened today. Tell IT which tasks were tested and when. If the issue affects only one application, record its exact error and whether other online services remain available.

Microsoft's Windows connectivity guidance distinguishes device, connection and application symptoms. In a managed dental environment, let your provider decide which corrective steps are appropriate; consumer reset instructions can alter settings that clinical systems, imaging bridges and printers rely on.

What you observeWhat it helps IT investigateUseful detail to report
One workstation fails; a nearby workstation worksDevice, cable, wireless connection or local configurationRoom, device label, wired or Wi-Fi, exact task
Wi-Fi devices fail; wired devices workWireless network or access-point pathAreas affected and network name, without its password
Several devices cannot use outside servicesShared network equipment, name resolution or internet circuitFirst failure time and which services are affected
Only one cloud application failsApplication, vendor service, account or specific connection pathProduct, error, affected users and other working services
Internet browsing works but local imaging does notLocal server, permissions, imaging bridge or device connectionRoom, image workflow and local application behavior
Everything slows at the same time each day, then recoversBandwidth, a scheduled backup or update, or a carrier fault under loadTimes it starts and stops, and what the office was doing

These are investigation paths, not diagnoses. Multiple faults can happen together. If imaging alone is affected, the dental imaging integration troubleshooting guide is a more relevant next read than continuing to treat the problem as an internet outage. If the pattern is recurring slowness rather than a full outage, the guide to common dental IT problems and their fixes covers the usual causes.

Find your next step

Pick the case below that matches what you saw. Each one ends with a report to IT, not a repair by staff.

One device is affected

Record its room, asset label and connection type. Compare the same normal task on another approved practice device. Report the difference; do not change network settings to test a guess. A single-device fault rarely needs the internet provider, so there is no reason to call the carrier yet.

Several devices or services are affected

Use the agreed outage channel and name one practice contact. Report the first observed time and affected workflows. Ask who owns ISP coordination; do not wait for a full checklist before escalating. An office-wide symptom during patient hours is worth an immediate call, even when the facts are still incomplete.

Only one application is affected

Record the product and exact error, plus other online services that still work. Ask IT to coordinate with the application vendor where needed. This observation does not by itself establish an internet-circuit failure, and it often points to the third route described below: the cloud vendor, not your office.

Is it our network, the internet provider or a cloud vendor?

Most dental office internet outages come down to one of three routes: a fault inside the practice network, an outage at the internet carrier, or a problem at a cloud vendor whose service you rely on. Each has different symptoms, a different first check and a different person to call, and each leaves different things working.

Knowing the route early saves the most time, because it decides who should be on the phone. A carrier will not fix a failed office switch; your IT provider cannot restore a cloud vendor's platform; and a vendor's status page will show green when the problem is in your wiring closet. The table below is the three-route outage plan. Print it with your contact list.

Route 1: our own networkRoute 2: the internet carrierRoute 3: a cloud vendor
Typical symptomSome rooms or devices fail while others work; or nothing inside works, including local printing and imagingEverything inside the office works (local printing, local imaging, a local server), but nothing outside loads on any deviceOne service fails (cloud practice software, email, eRx, a payment portal) while other websites load normally
First check (staff, no changes)Compare wired vs Wi-Fi and room vs room; note any equipment with no lights or a power problemDoes the carrier's outage page or support line report an outage at your address? Does a phone on cellular data, off the office Wi-Fi, reach the carrier's status page?Does the vendor's status page or service-health dashboard show an incident? Do colleagues at another location see the same error?
Who to callYour IT providerYour IT provider first (so one person owns it), then the carrier if your agreement says the practice makes that callYour IT provider, who confirms it is not local, then the vendor's support
What usually keeps workingUnaffected rooms; the internet itself for devices on a working pathSystems that run on a local server (for example an on-premises Open Dental, Dentrix or Eaglesoft setup), local imaging, local printingEverything except the failed service; other cloud tools and the internet in general
What usually stopsWhatever sits behind the failed equipmentCloud practice software, email, VoIP phones that use the same connection, card terminals on the network, insurance portals, remote accessThat service and anything integrated with it
Does backup internet help?Usually not: failover sits at the edge, so an internal fault staysYes, if failover is installed, powered and testedNo: a second connection reaches the same vendor outage

Two notes on the table. First, the "first check" column never asks staff to touch equipment; it asks them to look and compare. Second, the routes can overlap. A storm can cut power to a street cabinet and to your office at once, and a cloud vendor can be slow because your own connection is congested. When the evidence is mixed, say so in the report. "Local printing works, outside websites fail, our cloud schedule shows a vendor error" is the kind of line that helps IT pick the right route quickly.

For cloud services, check the vendor's own status channel before you open a ticket with them. Microsoft, for example, says its service health page lets an administrator "check the service health to determine whether this is a known issue with a resolution in progress before you call support." Most practice-software and phone vendors publish something similar; collect those links now, while the internet works.

What should a dental office do in the first 15 minutes of an internet outage?

In the first fifteen minutes, confirm the scope on two devices, call your IT provider through the agreed outage channel, name one person to coordinate, and switch the front desk to your approved downtime process. Leave equipment alone unless IT asks. Then tell staff what still works and when the next update will come.

That order matters because the most common mistakes in an outage happen early: several people calling the carrier, someone unplugging the wrong box, or the front desk improvising a workaround on a personal phone. A short, fixed sequence avoids all three. Here is one you can adapt.

    1. Minute 0–2: observe. Note the time. Test one ordinary task on two practice devices, one wired if you can. Look at whether local printing and local imaging still work.
    1. Minute 2–5: report. Call your IT provider on the documented outage channel. If that channel depends on the failed connection (a web portal, or office phones that ride the internet), use the alternative you wrote down in advance, such as a mobile phone.
    1. Minute 5: name one coordinator. One person keeps the incident log, talks to IT and gives staff updates. Everyone else reports new symptoms to that person.
    1. Minute 5–10: switch to downtime mode. Pull the printed schedule if you keep one. Use the practice's approved downtime forms for anything you would normally enter online. Hold card payments that cannot complete rather than retrying them repeatedly.
    1. Minute 10–15: first staff update. Confirmed impact, what still works, who is investigating and when the next update is due. "IT is investigating; no restoration time yet" is an acceptable update.

Write the result of each step in the log as you go. Times matter: they let IT match your observations to what its monitoring saw, and they become the raw material for the drill record later in this guide.

Check visible status without changing the environment

Look for simple observations your team can report safely. Does the workstation show a disconnected cable or an unavailable wireless network? Is there a building power issue? Are network devices showing their usual lights? If equipment is in a locked or restricted room, leave access to an authorized person.

Record observations rather than improvising repairs. Avoid factory-reset buttons, moving cables between switch ports, changing Wi-Fi networks, disabling security software or rebooting a server. A change that restores browsing on one computer may disconnect a phone, interrupt an imaging transfer or remove evidence needed to understand the outage.

It helps to know what the boxes are, so you can describe them accurately. A typical small dental office has a chain like this, though every installation differs:

EquipmentWhat it doesWhat staff can safely report
Carrier modem or fiber terminal (ONT)Connects the office to the internet provider; usually owned by the carrierWhether it has power and which lights are on or off (a photo helps)
Firewall or routerJoins the office network to the internet; often where internet failover is configuredWhether it has power; any warning light; do not press buttons
Cellular failover device (if installed)Provides a backup connection over 4G/5GWhether it has power and signal lights; where it sits
Network switchConnects wired workstations, phones, printers and servers inside the officeWhether it has power; whether port lights for affected rooms are dark
Wireless access pointsProvide Wi-Fi in rooms; often powered through the network cableWhich areas lose Wi-Fi
Battery backup (UPS)Keeps network equipment powered through short power cutsWhether it is beeping or showing a fault

If you do not know which box is which, that is a useful finding for the week after: ask IT to label each device with its name and what depends on it.

When a restart may be appropriate

A technician may ask an authorized staff member to restart a specific device. Confirm its label, what it supports, who is affected and the expected sequence first. "Restart the modem" is not enough when several similar boxes sit in a cabinet. Record the action and the time, then report whether the original symptom changed.

Server shutdowns deserve separate handling. The existing dental server shutdown guide explains why an office-wide restart should not become a default response to every connectivity problem.

Contact IT and the internet provider with one shared account of the incident

Use the outage channel agreed with your IT provider. If the normal web portal or office phone depends on the failed connection, use the documented alternative. An existing Legend client can find the client support entry point; a general assessment request is not a substitute for the support procedure in an active incident.

Tell the support team what is affected, when it began, whether patients are currently scheduled and who can be reached through a working channel. Do not wait for a perfect report before escalating an office-wide interruption. Send the initial facts, obtain a ticket reference, and add observations as they become available. Say which of the three routes the evidence points to, and why; it is a hypothesis for IT to test, not a conclusion.

Decide who owns the ISP call

Your agreement may place internet service provider coordination with IT or with the practice. Confirm the owner rather than assuming both parties have called. The ISP may need the service address, account identification and an authorized contact. Share those through the appropriate support channel, not in a public discussion or unsecured worksheet.

Ask for the ISP's incident reference and whether it has confirmed a wider service interruption. Record an estimated restoration time as an estimate, including when it was provided. Do not turn it into a promise to staff or patients. If IT and the ISP disagree about the cause, ask them to compare observations directly and identify the next test owner.

Response, updates and escalation expectations should come from your agreement. Our dental IT support SLA guide explains how those responsibilities differ from a guaranteed repair time.

Keep patient-hour communication coordinated

Choose one practice contact to maintain the incident log and share updates. Staff should report new symptoms to that person or the named ticket owner rather than open several disconnected tickets for the same outage. Individual patient-care decisions remain with the responsible clinical team.

Use a short internal update format: confirmed impact, what still works, current investigation owner and the next update checkpoint. Say "IT is investigating; no restoration time is confirmed" when that is the evidence. Silence often leads different teams to create incompatible workarounds.

For patients, keep it equally plain. A front-desk line such as "Our internet connection is down, so some systems are slower today; your appointment is going ahead" is usually enough. If phones are affected, decide early who will call patients later in the day from a working line and how you will reach them without copying patient lists onto personal devices.

Identify dependencies before promising normal service

Local practice-management functions might continue while online claims, payments, messaging or remote access fail. Other environments rely on an internet connection for most work. Phones may share the same connection. Even a locally hosted application can depend on an online login or integration.

Ask the team to list affected workflows, not just affected computers. Use the practice's approved downtime process for any temporary recording and reconciliation. Do not export patient records to personal email, messaging apps or unmanaged storage to work around the outage.

Legend's dental IT support service overview explains how workstations, software, imaging and networks fit together. That broader picture helps identify who should participate when a single outage crosses several systems.

What keeps working when the dental office internet goes down?

What keeps working depends on where each system runs. Software on a local server, local imaging and local printing often continue during a carrier outage. Cloud practice software, email, internet phones, card terminals on the network, insurance portals, e-prescribing and remote access usually stop. Map your own systems before the next outage.

The map below is a starting point, not a verdict on any product. Two practices with the same software can be set up differently, and many locally installed systems still use online services for some features. Fill in the last column with your IT provider.

WorkflowUsually depends on the internet?WhyYour office (fill in)
Practice software on a local server (for example an on-premises Open Dental, Dentrix or Eaglesoft setup)PartlyThe database is in the office; online features such as patient messaging, online forms, claims and eligibility checks are not
Cloud-hosted practice software (for example Denticon or Curve)YesThe schedule, charts and ledger live with the vendor
Imaging capture and viewing on the local network (DEXIS, Carestream and similar)Usually notSensors and the imaging database are local; cloud sharing or remote viewing is not
Email and Microsoft 365YesHosted online; desktop apps may show cached mail but cannot send
VoIP or cloud phonesUsuallyCalls travel over the internet connection unless the system has another path
Card terminals and online paymentsUsuallyMost terminals authorize online; check whether yours has an offline mode and its limits
Insurance eligibility and claimsYesPayer portals and clearinghouses are online
E-prescribingYesPrescriptions are transmitted online
Remote access and VPN for doctors or billing staffYesThey connect through the office internet connection
Door access, cameras, alarms on the networkVariesSome cloud-managed systems lose remote management but keep working locally

Phones deserve one specific check. The FCC warns that "VoIP service may not work during a power outage or when the internet connection fails or becomes overloaded." If your phones ride the same connection, an internet outage is also a phone outage, and 911 calls from those phones may be affected. How call forwarding, mobile apps and failover routing behave belongs to your phone system's design; the guide to VoIP phone systems for dental offices covers those choices.

Use a backup connection only if the practice has an approved plan

A secondary circuit or cellular connection may help, but its presence does not prove every workflow will function. Capacity, signal, routing, authentication and vendor restrictions can affect what is available. The practice should already know which systems the fallback connection is intended to support.

If an approved failover plan exists, ask IT to confirm whether it has activated and which tasks staff can use. Do not assume that attaching a personal hotspot to an operatory workstation reproduces the practice network. A temporary connection also needs the practice's normal safeguards and technical approval.

For future prevention, use the Dental IT Failure Map to review single points of failure. The network design service page is the appropriate destination for discussing the design of resilient connectivity. Those planning tasks should follow the incident investigation rather than compete with it; the next two sections are for that planning conversation.

What are the backup internet options for a dental office?

A dental office has four practical backup internet options: a second wired connection from a different carrier, a 4G/5G cellular failover device, fixed wireless, and satellite. Each suits a different site and failure. None fixes a fault inside your own network, a power cut without battery backup, or an outage at a cloud vendor.

The right choice depends on what fails most often where you are, how much the office must do on the backup, and what is actually available at your address. The table compares the options on behavior, not price; carrier pricing and packaging change often and vary by address, so get current quotes. One more boundary: backup internet keeps the office connected, while data backup keeps your records recoverable. They are different safeguards, and the dental backup and disaster recovery checklist covers the second.

OptionWhat it suitsHow failover usually behavesWhat it will not fix
Second wired connection from a different carrier (cable, fiber or DSL)Offices that need near-normal capacity on backup: cloud practice software, imaging uploads, many phonesThe firewall switches automatically when it detects the primary has failed; capacity is often close to normalAn outage that hits both carriers at once, such as both lines on the same pole or in the same conduit; a power cut without battery backup
4G/5G cellular failover deviceMost small offices as a first backup; quick to install; physically separate from the cable plantAutomatic through the firewall when set up that way; speed depends on signal inside the building and network load; data plans may cap usageHeavy use (large image uploads, many simultaneous calls); weak indoor signal; a wide-area event that congests local towers
Fixed wirelessSites where a second wired carrier is not available, with line of sight to a provider's antennaAutomatic through the firewall; behaves like a wired line once installedLoss of line of sight; severe weather affecting the antenna; the same power and inside-network limits as the others
SatelliteRemote sites with few other optionsAutomatic through the firewall; higher latency can affect calls and some cloud appsExtreme weather; obstructed sky view; a cloud vendor outage

The FCC's overview of broadband types supports the broad pattern: "Mobile wireless broadband service is typically slower than either wired or fixed wireless alternatives," and satellite speeds depend on "the consumer's line of sight to the orbiting satellite, and the weather," with service that "can be disrupted in extreme weather conditions."

Diversity matters more than the label

A second connection only helps if it fails for different reasons than the first. Ask where each line enters the building and how it reaches the street. Two "different" carriers that share a pole, a trench or a building riser can go down together. Cellular avoids most of that because it does not share the cable plant, which is one reason it is a common first choice for business internet backup.

Decide what the backup must carry

A backup connection rarely needs to carry everything. Agree with your IT provider which workflows get priority on the backup link (typically the cloud practice software if you use one, phones, card payments and eligibility checks) and which can wait (large file transfers, software updates, cloud backup uploads, guest Wi-Fi). That priority list is what lets a modest cellular link keep a front desk working.

A phone hotspot is not a failover plan

A hotspot can keep one person online in an emergency, if your IT provider approves its use. It does not carry the office network, the phone system or the firewall's protections, and it moves practice traffic onto a personal device. Treat it as a last resort written into the plan, not as the plan.

How does internet failover work, and why can it still fail?

Internet failover means the firewall watches the primary connection and moves traffic to a backup when the primary stops working, then moves it back when the primary recovers. It fails most often because it was never tested, the backup equipment lost power, the outage was not detected, or applications did not reconnect.

Failover is usually configured on the firewall or router at the edge of the office network, which is why it cannot help with a fault inside the network (route 1 in the outage plan). The setup itself belongs with the people who design and build your network; the guide on how a dental office network should be set up covers that work. What an office manager can usefully know is the list of reasons failover disappoints, so the right questions get asked.

    • The outage is not detected quickly. The cable can stay physically connected while no traffic gets through. Cisco's documentation for its Meraki MX firewalls, for example, says that in such a "soft failure (where the physical link is still up but provides no internet access)," it "can take approximately five minutes for failover to occur" (Cisco Meraki). Other products behave differently; ask your provider what yours does.
    • The backup equipment has no power. The modem, firewall, switch and cellular device all need power. If only the server is on a battery backup, a short power cut can take the internet down even when the carrier is fine.
    • Applications do not follow. A backup connection usually has a different public address. Services that only accept connections from your office's known address (some vendor portals, remote access, phone systems) may refuse traffic until they are told about the backup.
    • Phones need to re-register. Internet phones may drop active calls during a switch and take a short time to reconnect. Test it with a real call.
    • The backup is too small for the load. If cloud backups, updates and guest Wi-Fi compete with the front desk on a cellular link, everyone gets a slow connection. Traffic priority fixes this.
    • The data plan or subscription has lapsed. A cellular device that has sat unused for a year may have an expired plan or outdated firmware. Monitoring and periodic tests catch this.
    • Nobody notices it has failed over. If the office is quietly running on backup for days, the primary fault goes unreported. Someone should be alerted when failover happens.

Verify recovery with a workflow checklist

An ISP reporting "service restored" is an important signal, but it is not the final practice test. Ask IT when staff can resume verification. Check the workflows that actually failed, including those that depend on third-party services.

WorkflowWhat an authorized staff member confirmsRecord
Practice-management accessThe normal login and required workflow functionPerson, time, pass or issue
Imaging accessThe approved image-viewing or test workflow works in affected roomsRoom and remaining symptoms
Phone serviceApproved inbound and outbound test calls completeResult and affected extensions
Cloud servicesRequired scheduling, communications or billing service respondsProduct and result
Interrupted transactionsResponsible staff check status before retryingOwner and reconciliation status
Failover stateIT confirms the office is back on the primary connection, not still on backupWho confirmed and when

Do not repeatedly submit a payment or claim just to test connectivity. The responsible application user or vendor should first establish whether the interrupted transaction completed. Reconcile any temporary records through the approved workflow so restored access does not leave a second administrative problem.

Keep intermittent issues open long enough to describe them

If the connection works briefly and then fails again, record each occurrence and the tasks affected. "Still intermittent at the front desk after the ISP restoration notice" is useful evidence. Ask the ticket owner what observation period or follow-up checks are appropriate; there is no universal duration that proves every environment stable.

Close the incident with one prevention decision

Request a concise closure record: confirmed cause if known, which of the three routes it was, changes made, verification completed and any unresolved follow-up. If the cause remains uncertain, say so. A guessed root cause can lead the practice to buy equipment that does not address the actual failure.

Choose a specific next action with an owner. It might be testing an existing secondary connection, correcting an outdated ISP contact, documenting which phones depend on the circuit, labelling the network equipment, or improving the outage communication process. Avoid turning the closure meeting into an unrelated technology shopping list.

For the broader support model behind these responsibilities, read the Dental IT Support Complete Guide. If you want Legend to review recurring connectivity disruptions, request a practice IT assessment with the incident history available. Keep patient details out of the initial request.

How do you test internet failover without disrupting patients?

Test failover outside patient hours, or in a quiet hour agreed with IT, by having your provider disconnect the primary connection on purpose while staff check the workflows that matter. Record how long the switch took, what failed and who owns each fix. A short tabletop discussion of the same scenario first catches gaps cheaply.

Two kinds of test are useful, and they answer different questions.

A tabletop drill is a structured conversation: the team walks through a scenario ("the carrier is down at mid-morning on a full day") and says what each person would do. NIST describes tabletop exercises in its guide to test, training and exercise programs, and CISA publishes free tabletop exercise packages with "template exercise objectives, scenarios, and discussion questions." For a dental office, twenty to thirty minutes in a staff meeting is enough to find the missing phone number or the person who did not know where the downtime forms are.

A live failover test is technical: IT pulls the primary connection while staff check the practice software, a test call, a card terminal test mode if your processor offers one, and an eligibility check. It tells you whether the backup actually carries the office.

Planning and testing a contingency plan is also something the HIPAA Security Rule names. The contingency plan standard at 45 CFR 164.308(a)(7) lists an "Emergency mode operation plan (Required)" and "Testing and revision procedures (Addressable)", which it describes as procedures "for periodic testing and revision of contingency plans." How your practice documents this is a question for your compliance lead; NIST's contingency planning guide has templates if you want a structure.

Internet failover drill record

Keep one row per test, tabletop or live. File it with the outage checklist and review it when anything in the chain changes.

FieldWhat to writeExample entry
DateWhen the test ran(date)
TypeTabletop or live failover testLive
ScenarioWhich route was tested and howRoute 2: primary carrier unplugged at the firewall by IT
Who took partCoordinator, IT contact, front desk, clinical leadOffice manager, IT technician, two front-desk staff
Time to failoverFrom disconnection to the practice software working again, as measured(measured minutes)
What workedWorkflows that passed on backupSchedule, card terminal, outbound call
What failedWorkflows that did not, and the symptomRemote access for billing refused the backup address
Owner of each fixOne named person per failureIT contact
Fix confirmedDate the fix was retested(date)
Next testWhen the next test is due(date)

Pick a test schedule that fits the practice, for example each quarter, and add an extra test after any change to the carrier, the firewall, the phone system or the practice software. A failover that last worked two firmware updates ago is a hope, not a plan.

Put the outage checklist where staff can find it

An online guide is useful before an outage, but may be unreachable during one. Print the checklist below, the three-route table and the practice's approved contact list, and keep them with its downtime procedure. Review them when the ISP, phone system, IT provider or office manager changes.

The checklist is a record of observations and coordination. A checked item does not certify that the connection is safe or that every clinical system is ready. The support team and authorized practice staff still need to confirm recovery.

Keep the printed pack short enough to use under pressure: one page for the checklist, one for the three routes, one for contacts (IT provider, carrier account number and support line, phone vendor, practice software vendor, card processor) and the vendors' status-page addresses.

Internet outage handoff checklist

Tick items as you review them. This is a preparation aid, not a certification or a substitute for your practice’s approved process.

  • Record when the issue began and whether it is continuous or intermittent.
  • Compare one affected workstation with a second approved practice device.
  • Note whether local printing and local imaging still work (route 1 or route 2).
  • Check the status page of any single failing cloud service (route 3).
  • List which workflows still work and which have stopped.
  • Record visible network status and any error without patient information.
  • Contact the agreed support channel and record the ticket owner.
  • Confirm who owns the call to the internet provider.
  • Ask IT whether failover has activated and which tasks staff can use.
  • Verify the affected workflows after IT confirms recovery.

What to ask your IT provider about internet outages

These questions are for a calm week, not the outage itself. The answers tell you whether your office is prepared and who owns each part.

    • Which equipment sits between the carrier and our workstations, and is each device labelled with what depends on it?
    • Do we have a backup internet connection? Which type, and does it fail over automatically?
    • When was failover last tested, and can we see the result?
    • Will we be alerted if the office is running on the backup connection?
    • Are the modem, firewall, switch and cellular device on battery backup, and for how long?
    • Which of our systems need the internet (practice software features, phones, card terminals, eligibility, e-prescribing, remote access)?
    • Which services accept connections only from our office's address, and do they also accept the backup?
    • Who calls the internet provider during an outage, you or us? Do you hold our account details?
    • How do we reach you if our phones and internet are both down?
    • What will you record in the closure note after an outage?

Get help with an outage or a backup internet plan

If the internet is down now and you are a Legend client, use your normal support route: the helpdesk staffed 24/7 at 1-800-794-1588, one general number. Have the time it started, what still works and which route you think you are on.

If you are planning ahead, a Free Dental IT Assessment is a good place to raise how your office connects to the internet and whether your backup would carry the front desk. Bring your outage log and any drill records. Request a Free Dental IT Assessment, or call 1-800-794-1588.

About Legend Networking:

    • Served over 3,500 practices since 2004
    • 24/7 monitoring
    • Helpdesk staffed 24/7 at 1-800-794-1588 (one general number)
    • In-house engineers; no outsourced first-level triage
    • Onsite dispatch by appointment across served dental markets; remote-first nationwide
    • Google reviews: 4.8 rating · 173 Google reviews

Legend's operations are led by Ian Lynch: 22 years in dental IT; oversees the NOC, onsite dispatch and client technology roadmaps.

Questions

Frequently asked questions

Why does the computer show Wi-Fi connected but no internet?

Wi-Fi indicates a connection to a wireless network, which can exist without working internet access. The problem may be farther along the connection path, at the firewall, the carrier or a single application. Compare symptoms on another approved device, preferably a wired one, and report what works. Let your IT provider investigate the cause before anyone changes network settings.

Should we restart the router when the dental office internet goes down?

Restart it only when your authorized IT contact or documented procedure calls for that step. Confirm the exact device and its dependencies first, because several similar boxes often share a cabinet. An unplanned restart can interrupt phones, imaging transfers or a failover in progress and complicate diagnosis. Record the action and the time for the support team.

Can we use a phone hotspot to keep the practice working?

Use a hotspot only if it is part of an approved temporary-connectivity plan. It may not reach local systems, carry enough capacity or apply the controls your practice requires, and it moves practice traffic onto a personal device. Ask IT which workflows are permitted and how to reconnect afterward. Avoid moving patient information to personal devices or accounts.

Who should call the internet provider: the office manager or IT?

The owner should be the person designated in your support arrangement. IT may coordinate the call, while the practice supplies account authorization or service details. Agree on one incident owner, keep both ticket references and share confirmed updates. Parallel calls without shared information can make the investigation harder to follow and slow down the answer.

How do we know the outage is actually resolved?

Confirm the affected workflows after the support team reports recovery. Check approved application access, imaging, phones and required online services, review interrupted transactions before retrying them, and ask IT whether the office is back on the primary connection. Record who verified each item and any remaining symptoms. Working browsing alone does not show that every workflow has recovered.

What is the best backup internet for a dental office?

There is no single best option; it depends on your site and what fails there. A second wired line from a different carrier gives the most capacity if it does not share the same pole or conduit. A 4G/5G cellular failover device is a common first choice for small offices. Fixed wireless and satellite suit sites with fewer wired options.

Will our VoIP phones work if the internet goes down?

Often not, if the phones use the same connection. The FCC notes that VoIP service may not work during a power outage or when the internet connection fails or becomes overloaded. Some phone systems can forward calls to mobiles or switch to a backup connection. Ask your provider how yours behaves, and test it with a real call.

How often should we test internet failover?

Set a regular schedule that suits the practice, for example each quarter, and add a test after any change to the carrier, firewall, phone system or practice software. Run it outside patient hours with your IT provider, check the workflows that matter, and record the time to failover, what failed and who owns each fix.

Can we keep seeing patients if our practice software is in the cloud?

Clinically, that is your team's decision under your downtime procedure. Technically, cloud practice software needs a working internet connection, so plan for the gap: keep a printed or offline schedule where your vendor supports it, use approved downtime forms, and consider a backup connection. Ask your vendor what offline options it offers and how records reconcile afterward.

Conclusion

An internet outage becomes easier to manage when the practice reports a clear pattern, works out which route it is on, uses the agreed support channel and keeps one incident owner. Preserve the environment while technicians investigate, use only approved workarounds, and close the incident after affected workflows and interrupted transactions have been checked. Then use the quiet week afterwards: map what depends on the connection, choose a backup that fails for different reasons than the primary, and test it on a schedule you write down.

Ian Lynch
About the author

Ian Lynch

Owner & Operator, Legend Networking

22 years in dental IT. Oversees the NOC, onsite dispatch and client technology roadmaps for practices nationwide.

  • Operations center

    Dallas, Texas

    Serving dental practices nationwide since 2004

  • NOC hours

    24/7 monitoring

    Helpdesk staffed 24/7 at 1-800-794-1588

  • Engineers

    In-house only

    No outsourced first-level dental IT triage

  • Onsite dispatch

    By appointment

    Technicians deployed across served dental markets

About Legend Networking
Your next step

Schedule your free dental IT consultation call

Get clarity on technology, HIPAA compliance, and infrastructure in just 30 minutes.

Or call 1-800-794-1588

Free IT assessment

Tell us what you are running

Your information is secure and will never be shared.