ATLAS NETWORK INTELLIGENCE

Know What's Happening Across the Network.

Atlas is Layer 3’s network-management and operational-intelligence platform — being developed to bring monitoring, diagnostics, customer context and network events into one clearer operational view.

SITESLINKSCUSTOMERSEVENTS

ATLAS

SEE

Network and service state.

UNDERSTAND

Add customer, site and dependency context.

DIAGNOSE

Interpret evidence before assuming the cause.

ACT

Support people — and later approved automation — with better decisions.

What Atlas Is Network Intelligence Customer Context Diagnostics Monitoring Atlas Health Automation How Atlas Works Current Direction FAQ

ONE OPERATIONAL VIEW

From Network Data to Useful Operational Context.

Networks produce huge amounts of information. Individual tools may show device state, logs, performance, alerts, authentication and traffic or security events.

Atlas is being developed to bring relevant evidence together and help Layer 3 understand what changed, where it happened, who it affects, which systems support that conclusion and what should be checked next.

Atlas should help diagnose before recommending action.

CONNECTED INFRASTRUCTURE

See the Network as a Connected System.

Atlas is being shaped to connect sites, routers, wireless infrastructure, fibre and connectivity, backhaul links, customer services, device relationships, and availability or performance context. Complete live coverage of every device is not claimed today.

SITEROUTERCUSTOMERBACKHAUL

A Network Problem Is Usually a Customer Problem Too.

Technical evidence

Customer, site, service, device, recent events and support context.

Operational impact

A degraded link might affect one customer, an entire sector, a site or several downstream services.

Atlas should help distinguish those situations without exposing or inventing customer data.

EVIDENCE BEFORE ASSUMPTION

Diagnose the Problem Before Changing the Network.

More speed is not always the answer. A slow customer experience could involve congestion, wireless interference, packet loss, DNS, device problems, upstream failure, poor signal or an infrastructure fault. Atlas should help narrow the cause using evidence.

Quality

Latency, packet loss and utilisation.

State

Link state and monitoring alerts.

Change

Authentication events and recent changes.

Security

Relevant network and security events.

Monitoring Should Tell Us More Than “Up” or “Down”.

Current state

What is happening now, including quality and availability.

Recent state

Last successful data, changes and emerging trends.

Customer impact

Who or what may be affected by the evidence.

Atlas should eventually combine supported information from the Layer 3 monitoring ecosystem into useful operational context. This does not claim every integration is live.

ATLAS MUST MONITOR ATLAS

Intelligence Is Only Useful If Its Inputs Are Healthy.

Atlas itself depends on systems and integrations. Dependency health should consider heartbeat, last successful ingest, stale-data detection, error state and availability. If Atlas stops receiving data, Atlas should know.

Data sources

Monitoring platforms, syslog, IDS or security feeds where implemented.

Core services

Redis, Postgres, collectors and workers.

Network systems

UISP integrations, RADIUS and supported infrastructure interfaces.

Service dependencies

DNS or security services and APIs where implemented.

Not every dependency monitor is represented as complete today.

Security Events Need Network Context.

A security event becomes more useful when it can be linked to a customer, source and destination, device, site, severity and recent network behaviour. Atlas may consume security evidence from IDS or syslog systems where implemented.

Atlas is not presented as a SOC, MDR, EDR or guaranteed threat-prevention platform.

Signals Become Context. Context Becomes Better Decisions.

SIGNALS

Network and customer evidence.

COLLECT

Bring supported data together.

CORRELATE

Connect events and relationships.

INTERPRET

Add useful context.

DIAGNOSE

Narrow likely causes.

ACT

Alert, recommend or perform an approved action.

Atlas is not intended to blindly change networks because one alarm fired.

AUTOMATION WITH CONTROL

Automation Should Follow Evidence — Not Replace Judgement.

Future direction may include approved network actions, known recovery procedures, failover workflows, controlled configuration changes and verification after changes. Approvals, guardrails, logging, verification and recovery thinking remain essential.

Structured Access to the Network

Atlas is being developed toward controlled interaction with supported infrastructure, including reading state, interpreting events, diagnostics, alerts and future approved automation.

MikroTik direction

Structured diagnostics and network-state interpretation may support future approved actions. Credentials, private addresses and sensitive topology are never exposed here.

Two Views of the Same Reality.

Network operations

Sites, links, devices, network monitoring, events and diagnostics.

Customer operations

Services, customer devices, health, support context, recent events and relevant operational data.

This is an architectural direction, not a promise that every screen is complete.

Find Problems Before the Customer Has to Explain Them.

Atlas is being shaped to help identify stale data, degraded links, repeated failures, unusual events, availability changes and quality degradation. The goal is earlier, clearer operational awareness — not a promise that every outage is currently detected before customers report it.

CLEAR BOUNDARIES

Atlas Is Not a Magic Autopilot.

Not the customer conversational AI.
Not a guarantee that networks will never fail.
Not unrestricted autonomous control.

Not a replacement for competent engineers.
Not a reason to act without evidence.
Good intelligence should make people and controlled automation better informed.

Atlas Is Being Built in Layers.

1

Bring relevant information together.

2

Understand relationships.

3

Interpret evidence.

4

Recommend next steps.

5

Execute approved workflows where appropriate.

The Atlas Intelligence Layer

Intelligent Monitoring →

Network Automation →

Automated Diagnostics →

Proactive Alerts →

The Questions Atlas Should Help Answer.

Is the site actually down?
Is this one customer or many?
Did something change before the problem started?
Is latency increasing?

Is there packet loss?
Is a dependency stale?
Is this network, service or device related?
What should we check next?

Atlas FAQs

Is Atlas the Layer 3 AI product?

No. Atlas is the Layer 3 network-management and operational-intelligence platform.

Is Layer 3 AI the same as Atlas?

No. Layer 3 AI is the customer conversational AI family.

Does Atlas autonomously control the network?

Atlas is being developed toward controlled approved automation. Unrestricted autonomy is not represented as live.

What information can Atlas use?

Relevant network, monitoring, operational and customer-context data from supported Layer 3 systems and integrations.

Does Atlas replace engineers?

No. Its purpose is to improve visibility, diagnosis and operational decision-making.

Is Atlas customer-facing?

Atlas is primarily an internal operational platform. Selected customer-facing capabilities may be exposed through Layer 3 services in future.

BETTER CONTEXT. BETTER DECISIONS.

Better Network Decisions Start With Better Context.

Atlas is being built to help Layer 3 understand what is happening across the network, diagnose problems using evidence and improve the way technical operations are managed.