Business Network Outage Checklist

Record what stopped working and when

Record the first failure time and business impact. Identify whether one device, area, application, or the whole site is affected. Note recent construction, equipment moves, provider work, or power interruptions. Assign one person to keep incident notes so checks and changes are not repeated without context.

• List affected services: internet, WiFi, payments, online ordering, printers, phones, cameras, or access-system technology.
• Record what still works and the exact error message, including the time it appeared.
• Note the operating deadline, such as opening, a live event, or an active service period.

Compare symptoms without changing the network

A WiFi connection and an internet connection are different parts of the path. A device can be connected to its local wireless network while internet access is unavailable. Comparing another authorized device on the same network can help show whether the symptom is limited to one device; it does not establish the cause on its own.

• On an approved work device, confirm the expected network name and record its connection status.
• If an authorized device is already connected by cable, note whether it has the same problem. Do not move network cables to create a test.
• Check the relevant provider's official service-status information using an available connection, and record any outage notice or ticket number.

Reference: Microsoft: Fix Wi-Fi connection issues in Windows ↗

Preserve the equipment state

From a safe, accessible position, record equipment names, indicator lights, and warnings. Photograph useful labels without exposing passwords or customer information. Leave cabinets, electrical work, overhead cabling, and equipment you are not authorized to handle to the responsible specialists.

• Do not factory-reset equipment, move patch cables, or restart an entire rack as a first check.
• Do not restart, unplug, bypass, or reconfigure fire alarms, life-safety systems, alarm communicators, or controlled-door equipment. Contact the responsible provider.
• Keep firewalls and security controls enabled. Do not share passwords, payment data, or remote-access codes in an initial text.

Reference: Microsoft: Firewall and network protection ↗

Contact the owner of the affected service

Notify your IT contact and the relevant internet or application provider. Ordering-platform and local-connection problems may require different teams. For cameras or access systems, involve the authorized administrator and equipment provider before changes. Report suspicious account activity through your established security process.

• Use only contingency procedures already approved by your business and the affected service provider.
• If equipment is smoking, damaged, or creating an immediate physical hazard, stop troubleshooting and follow the site's emergency procedures.

Send a support brief that is ready to act on

For urgent technology help, text or call Purely IT at 262-221-6101. Intake is open 24/7; response and on-site dispatch are subject to availability. Purely IT accepts requests across the United States and confirms available remote or site support based on the issue, location, access, and resources.

• Business and site address: [name, street, city, state].
• On-site contact: [name and callback number].
• Issue and start time: [what failed, when, and whether it is intermittent].
• Impact and deadline: [systems affected, what still works, and operating deadline].
• Context: [recent changes, provider, case number, and checks already completed].

Confirm recovery in the business workflow

When support makes an authorized change, record it and verify the affected functions with their owners. Use approved test procedures for payments and ordering rather than creating unplanned transactions. Confirm camera viewing and recording, or access-system behavior, with the responsible administrator. Keep unresolved items visible and identify who owns follow-up work.

• Record the recovery time, checks completed, and any remaining symptoms.
• Label temporary workarounds clearly, with an owner and a plan for review.