Illustrative network equipment and cabling; not identified as ZTN infrastructure
Practical connectivity guidance

ZTN Technical Support

Guidance and Resources to Help You Stay Connected.

A connection problem becomes easier to explain when you know what is affected, where the failure begins, and which checks are safe to make. Use these educational guides to investigate common symptoms, document what you find, and decide when to seek appropriate technical assistance.

Understand the symptom. Find the next step.
01 / Start here

Welcome to the ZTN Support Center.

This center brings together general internet connection help, basic network troubleshooting, fiber connection information, business connectivity considerations, router and Wi-Fi guidance, explanations of network performance, and answers to frequent technical questions. Begin with the symptom that best matches your situation; you do not need to identify the cause before you start.

Good troubleshooting separates the parts of the experience. A laptop can lose its Wi-Fi connection while the internet service remains available. A router can broadcast Wi-Fi while its connection to the wider internet is unavailable. A particular website can fail even when other online services work. Testing those possibilities one at a time produces more useful evidence than repeatedly changing settings.

These articles are self-help education, not a live diagnosis or a statement of ZTN support availability. Your equipment manual, network administrator, and applicable service information take precedence over general advice here. For questions about your own circumstances, use the ZTN contact page; it provides the available way to make an enquiry. Never assume a particular support channel, service hour, or response time from this guide.

Investigate safelyCheck the observable basics before changing equipment configuration.
Describe clearlyRecord the affected devices, timing, indicators, and comparison tests.
02 / Find your topic

Select your technical support topic.

Choose a starting point below. Each card jumps to a practical section on this page; the guides are general and do not replace instructions for your particular equipment or service.

01 / CONNECTION

Internet Connection Problems

Find out whether the issue affects the device, local network, or wider connection.

Read the guide
02 / SPEED

Slow Internet Speed

Compare test conditions and look for congestion, device, or Wi-Fi constraints.

Read the guide
03 / WIRELESS

Wi-Fi Connectivity

Explore signal strength, placement, interference, bands, and coverage.

Read the guide
04 / OPTICAL

Fiber Internet Issues

Understand ONT indicators and learn which checks are safe to make.

Read the guide
05 / EQUIPMENT

Router and Modem Problems

Review power, ports, DHCP, DNS, heat, and repeated disconnections.

Read the guide
06 / WORKPLACE

Business Internet Connectivity

Scope office-wide problems and protect important workflows.

Read the guide
07 / METRICS

Network Performance

Make sense of bandwidth, latency, jitter, loss, and throughput.

Read the guide
08 / ENDPOINTS

Device Connectivity

Check computers, phones, TVs, consoles, printers, and smart devices.

Read the guide
09 / SAFETY

Network Security Basics

Review safer passwords, updates, access, and remote connections.

Read the guide
10 / ANSWERS

General Technical Questions

Browse 30 explanations of common connectivity questions.

Browse questions
03 / Basic diagnostics

Basic internet connection troubleshooting.

Start with visible, reversible checks. The aim is to establish whether the problem lies with one device, the Wi-Fi network, customer equipment, or a connection beyond the premises.

  1. Describe the symptom. Note whether there is no Wi-Fi name, a Wi-Fi connection without internet, intermittent access, or a single failing application. Write down the approximate start time and any exact error message.
  2. Check power and obvious cables. Confirm the router and any separate modem or ONT have power. Without disturbing optical connectors, look for visibly loose power or Ethernet plugs and damaged leads. Use the equipment manual to identify connections.
  3. Observe indicators. Record which lights are on, off, or flashing. Their meaning differs by manufacturer and model; consult the manual instead of interpreting an unfamiliar color or pattern as a definitive diagnosis.
  4. Compare devices. Try another phone or computer on the same network. If only one device fails, investigate its wireless adapter, settings, VPN, or software before concluding that the entire internet connection has failed.
  5. Compare wired and wireless access. If a suitable Ethernet-capable device and cable are available, compare it with Wi-Fi. A working wired connection alongside failed Wi-Fi points toward a local wireless issue, though it does not by itself identify the cause.
  6. Try more than one destination. Open several unrelated websites or applications. If only one fails, the remote service, its DNS record, or a device-specific application may be responsible.
  7. Restart only when appropriate. Save work first. If you administer the equipment and its manual permits it, use its ordinary power or restart procedure and allow it time to reconnect. Coordinate with others before interrupting a shared office network.
  8. Record what changed. Note which comparisons worked, what the indicators showed, whether the issue returned, and any recent power event or approved configuration change. Those details are more useful than a description of “internet down” alone.

