◎
Customized log templates for Mikrotik
Custom search patterns record exactly what the BTRC asks for — PPPoE ID, MAC, source and NAT IP, ports and timestamps — nothing to reconcile after the fact.
InfinityLog is a complete network-activity monitoring system for ISPs — it captures your subscribers' PPPoE, IP, MAC and port activity the moment your Mikrotik forwards it, and makes months of it searchable in under a second. Regulator-ready, without the storage bill.
Trusted by 350+ network operators across the region
Purpose-built for the way ISPs actually run — Mikrotik-native, multi-vendor syslog, and fast enough to search a quarter of logs while a regulator waits on the phone.
Custom search patterns record exactly what the BTRC asks for — PPPoE ID, MAC, source and NAT IP, ports and timestamps — nothing to reconcile after the fact.
Watch every device's traffic in real time as it lands — instant error and health monitoring, no polling, no lag.
Filter by date, IP, MAC or user, stacked with AND logic and a time-range window — pinpoint one session in a sea of rows.
Resolve any IP and moment back to the PPPoE user who held it — the question every investigation opens with.
Mikrotik-first, and ingests standard syslog from other sources — running on Ubuntu.
Default UDP/514 or any port you set — reduces noise and fits varied network setups.
User- and group-based permission controls with full activity tracking — every operator scoped to exactly what they should see.
Request a full day's log and the server prepares it in the background — a progress bar, then a download link. No timeouts, whether it's ten thousand rows or ten million.
A clean operator console — a resource-aware dashboard, a live trace-route stream, and a search that resolves any subscriber in a second.
Active subscribers, ingestion rate, storage and 24-hour load — at a glance, refreshed as logs land.
| Time | PPPoE user | User IP | Visited |
|---|---|---|---|
| 21:14:06 | rakib_home_842 | 10.250.14.7 | 142.250.199.132 |
| 21:14:05 | shipra_net_119 | 10.250.30.14 | 57.144.160.192 |
| 21:14:05 | tuhin_fiber | 10.250.12.5 | 31.13.71.36 |
| 21:14:04 | nadia_home | 10.250.59.31 | 8.214.27.19 |
| 21:14:04 | hasan.official | 10.250.50.1 | 104.244.42.1 |
Every flow, enriched with the subscriber behind it, streaming as it arrives.
| Time | NAT IP | Visited : Port | MAC |
|---|---|---|---|
| 21:14:06 | 182.16.7.60 | 142.250.199.132:443 | A8:F9:4B… |
| 20:58:22 | 182.16.7.60 | 142.250.80.14:443 | A8:F9:4B… |
| 20:41:09 | 182.16.7.61 | 142.250.199.99:443 | A8:F9:4B… |
| 19:33:50 | 182.16.7.60 | 142.250.4.100:80 | A8:F9:4B… |
| 18:07:12 | 182.16.7.62 | 142.250.66.196:443 | A8:F9:4B… |
Stack filters with AND logic; export the full matching set server-side.
Your Mikrotik ships prerouting logs over syslog to InfinityLog — one line per flow, on the port you choose.
logging action → remote 514Each line is parsed into fields and enriched with the PPPoE user behind the IP — the moment it arrives.
ip · port · mac · pppoeRows land in a columnar store at roughly 16 bytes each — months of history on a disk you can afford.
~16 bytes/event · ~8× smallerQuery any window in under a second, then hand a regulator a clean, timestamped export.
where ip = … < 1sInfinityLog's storage layer was re-engineered from the ground up. The same logs that once filled a 16 TB HDD now fit on a 2 TB SSD — and searches that crawled now finish before you let go of the mouse.
Put it on your trafficper logged event, compressed on disk
to search a full day across all devices
of rows queryable per server
smaller footprint than the legacy store
Every plan is the full product — capture, search, analytics and compliance exports. You scale the hardware, we run the software. Prices in BDT, billed yearly.
Every package has its own recommended spec — tap System requirements on any plan above. Thanks to the columnar rebuild, even the largest tier runs on affordable SSD hardware:
Practical guidance on IP-log compliance, tooling and the operational wins of getting it right.
The record every ISP must keep, why the regulator asks for it, and what "good" looks like.
Read article →Retention, search speed, compliance fit and total cost — the questions that actually decide it.
Read article →From audit-readiness to faster investigations — where a proper log server pays for itself.
Read article →Bangladeshi ISPs must retain subscriber activity logs and produce them on request. InfinityLog is designed around that obligation, not bolted onto it.
InfinityLog is built and run by Softify BD Limited — a Dhaka software company focused on the tools ISPs depend on. We ship, deploy and support it ourselves.
The practical questions that come up in every evaluation — capture, compliance, hardware and migration.
Every connection flow your Mikrotik forwards — the PPPoE account, MAC address, source and NAT IP, source and destination ports, the destination, and a precise timestamp. It's the complete record the BTRC expects, enriched with the subscriber behind each IP the moment it arrives.
Yes — that's the design goal, not an afterthought. InfinityLog captures the full mandated record, stores it append-only with per-source retention windows, and produces clean, timestamped exports you can hand to a regulator without editing. Every operator lookup is itself role-scoped and tracked, so access to the logs is accountable too.
Because events are stored columnar at roughly 16 bytes each, months of history fit on a modest SSD — a network that once needed a 16 TB HDD typically runs on a 2 TB SSD. Every package ships with its own recommended spec, and retention windows are configurable per source.
No. Your Mikrotik simply forwards prerouting logs over syslog — a lightweight, fire-and-forget stream. There's no agent on subscriber devices and nothing inline on your data path; InfinityLog receives and processes everything on its own server.
A search across a full day of a 20,000-subscriber network returns in about a second. You stack filters — date, IP, MAC, user — with AND logic, and export the full matching set server-side without timeouts, whether it's ten thousand rows or ten million.
Yes. InfinityLog can run alongside a legacy MySQL-based store during a dual-write migration, so ingestion never stops and no history is lost while you cut over. We plan and run the cutover with you.
Softify BD Limited builds, deploys and supports InfinityLog directly — on your own hardware, on-premises. It's infrastructure you own, run by a team that has done it across hundreds of ISP networks.
Book a live demo and we'll point a test Mikrotik at it — you'll watch your logs land, search them, and export a compliance record in the same session.