Municipal Internet Outages: Does Your Backup Connection Keep the Office Working?

Start with what stops at the counter

Imagine a township office on a busy morning. Computers are powered on, but the cloud application will not open and internet-based phones cannot reach outside callers. Someone remembers that a backup connection was installed last year. Nobody is sure which devices use it or whether it has been tested since the phone system changed. The missing piece is an office plan tied to that connection.

For Michigan townships, villages, and cities, begin with three activities that depend on connectivity: helping a resident, communicating with staff, and reaching an essential application. Identify the device, service, and employee involved in each. Then ask IT what remains available during a primary internet outage and what staff should do while the technical team investigates.

Define what the backup is supposed to support

A second internet service and a personal phone hotspot are different arrangements. Decide which municipal devices may use the approved backup and how they connect. Record whether switching is automatic or requires an authorized person. Give staff a clear instruction rather than expecting everyone to change network settings independently when an outage begins.

Ask about the backup service’s capacity, usage limits, and any restrictions relevant to the planned work. For a hypothetical village hall, the priority might be the counter application and office phones while large downloads wait. Agree on that priority with the department and IT. Test the intended combination of activities instead of assuming that one web page loading means the whole office can continue normally.

Ask what can interrupt both connections

NIST’s contingency planning guide recommends identifying telecommunications dependencies and single points of failure. Use that planning approach to ask whether the primary and backup connections depend on the same equipment, building power, or upstream infrastructure. Have IT and the service providers explain what the alternate path protects against and which interruptions it cannot address.

Keep the question specific to your building. Where is the backup equipment installed, who can reach it, and what must be powered for it to work? If cellular service is proposed, arrange a site check where the equipment will actually operate. Document the results and the remaining limitations. A second provider’s name alone does not establish that two paths will survive the same local disruption.

Check the applications, phones, and remote connections

Netgate’s documentation illustrates why internet failover needs more than a spare circuit: firewall-generated traffic, name resolution, and VPN connections have their own routing considerations. Ask your technical team how the equivalent parts work in your environment. Keep the configuration work with IT and identify the application or phone provider needed to validate any service-specific dependency.

Also ask what happens to work already in progress. Netgate describes how existing connections may need to reconnect after a failed path is replaced. Have IT explain what staff could see and the correct recovery step for each important application. If a transaction’s result is uncertain, staff should follow the application’s approved verification process before repeating it. Include incoming calls and approved remote access in the review.

Make the outage handoff easy to start

Record the office’s support contact, internet provider, service location, and circuit or account identifier in an approved place. Name the employee who can authorize troubleshooting and the backup contact for absences. Decide how that person reaches support if normal email and office phones are unavailable. Contact details should be usable through the office’s agreed alternate method.

Give staff a short reporting prompt: when the problem started, which building and services are affected, and whether other devices show the same issue. Netgate’s troubleshooting guidance notes that monitoring a reachable modem can miss a failure farther along the internet path. Ask IT how an outage is detected in your system and who receives that alert. Staff should report observed symptoms rather than treating equipment lights as proof of internet availability.

Test the switch and the return to normal

Arrange a controlled test with IT, affected departments, and relevant vendors. Agree on timing, interruption limits, and how to stop the test. Let the technical team simulate the failure through its approved procedure. Use sample work that does not create real payments or other unintended business records, and tell staff which temporary interruption to expect.

Check the priority application, an approved phone-call test, and other agreed workflows while the alternate connection is active. Record what worked, what required a reconnect, and what remained unavailable. Then have IT restore the normal path and verify the same activities again. NIST includes testing and plan maintenance in contingency planning; use the findings to update instructions after equipment, provider, or application changes.

Use this checklist at your next IT review

Managed IT in Michigan should include a practical conversation about connectivity and office responsibilities. Bring one building’s priority workflows to your next Michigan IT services review and ask for clear answers to these questions.

• Which activities and devices must the approved backup support?
• Who switches the connection, and what capacity or usage limits apply?
• What shared equipment, power, or provider dependencies remain?
• Have applications, incoming calls, and approved remote access been checked?
• Who receives outage alerts and contacts the responsible providers?
• Has a controlled test covered both failover and the return to normal?