A modem or optical network terminal connects to an access technology; a router connects local devices to other networks and often supplies Wi-Fi. Some products combine these functions. If several devices lose both wired and wireless internet, investigate the shared equipment and service path. If one device alone fails while others work, concentrate on that device. These are diagnostic clues, not proof of a particular provider-side fault.

Avoid factory resets.

A factory reset can remove connection settings, Wi-Fi names, security configuration, and administrator changes. Do not perform one unless your equipment provider or network administrator specifically instructs you to do so and you understand how the configuration will be restored.

04 / Speed and consistency

Troubleshooting slow internet speed.

A slow application experience can be caused by a busy local network, wireless conditions, limited equipment, the destination service, or conditions beyond your premises. Test method matters as much as the number displayed.

Begin by asking what is slow. A large download may be limited by the remote server, while a video meeting may struggle with upload congestion or variable latency. Multiple users, cloud backups, software updates, streaming, and background synchronization can compete for capacity. Router processing limits, an old device, a weak Wi-Fi signal, or a damaged Ethernet cable can also restrict achieved throughput. ISP-side network conditions are another possibility, but a single slow wireless result does not establish where the constraint is.

A practical speed-testing method

  1. Choose a reputable internet speed-testing service and note which server it selects. Keep the same test method when comparing results.
  2. Pause large downloads, uploads, cloud backups, and other known heavy activity where practical. Do not disrupt someone else's critical work without agreement.
  3. Test near the router or access point to reduce the effect of a weak wireless signal. This is a Wi-Fi comparison, not a guaranteed measurement of the access line.
  4. If your equipment and network policy allow, compare with a capable device connected by Ethernet. Use a suitable cable and verify that the wired link is operating normally.
  5. Repeat at different times, including when symptoms occur and when the connection feels normal. Note how many users and applications were active.
  6. Record download rate, upload rate, and latency, together with the date, time, device, connection type, and test server.
  7. When asking for assistance, share the pattern and context rather than only the highest or lowest number.

One result is a snapshot across a particular device, test server, route, and moment. It cannot establish a persistent fault or guarantee future performance. Compare repeated results under comparable conditions, then relate them to the application that actually matters. Ethernet and Wi-Fi can differ because wireless shares radio airtime and is affected by distance and interference; neither single result defines the entire service specification.

Useful comparison:

If a capable wired device is consistently responsive while several wireless devices struggle in distant rooms, investigate Wi-Fi coverage. If both wired and wireless devices struggle at the same times, look for shared traffic and equipment constraints and document the pattern before seeking help.

05 / Wireless coverage

Wi-Fi connectivity troubleshooting.

Wi-Fi is the local radio connection between a device and an access point. It is not the same measurement as the speed or reliability of the internet service feeding that access point.

Start with placement. A router tucked into a cabinet, behind a television, or at one end of a large building may provide uneven coverage. Walls, floors, metal shelving, dense construction, and distance weaken or obstruct the signal. Moving an access point into a more open, central location can improve coverage when cabling and safety permit. Test in several rooms and compare how close and distant locations behave; signal bars are a rough indicator, not a complete performance measurement.

Nearby Wi-Fi networks and other radio devices may compete for airtime. The 2.4 GHz band often reaches farther and works with many devices, but it is commonly congested. The 5 GHz band can offer more available capacity at shorter ranges. Where both the access point and client support it, 6 GHz can provide additional spectrum but generally requires suitable proximity and compatible equipment. Actual performance depends on channel conditions, device capabilities, construction, and configuration; a band name alone does not guarantee a result.

If a network name does not appear, check whether wireless networking is enabled on the router and device, then compare with another device. If authentication fails, carefully verify that the selected network and password are correct; avoid repeatedly sharing the key in messages. If a device connects and then drops, observe whether this occurs only in a weak-signal zone, during movement between access points, or for all clients at once. Device compatibility and router firmware may matter; install updates through the manufacturer's trusted instructions, ideally when you can tolerate a brief interruption.

Practical ways to improve coverage

  • Place access points away from large obstructions and sources of interference, within the manufacturer's operating guidance.
  • Compare the same device near the access point and in the problem area; this helps separate coverage from a general connection issue.
  • Use an appropriate band for each device and location. A more distant device may work more reliably on 2.4 GHz than on a weak 5 GHz connection.
  • If supported, review automatic channel selection or have an administrator assess channel congestion instead of making speculative changes across a managed network.
  • For larger premises, consider additional access points or a properly planned mesh system. Mesh nodes must themselves have a good link; placing one in an existing dead zone rarely helps.
  • Where feasible, wired backhaul connects access points over Ethernet rather than using wireless airtime for the link between them. This can improve consistency, but installation and configuration should suit the site.

