About
Yuri "Support" O., and a shelf of routers that did not make it
The company is a MikroTik hAP in a Bucharest flat, an idea about doing one thing properly, and a lot of mail. We started in 2014 because a friend's internet was broken for the fourth time and nobody wanted to admit it was a firewall rule.
Nothing here is a platform. There is no dispatch board, no tier 1, no knowledge base you have to register for. You write, we read it, we ask for a tunnel, and we fix the thing — and if it cannot be fixed from a terminal, we say that in the same mail as the invoice.
| Year | Sessions | Note |
|---|---|---|
| 2014 | 38 | one hAP, one friend, word of mouth |
| 2015 | 76 | VAT registration, first monitored site |
| 2016 | 104 | the blog starts, with a Winbox CVE |
| 2017 | 131 | the Mirai year: remote management everywhere |
| 2018 | 149 | CVE-2018-14847, forty-six routers in three weeks |
| 2019 | 168 | first UniFi-heavy customers |
| 2020 | 201 | everyone discovers their home network |
| 2021 | 213 | the DrayTek years begin |
| 2022 | 226 | most sessions ever in one year |
| 2023 | 219 | TP-Link stok, again and again |
| 2024 | 208 | SwOS joins the list |
| 2025 | 181 | firmware upgrades finally boring |
| total | 1 914 | 2026 adds 174 so far, November nearly over |
Who answers
Yuri O. — the routing
Writes the commands, keeps the CVE list, owns the phrase "let me look at the log first". MikroTik since RouterOS 5, and stubbornly reads vendor release notes even when they are eleven years old and written in three languages.
yuri@mikro.st — yes, that address works, it is the same person who set up the mail server for this site and then wrote a page about why you should not host your own.
Diana — the paperwork
Invoices, scheduling, monitored-site contracts, and the only person here who reads Romanian fiscal updates out loud. If your mail about a €29 tunnel setup got an answer in four minutes on a Saturday, that was not routing skill, that was her.
The alias info@support.mikro.st goes to both of us; ops@support.mikro.st
goes to the monitoring alerts, which is a polite way of describing a phone in a pocket.
Shelf, currently
Test units and spare stock. If your device is on this list we have probably broken it on purpose at least once, which is the cheapest way to learn where the "apply" button really writes.
Last incidents we handled
The honest table: what broke, how long we took, and what it turned out to be. Monitored sites are marked; the rest came in as mail with a subject line like "internet is down again".
| Date | Site | Reported | Cause | Resolve |
|---|---|---|---|---|
| 2026-11-18 | Cabana Aries (monitored) | pppoe flapping at 04:12 | ISP-side BRAS maintenance; the router did nothing wrong | 2 min auto |
| 2026-11-14 | Office Pipera | "wifi is slow on the laptop" | 20 MHz forced on 2.4 GHz by a guest-network rule from 2019 | 12 min |
| 2026-11-09 | Atelier VR (monitored) | alert: config hash changed | an apprentice added a virtual AP at 18:44 | 1 mail |
| 2026-11-02 | Tenda Guesthouse | guests cannot print | client isolation on the guest SSID, working as designed, undocumented | 9 min |
| 2026-10-27 | Sediul Vigor | VPN up, no traffic | missing return route after the 1.5.1.6 to 1.5.1.7 upgrade | 17 min |
| 2026-10-15 | Ferma Sud | switch unreachable | SwOS management VLAN removed by an update; no CVE involved | 22 min |
| 2026-10-03 | Cluj Cabinet | one AP "pending" | inform URL still pointing at a controller that moved in 2024 | 6 min |
| 2026-09-22 | Podul Nou | alert: cpu 91 % | a loop through a switch in a cupboard, and the storm control nobody enabled | 31 min |
Opinions, held firmly
- A router you can read is a router you can fix. Documentation over dashboards.
- Remote management on the WAN interface is a decision, not a default, and usually the wrong one.
- Firmware updates are maintenance, not risk — the risk is updating the one box in the house that has no backup config.
- Two subnets is a network; twelve VLANs and no diagram is a hobby.
- A tunnel on the router, not on a laptop, solves most of what people call "VPN problems at home".
- Monitoring is expensive until the second alert. Then it is a line item.
- If the vendor's own response to a CVE is "we do not consider this a vulnerability", the fix is a firewall rule and a phone call.
- The password you cannot remember is the one that was changed by an update.