Get in Touch
Network Support Scope Method Coverage Configuration FAQ
Scope Method Coverage Configuration FAQ
About Us
AI Solutions overview AI Consulting Services AI Strategy and Readiness Enterprise AI Implementation Generative AI Consulting Agentic AI Consulting AI Automation AI Integration
Oracle Services overview Oracle Fusion Cloud Oracle Fusion Financials Oracle Fusion HCM Oracle Fusion SCM Oracle Fusion Project Oracle Sales Cloud Oracle EPM Planning and Budgeting Oracle Hyperion Financial Accounting Hub Oracle BI Integration Oracle Technology Oracle SOA Suite Oracle DBA Oracle APEX Oracle OIC Oracle VBCS Oracle E-Business Suite EBS Upgrade and Support EBS Migration to Cloud Oracle NetSuite NetSuite SuiteScript NetSuite CRM NetSuite Supply Chain, Inventory & Manufacturing NetSuite HCM NetSuite Analytics & AI
Salesforce overview Salesforce Implementation Salesforce Integration Salesforce Managed Services Agentforce and Salesforce AI Salesforce Migration
Microsoft Enterprise Services overview Microsoft Dynamics 365 F&O Microsoft Business Central Microsoft Power BI The .NET Framework
Application Management overview Java Development Mobility Solutions Android App Development React Native Xamarin Universal Windows Platform Automation Testing Services Katalon Selenium DevOps Web Development LAMP Stack MEAN Stack E-commerce Solutions Enterprise E-commerce
Managed IT Services overview Infrastructure Monitoring Network Support End User Support System Support Managed Cloud Services Managed Security Services
Managed Business Services overview Logistics BPO Services Finance and Accounting Services Healthcare BPO Services Mortgage Loan Processing Order Processing
AtomicRoute Enterprise AI Atomic HR
Manufacturing Government and Non-profit IT Services and Networks Education Real Estate Media Logistics Pharmaceutical
Insights Newsroom Gallery Why AtomicNorth Get in Touch

Every link has
a named owner

LAN, WAN, SD-WAN, wireless, VPN and the carrier circuits between your sites, including vendor management when the fault turns out to be on the provider's side.

Configuration is version-controlled, so a rollback is a file rather than somebody's memory.

Get in touch See the coverage
Cover24×7×365

Circuits fail overnight more often than during the day, which is when a staffed shift matters.

ScopeSite to carrier

Switching, routing, wireless, VPN and the provider relationship behind each link.

ConfigVersion-controlled

Every change captured, so a rollback is a known-good file rather than a reconstruction.

VendorsManaged for you

We open and chase the carrier ticket, with the evidence already attached.

What we run

The network, end to end

Most network incidents are diagnosed twice: once by you and again by the carrier. The value of a single owner is that the second diagnosis is not necessary.

Switching and routing

Campus and data centre switching, routing, VLANs, spanning tree, first-hop redundancy and the change control around them.

Configurations are backed up on change and held in version control, with a diff available for every incident review.

A rollback that takes minutes and does not need the original engineer.

WAN and SD-WAN

Site-to-site connectivity, SD-WAN overlays, path selection, quality of service and failover behaviour that has been tested rather than assumed.

Failover is exercised on a schedule, because a standby path nobody has cut over to is a hypothesis.

Failover proven, with the switchover time recorded.

Wireless

Controller and access point management, RF planning, roaming behaviour, guest and corporate separation, and density for spaces that fill up.

Surveys are repeated after floorplan changes, which is when most wireless complaints actually start.

Coverage that survives a full room.

Remote access and VPN

Site-to-site and client VPN, certificate lifecycle, MFA integration and the capacity to absorb a day when everyone works from home.

Certificate expiry is inventoried and alerted, because that is the outage everyone has had at least once.

Remote access that holds on the day it is needed most.

Carrier and vendor management

Circuit inventory, contract and renewal dates, fault raising, escalation through the provider's tiers, and credit claims where the SLA was missed.

We arrive at the carrier with logs and timings, which shortens the argument considerably.

One party chasing the provider, and it is not your team.

Network security controls

Firewall rule lifecycle, segmentation, access control lists and the review process that stops rule bases growing forever.

Rules are reviewed on a cycle with owners named, so temporary exceptions do not become permanent by default.

A rule base you can explain to an auditor.

Taking over a network

StepOneDiscover