When a wired device performs well but Wi-Fi varies strongly by location, concentrate on the wireless design. If both wired and wireless access fail, return to the basic connection sequence. Do not assume that improving Wi-Fi changes the actual internet service capacity; it improves how effectively devices reach that service within the premises.

06 / Optical access

Fiber internet troubleshooting.

Fiber carries data as optical signals. Its customer-side equipment and indicators can offer clues, but their exact interpretation depends on the equipment and network design.

An Optical Network Terminal, or ONT, is customer-premises equipment that terminates a compatible fiber connection and presents a connection for other equipment. In some access-network designs, an Optical Line Terminal, or OLT, sits on the network side and communicates with many ONTs. Not all fiber services use the same architecture. The router, ONT, power supply, optical route, and wider network can each affect whether a device can reach the internet.

Safely confirm that equipment has power and note any visible status indicators. On some equipment, labels such as PON concern the optical network connection and LOS refers to loss of signal. Their colors, flashing patterns, and precise meanings are model-specific: consult the manufacturer's documentation or the instructions supplied for your service. A warning may relate to the optical path, a power or equipment problem, or a network-side interruption. Record the label and behavior rather than guessing from a generic chart.

From a distance, look for obvious damage to accessible cabling without pulling, bending, cleaning, or disconnecting it. Tight bends and damaged connectors can disrupt an optical signal, but attempting a physical repair can create hazards and worsen the fault. If the ONT is powered and an optical warning persists, or fiber appears damaged, stop physical troubleshooting and seek appropriate technical assistance. You can still document whether devices see the Wi-Fi network and whether the router is powered.

Optical-fiber safety warning

Never look directly into an optical fiber connector or laser source. Avoid touching or disconnecting fiber connectors unnecessarily. Physical fiber inspection, cleaning, splicing, or repair should be handled by qualified technicians.

A loss of service is not always a broken fiber. Power interruptions, local router problems, and network-side interruptions can produce similar user-facing symptoms. Share the indicator labels, their observed behavior, and the time the issue started through the applicable assistance route; do not infer ZTN-specific equipment behavior from these general descriptions. Learn about the technology on the Fiber Internet page.

07 / Customer equipment

Router and modem troubleshooting.

A router, modem, ONT, and Wi-Fi access point can be separate devices or combined in one enclosure. Identify what equipment you actually have before interpreting a light or changing a setting.

If a router does not power on, check its normal power connection and whether other devices at the outlet have power; do not open the casing or use an incompatible adapter. If an internet indicator is absent or reports an error, record it and consult the manual. If the Wi-Fi name disappears while Ethernet continues to work, inspect the router's wireless status and compare several devices. If devices see Wi-Fi but cannot join, verify the correct network name and credentials and look for a device-specific authentication error.

Frequent disconnections can stem from unstable power, overheating, Wi-Fi interference, an overloaded router, a faulty cable, or an upstream issue. Keep equipment ventilated according to its manual; do not cover vents or place it near heat sources. An older router may lack the processing capacity, interfaces, or Wi-Fi features needed by a busy network. Firmware updates can address reliability and security issues, but they should come from trusted manufacturer instructions and be planned so a temporary interruption is acceptable.

DHCP normally assigns local IP settings to devices. If one device cannot obtain an address while others can, reconnect it and check its network status before altering the DHCP server. DNS problems can allow a connection to exist while names of websites fail to resolve. A damaged Ethernet cable or failing port may cause an intermittent or unexpectedly limited wired link; compare a known-good cable or port only when safe and permitted. Administrators should check logs and configuration before making changes to an important network.

Equipment checklist

  • Is power present, and is the correct supply in use?
  • Are visible status indicators recorded against the equipment manual?
  • Does the problem affect Ethernet, Wi-Fi, or both?
  • Are several devices affected in the same way?
  • Does the device receive expected local network settings?
  • Are vents clear, cables sound, and ports physically undamaged?
  • Did symptoms start after an approved update, power event, or configuration change?

Equipment that will not power on, repeatedly overheats, shows physical damage, or fails across several known-good devices may require replacement or professional assessment. Avoid opening equipment, altering advanced settings without documentation, or performing a factory reset as an experiment. If the equipment belongs to an organization, involve its administrator before restarting or replacing it.

08 / Workplace diagnostics

Business internet support guidance.

In a workplace, a connectivity fault can affect people, departments, applications, or an entire site differently. Establish its scope before changing a shared network.

