Outages with no clear cause
The link drops, the subscriber complains and there is no clear trace between antenna, OLT, RouterOS and RADIUS. We review every hop with evidence.
Rural ISPs
Technical support for rural ISPs
Your network serves subscribers every day and there is no engineering team behind it. We review the real RouterOS configuration, the FTTH network and the servers, fix the incident and leave you the documentation to operate it.
Day to day
What breaks when there is no engineer on call
It does not take a huge incident: one misconfigured queue, one PPPoE that will not authenticate or one subscriber dropping every night is enough to ruin the week.
Growth without structure
Every new subscriber adds a manual rule. We organize queues, PPPoE profiles and segmentation so the network scales without surprises.
Inherited configuration
Someone who is no longer around built the network. We document what exists, put it in order and leave a backup that can be restored.
Internet exposure
RouterOS with open services and accumulated firewall rules. We audit and harden without taking the operation down.
What we solve
The whole network: access, authentication, transit and DNS
We work on what you already have deployed. Each front maps to a service with a closed scope.
MikroTik and RouterOS
Firewall, NAT, mangle, queues and routing policy on the configuration already running in production.
ServiceFTTH and GPON access
OLT and ONT: profiles, per-subscriber VLANs, provisioning and optical power readings.
ServicePPPoE, RADIUS and CGNAT
Subscriber authentication, speed profiles and CGNAT egress when the IPv4 block is not enough.
ServiceBGP and multihoming
ASN, IP blocks, filters and redundant sessions so transit does not depend on a single provider.
ServiceDNS and servers
Authoritative and recursive resolution, caching, DNSSEC and monitoring of what your network resolves.
ServiceHardening and monitoring
Closed management surface, audited access and threshold alerts before the subscriber calls.
ServiceThe scopes listed here are the usual starting point. The final proposal is adjusted to your topology, your change window and your criticality level.
How we work
Diagnostic, reversible change and documentation
The same method we use on larger networks, with the scope adjusted to what your operation can absorb.
- 01
Diagnostic on the real network
We read the configuration, measure and tell you what is causing the problem. No generic quote and no invented task list.
- 02
Change window and rollback
Prior backup, agreed change and tested rollback. If it cannot be reverted, it does not run during traffic hours.
- 03
Documentation your team can follow
Diagrams, runbook and an .rsc backup. When we finish, the network is understood without depending on us.
Frequently asked
What small ISPs usually ask
Do you work with small and rural ISPs?
Yes, that is our focus. Networks with dozens or hundreds of subscribers, no in-house engineering team, where the person deciding also answers support calls.
Can you review my FTTH network or my wireless access?
Yes. We review OLT, ONT, PPPoE profiles, RADIUS and CGNAT, plus towers, PtP and PtMP links and edge routing.
Do you handle emergencies?
Yes, when there is an open incident. The escalation channel and response time are agreed before they are needed.
How does contracting work?
After the diagnostic we deliver a proposal with closed scope, acceptance criteria and contracting model. Nothing is executed without written approval.
Do you work remotely or do you need to be on site?
Most changes are made remotely with agreed access. When the problem is in the tower, the OLT or the cabling, we coordinate the visit.
Is your network costing you subscribers?
Tell us what fails, how many subscribers it affects and what changed. We answer with a technical diagnostic, not a sales form.