Physical and logical topology, circuit inventory with contract dates, configurations captured, and the dependencies nobody documented.

Most estates have at least one link whose purpose nobody can explain. Finding it before it fails is the point.

You receive:

A topology and circuit register

Every link with a provider, a contract date, a bandwidth, a purpose and an owner, plus the single points of failure ranked.

Yours to keep regardless of what happens next.

StepTwoBaseline

Configurations into version control, monitoring on interfaces, paths and circuits, and a performance baseline per site.

Baselines matter most for the sites that complain. Without one, every conversation about slowness is opinion.

You receive:

Configs under control

A backed-up, diffable configuration for every device, plus interface and path monitoring with tuned thresholds.

Certificate and contract expiry dates loaded with alerts ahead of each one.

StepThreeRemediate

The single points of failure, the firmware years out of date, the rules nobody owns, and the failover paths that have never been tested.

Each item is costed and sequenced. You decide what gets fixed and what is accepted as risk on record.

You receive:

A remediation plan

Findings ranked by what they cost on the day they fail, with effort attached and a documented risk acceptance for anything deferred.

Failover tests are executed as part of this step, not promised for later.

StepFourOperate

Steady state: incident response, change management, firmware cycles, scheduled failover tests and carrier escalation on your behalf.

Recurring faults become problem records. A circuit that drops monthly is a supplier conversation, not a monthly ticket.

You receive:

A monthly service review

Incidents by site and cause, change record, firmware position, failover test evidence, and open carrier escalations with ages.

Circuit performance against the provider's SLA, with credits claimed where they are due.

01
Coverage

By layer, and who acts

Response targets are for acknowledgement and first action, set against the site criticality agreed during discovery.

Network Support coverage
AreaScopeFirst actionResponse target
Campus LAN Switching, VLANs, PoE, access portsPort or path isolated, config diff checked30 min, P2
Data centre Core and distribution, redundancy, routingFailover verified, affected path removed from service15 min, P1
WAN and SD-WAN Circuits, overlays, path selection, QoSTraffic moved to a healthy path, carrier ticket opened15 min, P1
Wireless Controllers, access points, RF, guest accessRadio or controller addressed, client impact scoped30 min, P2
Remote access Client and site VPN, certificates, MFATunnel restored or rerouted, capacity checked15 min, P1
Firewall Rule base, segmentation, access listsChange reverted or exception raised with an owner15 min, P1
Configuration

A rollback should be a file, not a memory

The worst hour in a network incident is the one spent working out what the configuration looked like before the change. It is avoidable, and the fix is unglamorous: capture every configuration on change and keep it somewhere diffable.

That single practice shortens most outage post-mortems from a debate into a comparison, and it makes an unfamiliar estate supportable within weeks rather than months.

Ask for a network review
  • Captured on changeEvery device configuration backed up when it changes, held in version control, with a diff available per incident.
  • Dated inventoryCircuits, contracts, certificates and firmware with expiry dates loaded and alerted ahead of time.
  • Tested failoverRedundant paths cut over on a schedule, with the switchover time recorded rather than assumed.

Indicative practice. Scope is confirmed after discovery.

Questions we get asked

Before changing network support

Do you replace our network vendor or work with them?

Work with them. We are the support and escalation layer, not a reseller trying to displace your hardware. Where a platform is genuinely at end of life we will say so and cost the options, and we will keep supporting it while you decide.

Who talks to the carrier?

We do, with the logs and timings already attached, which is the part that shortens a carrier ticket. We also track the SLA and claim credits where they are due, which frequently pays for a slice of the contract and is almost never done by an internal team with other priorities.

Can you support a network you did not design?

That is the normal case. Discovery exists to make it supportable: topology mapped, configurations captured, undocumented links traced to a purpose. It takes weeks rather than days, and it is the reason takeovers succeed or drag.

What about sites in countries where you have no presence?

Remote support and carrier management work anywhere. Hands-on-site work is arranged through local field partners, which we manage and you do not have to. Where a site needs guaranteed on-site response times, we say so before the contract rather than after.

Is out-of-hours cover only for emergencies?

Cover is 24×7 for incidents at the agreed severities. Planned work is deliberately scheduled out of hours as well, because a change window during the day is not a change window, and pretending otherwise is how estates drift.

Links thathold.

Start with a network review. It produces a topology map, a dated circuit register and a ranked risk list, all of which are yours to keep.

Get in touch Book a scoping call