Ask whether all employees have a problem or only those on a particular Wi-Fi network, floor, switch, or office area. If cloud applications do not load but other websites work, check whether the application itself has a known issue and whether access works from another approved network. Video conferencing and VoIP can suffer from upload saturation, jitter, packet loss, Wi-Fi interference, or platform issues even while ordinary browsing feels normal. Record the affected meeting or call times and whether wired users see the same symptom.

Point-of-sale connectivity is operationally sensitive: follow your POS provider's approved contingency procedures and never bypass payment security controls. A network printer can be unreachable because of its own power, local address, VLAN, or print queue even while the internet is working. Slow file transfers may involve a remote server, an internal LAN link, or a busy uplink. Guest Wi-Fi failures can be isolated from the staff network; a segmented design means one network's symptoms do not automatically describe the other.

A business troubleshooting checklist

  1. Record the first known failure, impacted locations, and business-critical functions. Identify whether a safety or operational contingency needs to be activated under your own policies.
  2. Compare one affected device with a working device, then compare affected and unaffected network segments. Note Wi-Fi names, wired ports, and locations without exposing sensitive settings.
  3. Test several approved destinations and applications. Determine whether the failure is internet-wide, limited to one platform, or limited to internal resources.
  4. Check shared equipment status and available monitoring with an authorized administrator. Avoid restarting a switch, firewall, router, or ONT that serves others without coordination.
  5. Document the impact on calls, payments, file transfers, printers, or guest access separately. Different symptoms may have different causes.
  6. Escalate through the organization’s established technical process and the applicable service contact route, sharing concise observations rather than speculative conclusions.

An issue confined to one device suggests an endpoint or local port. An issue confined to one floor or VLAN suggests a segment-specific dependency. An issue affecting all devices and both wired and wireless access suggests a shared component or external path. These distinctions help the responsible team prioritize investigation, but they are not a substitute for actual tests. For service-category considerations, see Business Internet.

09 / Complex networks

Dedicated internet and enterprise network issues.

Enterprise diagnostics need a clearly defined service boundary and coordinated changes. A site can have a healthy access circuit while an internal route, firewall policy, or remote service still fails.

For a dedicated circuit, authorized teams can compare its reported status and bandwidth utilization with the times users noticed a problem. A saturated interface may produce queues, increased latency, and packet loss. A change in latency can reflect routing, congestion, or destination behavior, so compare paths and times rather than attributing every change to the circuit. Static IP connectivity should be checked against the actual service specification and approved configuration; never assume that a static address is included.

DNS resolution failures can make an application appear down while its IP path remains reachable. Firewall configuration can block legitimate traffic after a policy change, whereas a permissive emergency rule can create security exposure. VLAN configuration can isolate traffic as intended or unexpectedly disconnect a group of users if a switch port, tag, or trunk is misconfigured. Multi-site problems require checking which locations and applications are affected, including whether a central service has become a common dependency.

Redundant connections and failover designs provide alternatives for defined failure scenarios; they do not guarantee uninterrupted operation. Two paths may share a duct, power source, router, or downstream service. Monitoring of interface state, utilization, errors, latency, and packet loss is useful when compared with a known normal baseline. Administrators should preserve logs and change history before modifying routing, firewall rules, VLANs, addressing, or failover behavior.

Configuration boundary

Advanced network changes should be performed by qualified network administrators who know the organization's topology, security policy, maintenance procedures, and rollback plan. This page is an explanation of concepts, not an instruction to change production settings.

Explore the general service considerations on Dedicated Internet and Enterprise Solutions. Actual circuit characteristics and operational responsibilities must come from the applicable service documentation.

10 / The language of performance

Understanding network performance.

Different measurements answer different questions. Knowing the difference helps you explain why a connection can pass a speed test yet still make a call sound poor.

Bandwidth

The amount of data a link is designed to transfer over time, often expressed in bits per second. Think of it as capacity available to be shared among concurrent activities. A cloud backup and several streams may together consume capacity even if each application works well alone.

Latency

The time data takes to travel between endpoints, commonly reported as a round-trip time. Distance, processing, and queues contribute. A high-latency path can make a game or remote desktop feel unresponsive despite ample download capacity.

Jitter

Variation in packet arrival times. Audio and video need a reasonably steady flow; irregular arrival can cause stutter even when the average latency looks acceptable. Wireless interference and congestion are possible contributors.

Packet loss

Packets that do not arrive at their intended destination. Downloads may retransmit missing data and slow down, while live speech may reveal gaps immediately. Loss can originate on local Wi-Fi, damaged links, congested devices, or other parts of a route.

Throughput

The data transfer actually achieved during a particular test or task. It can be lower than nominal bandwidth because of protocol overhead, shared usage, device limits, server limits, or conditions elsewhere on the path. Test conditions must accompany the number.

Network congestion

Demand exceeding available capacity at a point in the network. Packets wait in queues or may be dropped. A busy upload can make a video call unstable even while a separate download test appears reasonable.

DNS resolution

The process of translating a domain name into an IP address. When name resolution fails, a website may not open by name even though the device remains connected to the network. DNS does not itself carry the website's complete data transfer.

Routing

The process that moves packets through networks toward a destination. A route problem can affect certain destinations while others work. The outbound and return paths may differ, so a single successful test cannot describe every application path.

Streaming often benefits from sustained throughput and buffering; gaming is especially sensitive to delay and loss. Video calls and VoIP depend on timely, steady upload and download. Cloud services can be affected by the local connection, DNS, routing, authentication, or the service provider's own systems. Business applications may depend on several of these at once. Describe the specific symptom and test path rather than using “speed” as a catch-all term.

11 / Check the endpoint

Device and operating-system troubleshooting.

When other devices work, a device-level check can save unnecessary changes to shared network equipment. Start with simple, reversible actions and follow your organization's policies.

Windows computers

Confirm airplane mode is off and the expected Wi-Fi or Ethernet adapter is enabled. Reconnect to the correct network, review the operating system's connection status, and restart the computer if appropriate. Compare another browser or application. A VPN or endpoint policy can alter the route; ask your administrator before changing managed settings.

macOS computers

Check the active network in System Settings and confirm the device joined the intended Wi-Fi name. Try a known working application and, if available, a permitted wired connection. Note whether a VPN is active and whether system updates are pending. Avoid changing DNS or network location settings without understanding the configuration.

Android devices

Check airplane mode, Wi-Fi selection, signal strength, and whether the phone is switching to mobile data. Reconnect to the intended network and restart the device if needed. If only one app fails, review the app and its updates rather than changing the router for every user.

iPhones and iPads

Check Wi-Fi in Settings, confirm the correct network is selected, and compare more than one app. Move nearer the access point to test coverage. A VPN or device-management profile may control connectivity; consult its administrator before removing or changing it.

Smart TVs and gaming consoles

Check whether the device is connected to the expected network and whether the platform's online service is functioning. Updates and background downloads can affect the experience. Compare a suitable Ethernet connection if supported, and distinguish an account or game-service problem from a general internet failure.

Network printers and IoT devices

Confirm power, network association, and whether another device on the permitted network can reach the printer or smart device. Older devices may support only certain Wi-Fi bands or security modes. Do not weaken wireless security to accommodate a device without an administrator's risk assessment.

Outdated software, a disabled adapter, a saved incorrect password, a VPN route, or device-specific DNS settings may explain why one endpoint behaves differently. If a setting is unfamiliar or managed by work or school, document the symptom and ask the responsible administrator. Do not disable essential security protections simply to test whether an application loads.

12 / Addressing and names

DNS and IP address troubleshooting.

Addressing tells devices where to send traffic; DNS helps people use readable names. Understanding a few terms makes a “connected, but nothing opens” report more useful.

An IP address identifies an interface for communication on an IP network. A private IP address is used inside local networks and is not normally routed directly across the public internet. A public IP address is reachable or visible in the wider internet addressing system, although translation, firewalls, and provider arrangements affect how it is used. The address displayed on your device is not necessarily the same as the public address observed by a website.

DHCP automatically supplies devices with network settings such as a local address, subnet information, gateway, and DNS servers. A default gateway is where a device normally sends traffic destined beyond its local network. A subnet mask or prefix indicates which addresses are considered local. An IP conflict occurs when devices attempt to use the same address on the same network; this can cause intermittent or failed communication. Managed networks may assign settings differently, so do not treat a particular address format as proof of a fault.

DNS, the Domain Name System, resolves names such as a website address into IP addresses. If DNS resolution fails, a device may be connected and still be unable to open websites by name. An unavailable website, a wrong DNS response, a browser problem, or a remote service failure can create similar symptoms. Compare multiple sites and devices and avoid changing DNS providers on a managed network without permission.

Safe diagnostic examples

Windows: Open Command Prompt and run ipconfig to view assigned network addresses and the default gateway. Run nslookup example.com to ask the configured DNS resolver for an address. These commands display information; they do not repair a connection or change its settings. Record relevant results without publishing private network details unnecessarily.

macOS: In Terminal, run networksetup -getinfo Wi-Fi to inspect information for the Wi-Fi service where that service name exists, or use System Settings to inspect the active connection. Run nslookup example.com to test name resolution. A different network-service name may be used on your Mac. These are diagnostic examples, not instructions to reconfigure an interface.

Change settings deliberately.

Do not manually replace addresses, gateways, DNS servers, DHCP configuration, or subnet settings without understanding your network and its administrator's requirements. On a shared or managed network, an apparently simple change can interrupt applications or create an address conflict.

13 / Safer connectivity

Network security and safe connectivity practices.

Security is an ongoing practice across the router, connected devices, accounts, and people using them. A working connection is not automatically a safe one.

Use a long, unique Wi-Fi password and modern wireless security such as WPA2-AES or WPA3 where supported by your equipment and devices. Change default administrator credentials on equipment you manage, and keep those credentials distinct from the Wi-Fi password. Install trusted router firmware updates according to the manufacturer's guidance, allowing for a possible restart. Review the list of connected devices periodically, recognizing that device names can be incomplete or misleading.

Avoid configuration changes you cannot explain or reverse. Use networks you trust for sensitive work, and follow your organization's secure remote-access procedures when working away from the office. Suspicious links and unexpected requests for credentials should be treated cautiously even when they appear to come from a familiar sender. Keep important network configurations documented and backed up securely so an authorized administrator can restore them if equipment fails.

A router firewall can control traffic between networks, while endpoint security protects computers and other devices against threats they may encounter through applications, files, and user actions. Neither replaces the other. A VPN can be part of secure remote access, but its presence does not make unsafe behavior harmless; use approved tools and report unusual behavior through your organization's established security process.

If you suspect an active security incident, stop experimenting with settings and involve the responsible administrator or qualified professional. Preserve relevant observations, avoid posting sensitive information publicly, and do not disable protective controls merely to make a failing connection appear to work.

14 / Keep track

Your troubleshooting checklist.

Use this on-page checklist while investigating. It is a personal reference in this browser view; checking a box does not send anything to ZTN or diagnose the cause.

0 of 10 checks noted

This is a downloadable-style reference layout, not a file download or a support submission. Copy your observations into your own notes if you need to retain them.

15 / Prepare the essentials

Information to prepare before contacting support.

A concise, factual description helps someone determine the next appropriate diagnostic step without requiring you to guess the underlying fault.

Have your customer or account reference if applicable, your registered contact details, and the full service location to hand. Note the type of connection if you know it, along with the router, modem, or ONT model as printed on the equipment. Describe what fails in ordinary language: for example, “three wired computers cannot open any websites, but local file sharing works,” rather than simply “the network is broken.”

Include the approximate time symptoms started, whether they recur, and whether one device, several devices, or the whole premises is affected. Record indicator-light labels and behavior against the relevant manual. If speed is the concern, include several dated results with download, upload, latency, and whether each test was wired or wireless. Screenshots of error messages can be useful where appropriate, provided personal or sensitive information is removed first.

For a business, describe the operational impact separately: whether calls, cloud applications, POS terminals, printers, or a particular site are affected. Mention any relevant authorized change shortly before the issue, but avoid sending full configuration files through an unverified channel.

Protect private information.

Do not share passwords, Wi-Fi keys, one-time passcodes (OTPs), or sensitive account credentials in public messages. Use only the appropriate contact route and follow any security instructions applicable to your service.

16 / Know when to stop

When to contact technical assistance.

Self-help should stop when the next step requires specialized tools, access rights, physical repair, or changes that could disrupt others or weaken security.

Seek appropriate assistance for repeated service interruptions, suspected fiber damage, persistent optical-signal warnings, equipment that will not power on, or an outage affecting an entire business. Persistent packet loss after controlled comparisons deserves investigation. Unusual network behavior may require a security response, not a sequence of casual configuration changes. If resolving a problem requires access to routing, firewalls, VLANs, or provider-managed equipment, involve the responsible administrator or qualified technician.

Bring your observations from the checklist and the preparation guide. The ZTN contact page is the place to find the available route for an enquiry; this page does not claim live assistance, particular hours, a ticket system, or a response-time commitment. Physical fiber work should always be left to qualified technicians.

17 / Continue learning

Fiber, business and enterprise support resources.

These pages explain service categories and infrastructure considerations. They do not confirm that a particular option is available at your address.

18 / Frequently asked questions

Technical support questions, answered.

Open any question for a practical explanation. These are general diagnostics, not equipment-specific instructions or confirmation of an individual service fault.

Explore all FAQs
1. Why is my internet not working?

First determine whether one device or several are affected. Confirm power to the relevant equipment, check visible indicators against its manual, and try more than one website or application. If another device works, focus on the failing device. If wired and wireless devices all fail, document the shared symptoms and seek assistance through the applicable route rather than assuming a specific cause.

2. Why is my internet connection slow?

Slow performance can result from competing downloads, a weak wireless signal, device or router limits, a busy remote server, or conditions beyond the premises. Compare repeated tests at different times, preferably including a suitable wired device. Note what application is affected, because slow page loading, a delayed call, and a large transfer may point to different constraints.

3. What should I check before contacting support?

Note when the problem began, which devices are affected, whether wired and wireless access differ, what the equipment indicators show, and whether several destinations fail. Record exact error messages and any relevant speed tests. Avoid resetting equipment or changing unfamiliar settings just to produce a result; a clear description of the original symptom is valuable.

4. Why does my router show no internet?

The router may not have a usable connection to its modem or ONT, the access path may be interrupted, or its configuration may be unable to establish connectivity. Confirm power and obvious Ethernet connections without disturbing optical fiber. Interpret the light or status message using the correct model's documentation; identical-looking indicators can mean different things on different devices.

5. Why is my Wi-Fi connected but there is no internet?

Wi-Fi only confirms that the device has joined a local wireless network. The router can still lack an upstream connection, or the device may have a DNS, gateway, authentication, or application-specific problem. Compare another device on the same Wi-Fi and, if possible, a wired device. Record whether all websites fail or just one destination.

6. Why does Wi-Fi keep disconnecting?

Weak coverage, movement between access points, interference, device software, or a router issue can interrupt wireless association. Test closer to the access point and see whether other devices disconnect at the same time. If only one device is affected, investigate that device; if all wireless devices drop but wired devices remain connected, focus on the wireless network.

7. How do I restart my router safely?

Save active work and coordinate with anyone else using the network. If you are authorized to manage the router, follow its manual's normal restart or power procedure, then allow sufficient time for reconnection. Record the indicators before and after. Do not unplug unfamiliar fiber connectors or restart shared business equipment without the responsible administrator's approval.

8. Should I factory reset my router?

Not as a routine troubleshooting step. A factory reset can erase access settings, Wi-Fi credentials, security rules, and other configuration needed to restore service. Only do it when instructed by the equipment provider or administrator, with an understood restoration procedure and the necessary configuration information available.

9. Why is my fiber ONT showing a warning light?

A warning could indicate an optical signal issue, equipment or power problem, or another model-specific state. Consult the documentation for the exact ONT and record the label, color, and flashing pattern. Do not assume a universal meaning or disconnect fiber to test it. Persistent warnings warrant appropriate technical assistance.

10. What does a LOS light indicate?

LOS commonly refers to “loss of signal,” but the precise behavior and interpretation depend on the equipment and access design. Note whether the indicator is lit or flashing and check the manual. If an optical warning persists, leave connectors alone and request qualified assistance; never look into an optical connector.

11. What does a PON light indicate?

On equipment using a passive optical network, a PON indicator generally relates to the ONT's optical-network connection or registration. Its normal color and pattern are specific to the device and service. Compare with the supplied equipment instructions rather than assuming every PON light follows the same rule.

12. Why is my fiber connection unstable?

Possible causes include power interruptions, customer equipment, an optical-path issue, or conditions elsewhere in the network. Record the times of disconnection, the ONT and router indicator behavior, and whether both wired and wireless devices are affected. Do not bend, clean, or reconnect optical fiber as an experiment; physical inspection and repair belong to qualified technicians.

13. Why is Wi-Fi slower than Ethernet?

Wi-Fi shares radio airtime and must contend with distance, walls, nearby networks, and device capabilities. Ethernet provides a different local connection and may be more consistent under suitable conditions. Compare the same capable device and similar test conditions before concluding that the external service is slow; both methods can still be limited by the destination.

14. What is the difference between 2.4 GHz and 5 GHz Wi-Fi?

2.4 GHz often reaches farther but commonly has more congestion and less available spectrum. 5 GHz generally offers more capacity at shorter distances, depending on equipment and local conditions. Devices must support the selected band. Where supported, 6 GHz adds another option but does not remove the effects of distance or physical obstacles.

15. How can I improve Wi-Fi coverage?

Move the access point to an open, suitable position if cabling allows, and compare results in several rooms. Reduce obvious obstructions, assess interference, and consider additional access points or a properly placed mesh system for a larger premises. A wired backhaul can help connect access points without consuming wireless airtime. Avoid assuming a faster internet plan will correct a radio dead zone.

16. Why do some websites fail to load?

A particular website or its hosting provider may be unavailable, its DNS record may not resolve, or a browser, device, VPN, or network policy may interfere. Try unrelated websites and compare another device or approved connection. If only one destination fails, collect its error message and time; this differs from an internet-wide outage.

17. What is a DNS problem?

DNS translates readable domain names into IP addresses. If that lookup fails, a browser may report that it cannot find a site even when the device remains connected to the network. Compare several domain names and devices; a diagnostic nslookup example.com can show whether a resolver answers. Do not change managed DNS settings without authorization.

18. What is an IP address conflict?

An IP conflict happens when two devices try to use the same address on the same local network. Connectivity can become unreliable because traffic may reach the wrong device or fail intermittently. Record the affected device's network information and involve the network administrator if the environment is managed. Randomly assigning a different address can create another conflict.

19. How do I check my internet speed?

Use a reputable speed-testing service, pause large background transfers where practical, and record download, upload, latency, device, connection type, server, and time. Compare a test near the router with a suitable wired test if possible, then repeat when the problem occurs. A single measurement is only one snapshot, not proof of a persistent fault or a guaranteed service rate.

20. Why does video conferencing lag?

Video meetings need timely upload and download as well as reasonably stable latency. A weak Wi-Fi link, another upload, packet loss, jitter, the device, or the conferencing platform can cause freezes or delayed audio. Check whether other participants or applications are affected and compare a wired connection if appropriate. A headline download result alone does not describe call quality.

21. What causes packet loss?

Packets may be discarded because of congestion, wireless interference, faulty equipment, damaged links, or other path conditions. Live audio can expose loss immediately, while downloads may recover through retransmissions and simply take longer. Compare devices, times, and paths to narrow down where loss begins; a result to one remote host cannot represent every destination.

22. What is network latency?

Latency is the delay between sending data and receiving a response, often measured as a round trip in milliseconds. Distance, processing, queueing, and routing all contribute. High latency can make interactive applications feel sluggish even if a large file can eventually transfer quickly. Test context and the destination matter.

23. What is jitter?

Jitter describes variation in the time packets take to arrive. A call can sound choppy when packets arrive at uneven intervals despite enough average bandwidth. Wireless interference, congestion, and route changes can contribute. Record when the problem occurs and whether it also affects a suitable wired device.

24. Why does my connection slow down during busy hours?

More simultaneous local users and applications can consume shared capacity. Congestion may also occur elsewhere on a route or at a remote service. Compare repeated tests and actual application behavior at busy and quiet times, noting active uploads and downloads. The pattern is useful evidence but does not by itself identify which network segment is congested.

25. Why do multiple devices affect network performance?

Devices share Wi-Fi airtime, router resources, and available internet capacity. A single background backup can use substantial upload bandwidth while several streams or downloads use the downstream path. Count active tasks rather than only connected devices: an idle phone and a computer uploading a large file have very different effects.

26. What should a business do during a connectivity interruption?

First identify which sites, segments, devices, and critical applications are affected. Follow the organization's approved continuity and security procedures, particularly for payments and communications. Coordinate equipment checks with the administrator, preserve logs and timestamps, and use the applicable contact route with a clear description of the business impact. Avoid unplanned changes to shared equipment.

27. What is the difference between a router and a modem?

A modem interfaces with a particular access technology, while a router directs traffic between the local network and other networks. A fiber connection may use an ONT instead of a conventional modem. Some equipment combines routing, access termination, and Wi-Fi in one device, so the boxes in your premises may not map neatly to separate functions.

28. Can a damaged Ethernet cable affect internet performance?

Yes. Physical damage, a poor connector, or an unsuitable cable can cause errors, intermittent links, or a lower negotiated link rate. If authorized and safe, compare with a known-good cable and another port while keeping other conditions similar. Do not confuse an internal cable fault with the external service without a comparison test.

29. When should I contact a qualified technician?

Seek qualified help for suspected fiber damage, physical equipment faults, persistent optical warnings, unsafe wiring, or changes requiring specialist access. Never look into an optical connector or attempt physical fiber repair. Business routing, firewall, and VLAN changes should be handled by qualified administrators who can assess the impact and restore the previous configuration if necessary.

30. How can I contact ZTN about connectivity questions?

Use the Contact ZTN page to find the available contact route. Prepare your service location, relevant account reference if applicable, equipment model, symptom timeline, affected devices, and safe diagnostic observations. This guide does not represent a live support channel or promise any particular availability or response time.

A clearer next step

Need Help With Your Connectivity Requirements?

Explore our support resources or contact ZTN to discuss your internet and network connectivity questions.