<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Swift Fox changelog</title><description>What&apos;s new in Swift Fox: dated release notes for the WISP operations platform.</description><link>https://swiftfox.net</link><item><title>RF coverage maps, data export, more beta netmap fixes</title><link>https://swiftfox.net/changelog/2026-08</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-08</guid><description>RF coverage maps: Open the RF Coverage tab on any site in the new network map and you get predicted coverage for each sector drawn over the map, computed from open LIDAR terrain (USGS 3DEP in the US, CanElevation in Canada, with a 30 m Copernicus baseline where no LIDAR exists) and the actual radio and antenna on the tower. Terrain for your area is fetched automatically the first time you open it, and sectors are discovered from the devices Swift Fox already logs into, so there is very little to set up.

Data export: Admin → Data Export is a real export now. Pick from 20 datasets across customers, billing, service packages and CPEs, and Swift Fox builds a ZIP of CSVs (with a manifest) in the background with live progress, then gives you a download link that works for seven days. Every customer-related file carries the account number so you can join them in a spreadsheet.

Auto traffic balancing has better error reporting: To help ISPs more easily roll out auto balancing, Swift Fox now checks and alerts for some new types of network misconfigurations: parallel links where only one radio has TE enabled, fixed bandwidth on TE interfaces too small to support enough tunnels, and a loopback address that doesn&apos;t match the OSPF router-id.

Netmap beta fixes: Another round from beta feedback. PFO percentage labels on backhauls update live, clicking an access point in map view stays on the map, and hovering a customer row draws a line from the tower to their dot. The region breadcrumb follows map drills, the Backhauls tab colours latency and loss separately, customer names in AP Clients no longer all drift to blue after a while, and the routing tables in the device pane are sortable.

Subnets page and IP details: The Subnets page was rebuilt on the new system from ISP feedback: filter to just the /24s that are actually on your network, pick a /24 to expand, and it works on a phone. The IP detail popup you get by hovering an address anywhere in Swift Fox can now be pinned with a click (or a tap), so that links to the device, site and customer are actually clickable now.

CPE login and RouterOS 7 fixes: Credential chains now advance past a connection failure as well as a bad password, so a CPE whose SSH is on a custom port no longer gets stuck behind a port-22 credential at the top of the chain. Once a port answers, the chain sticks to that port&apos;s credentials, so a wrong password is reported as a wrong password. Disconnected customers whose radio still pings but can&apos;t be logged into are reported as issues now instead of skipped.

Undo a deposit: Each previous deposit on the Deposits page has an Undo link, for when a batch was closed with the wrong payments in it: the deposit is removed and its payments go back to the undeposited list. This only works for deposits not part of a Canadian legacy EFT batch, as those are locked to the submitted file.

Call volume report restyle: The call volume report on the Phone page got a restyle: a proper heat ramp on the hourly grid, empty hours hidden, and abandoned calls in red on the chart.</description><pubDate>Mon, 31 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Netmap beta speed-up, Pathbox 1.0.8, CGNAT on multiple edges</title><link>https://swiftfox.net/changelog/2026-07</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-07</guid><description>Netmap beta: much faster on big networks: The new network map got a performance pass after beta feedback from the larger networks. Tabs only load when you open them, the Discovered list pages 250 rows at a time with a text filter, and the map layout is only recomputed when something actually moves. On a 300-site network the browser tab went from over 2 GB of memory to around 70 MB.

Map view on MapLibre: The map view of the network map now renders with MapLibre GL instead of Leaflet, so panning and zooming with a lot of customer dots on screen is much smoother. This will also allow us to more easily roll out an upcoming feature involving RF propagation mapping.

Pathbox 1.0.7 and 1.0.8: Two releases out of the first production Pathbox deployment. A memory leak in the latency counters and another in the bridge counters (public IPs on the upstream side) are fixed, rsvpd reconnects to MQTT properly and restarts itself if it can&apos;t, and a restart bug that stacked VPP feature arcs (which multiplied NetFlow counts) is gone.

CGNAT with more than one edge router: If you run CGNAT on two or more edge routers, each router now only gets the NAT rules for its own private subnets. Before this, every edge received every pool&apos;s rules. New private subnets that overlap an existing pool are rejected when you save (a private IP can only be behind one edge), and long rule pushes are split to stay under RouterOS&apos;s 4096-character line limit.

Smaller fixes: Changing a device&apos;s class or deleting it clears its old frequency records, and the Frequencies tab hides stale entries. Bandwidth graphs on the network map filter out the occasional impossible spike (over 1 Tbit) that a counter reset produced.</description><pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The new network map, SSH in the browser, traceroute</title><link>https://swiftfox.net/changelog/2026-06</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-06</guid><description>New network map (beta, everyone): The rebuilt network map opened to all ISPs this month: the same workflows in a much faster interface — edit modals, device detail panes with issue history, region views, PFO status labels, and a colourblind-friendly quality palette. Toggle between it and the classic map per user by going to &quot;Actions - Switch to Netmap Beta&quot;.

SSH from the browser: Click a device on the map and open a real SSH terminal to it, right in the browser — no VPN or jump host required. Sessions run through your pingbox, so nothing on your network needs to be exposed.

Traceroute everywhere: Run traceroutes from the network map, the customer page, or against any arbitrary IP — alongside the ping and SSH tools, on desktop and mobile.</description><pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Neighbour discovery, credential chains, always-on monitoring</title><link>https://swiftfox.net/changelog/2026-05</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-05</guid><description>Passive neighbour discovery: Pingboxes now listen for LLDP, CDP, and MNDP announcements on your network — building a live picture of what&apos;s cabled to what without you typing in a single link. This feeds the upcoming guided network discovery flow.

New credentials system: A rebuilt credentials UI with ordered credential chains: Swift Fox tries each credential in order (each with its own custom port) until one works, and remembers what worked per device. Much less fiddly for networks with generations of password schemes.

Cloud pingbox latency test: If you&apos;re choosing a cloud pingbox region, you can now run a live latency test from your browser to each location before you pick.

Pathbox v1.0.5 – v1.0.6: Preflight picks better NICs and validates Intel X710 firmware, AMD CPUs report correctly on the dashboard, and every appliance now provisions a colocated pingbox automatically. Appliances also appear on the manage pingboxes page.

Config backup overhaul: Device config backups migrated to the new backend; the legacy backup task is retired. Config backups also gained a much-improved diff comparison tool in the new netmap beta launching next month.</description><pubDate>Sun, 31 May 2026 00:00:00 GMT</pubDate></item><item><title>Pathbox 1.0 and the new balancing engine</title><link>https://swiftfox.net/changelog/2026-04</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-04</guid><description>Pathbox: first releases: Our inline appliance for non-MikroTik networks shipped its first versions. VPP-based with custom plugins for per-subscriber fq_codel shaping, captive disconnects, MSS clamping, and RSVP-TE — with a web UI for provisioning, live dashboard graphs, and health monitoring from the platform.

Auto traffic balancing: new engine live: The rebuilt balancing engine went into production: NetFlow demand data calibrated against interface counters, smarter spreading across redundant backhauls, and appliance-aware path selection.

Customer import wizard: A new guided importer brings customer lists in from spreadsheets and other systems — mapping columns interactively instead of demanding a rigid template.

4096-QAM support: Radios negotiating 4096-QAM report their true modulation and capacity — frequency planning and backhaul capacity math stay accurate on the newest gear.

MTU fragmentation at tunnel ingress: Traffic exceeding the path MTU at a TE tunnel entrance is fragmented correctly instead of dropped, finishing off the MTU work from March.

FCC Form 477 updates: Reports round speeds above 10 Mbit to whole numbers per the updated FCC specification.</description><pubDate>Thu, 30 Apr 2026 00:00:00 GMT</pubDate></item><item><title>MTU monitoring and MSS clamping</title><link>https://swiftfox.net/changelog/2026-03</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-03</guid><description>MTU monitoring and TCP MSS clamping: Swift Fox now probes and monitors path MTU across your network and can clamp TCP MSS automatically — catching the classic &quot;some websites don&apos;t load&quot; fragmentation problems before a customer calls about them.

Routing analysis: tunnels view: The routing analysis screen gained a tunnels tab and MTU details, so you can see every TE tunnel, its path, and its constraints in one place.

Balancing engine rework underway: The auto traffic balancing engine was rebuilt around a faster LP solver with two-pass spreading over redundant backhauls, and native RouterOS v6 MPLS/TE support in the new engine. It went live the following month.

PFO fix for very large networks: PFO now splits router commands that exceed RouterOS&apos;s 4096-character limit — shaping syncs reliably no matter how many packages you have.</description><pubDate>Tue, 31 Mar 2026 00:00:00 GMT</pubDate></item><item><title>The pingbox, rewritten</title><link>https://swiftfox.net/changelog/2026-02</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-02</guid><description>pingboxd: a new monitoring agent: The pingbox agent was rewritten from the ground up as a small native daemon: a single static binary that runs on anything, syncs over MQTT, keeps its own time with NTP, and manages SSH sessions to your gear far more carefully. Rolled out fleet-wide this month.

New real-time ping tests: The real-time ping test tool has been in Swift Fox since the very start, and it was beginning to show its age. It&apos;s been fully redesigned on the frontend and backend to be more reliable and easier to use. You can now ping infrastructure devices in addition to CPEs, and select which pingbox you&apos;re pinging from.

Updated TCP latency on customer pages: Live TCP latency monitoring and traces are now sourced from the new pingbox backend, enriched with geolocation and ASN lookups.

RB5009UPr voltage monitoring: MikroTik RB5009UPr routers report supply voltage as a monitored metric.</description><pubDate>Sat, 28 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Bugfixes and backend work</title><link>https://swiftfox.net/changelog/2026-01</link><guid isPermaLink="true">https://swiftfox.net/changelog/2026-01</guid><description>Backhaul quality history: Backhaul status history is computed from the new metrics backend, combining bandwidth metrics and ping data into a single stored quality state per backhaul.

Data-entry quality of life: Small things that add up: postal codes autofill their form fields, pasting a full phone number into the area-code box splits it correctly, and the paging page nudges you to create a rule if none exist.

Pingbox connectivity fixes: Pingboxes negotiate SSH with a wider set of algorithms for older devices, and a memory leak in traffic accounting is fixed.</description><pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate></item><item><title>Faster netmap, vintage NanoStations, next-gen pingbox</title><link>https://swiftfox.net/changelog/2025-12</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-12</guid><description>Netmap quality data moved to the new backend: Map quality colouring now comes from the new time-series backend with Redis-cached state — faster map loads and live quality updates, and the first big step in retiring the legacy pinger.

Pre-M NanoStation support: Based on a request from an ISP in Africa monitoring donated equipment, pre-M Ubiquiti NanoStations are now recognized and monitored like everything else. When we say we&apos;ll add support for any WISP gear, we mean it!

CPE issue reporting: Customer radios now raise issues in the alerting system, not just infrastructure devices.

Next-generation pingbox groundwork: The new pingbox generation syncs its ping targets exclusively over MQTT — quicker to pick up changes and simpler to run behind strict firewalls.</description><pubDate>Wed, 31 Dec 2025 00:00:00 GMT</pubDate></item><item><title>New paging engine, backhaul alerting, power devices</title><link>https://swiftfox.net/changelog/2025-11</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-11</guid><description>Paging engine rebuilt: A ground-up rebuild of paging: issue severities, per-timespan rules per user and delivery method, PagerDuty support alongside SMS and email, rate limiting, and repage limits. The issues list gained severity icons, sortable dates, and human-readable durations. Legacy paging is deprecated.

Backhaul metrics and alerting: Backhauls are now monitored in their own right: capacity and usage metrics with thresholds, collapsible threshold menus, and default paging rules on every backhaul.

Power device monitoring: Ubiquiti power managers join the map as a device class: battery graphing, state of charge, DC power draw, and backup-radio status on Wave and GigaBeam radios — so you can watch a tower ride out an outage on batteries.</description><pubDate>Sun, 30 Nov 2025 00:00:00 GMT</pubDate></item><item><title>Editable alert thresholds and uptime tracking</title><link>https://swiftfox.net/changelog/2025-09</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-09</guid><description>Editable alert thresholds: Alert thresholds are now editable right from the device pane: adjust what counts as degraded per metric, edit several at once, and set wait periods so a brief blip doesn&apos;t page anyone at 3 a.m.

Uptime tracking everywhere: Linux servers, MikroTik, generic SNMP, and Ubiquiti devices all report uptime as a monitored metric — reboots show up as issues instead of going unnoticed.</description><pubDate>Tue, 30 Sep 2025 00:00:00 GMT</pubDate></item><item><title>Alerting overhaul, Linux servers, Ubiquiti MLO</title><link>https://swiftfox.net/changelog/2025-08</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-08</guid><description>Issues and paging system overhaul: The alerting engine was rewritten around per-device metric overrides: static default thresholds per device class, cleaner issue naming, and a more reliable paging handoff.

Linux server monitoring: Swift Fox now monitors Linux servers alongside your network gear — health, CPU, and memory usage tracked like any other device on the map.

Ubiquiti MLO radio support: Multi-link-operation Ubiquiti radios are recognized and monitored, including correct interface reporting on backhauls.

Netonix and EdgeSwitch bandwidth counters: Netonix and Ubiquiti EdgeSwitch interfaces now record bandwidth counters, so switch ports show up in interface graphs.

CGNAT management improvements: CGNAT pools are visible on the subnets page, slot assignment respects a minimum-traffic threshold, and captive portal sync understands CGNAT public addresses.

IPPay support via Spreedly: IPPay joins the supported payment providers via Spreedly tokenization, and existing IPPay account information is migrated over securely.</description><pubDate>Sun, 31 Aug 2025 00:00:00 GMT</pubDate></item><item><title>Billing hardening and FCC reporting</title><link>https://swiftfox.net/changelog/2025-07</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-07</guid><description>Spreedly payment hardening: A round of polish on the new card processing: tighter iframe security for card entry, automatic tokenization of legacy stored cards, fixes to automatic payments, and a clearer flow for turning autopay off.

FCC Form 477 reporting fixes: The FCC 477 report works with the new GPS coordinate fields and secure geocoding lookups.

Server migration: We moved our servers to the new datacentre in a late-night migration window, with minimal impact to users and no reported issues.</description><pubDate>Thu, 31 Jul 2025 00:00:00 GMT</pubDate></item><item><title>Raspberry Pi pingboxes, Baicells, SNMP devices</title><link>https://swiftfox.net/changelog/2025-q2</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-q2</guid><description>Flash-your-own pingbox: Raspberry Pi 4/5 images: In addition to the VM image and cloud tunnel, you can now download a ready-to-flash pingbox image for the Raspberry Pi 4 or 5. If you&apos;ve got one in a drawer, that&apos;s all the hardware you need.

Baicells access point support: Baicells LTE access points joined the supported-vendor list, with full monitoring support.

Generic SNMP device support: Devices that don&apos;t have a native Swift Fox collector can now be monitored over standard SNMP.

Mimosa monitoring improvements: Mimosa devices are polled over HTTPS where available, and backhaul capacity reporting is more accurate.</description><pubDate>Mon, 30 Jun 2025 00:00:00 GMT</pubDate></item><item><title>Spreedly billing, network regions, Ubiquiti Wave</title><link>https://swiftfox.net/changelog/2025-q1</link><guid isPermaLink="true">https://swiftfox.net/changelog/2025-q1</guid><description>Credit card processing via Spreedly: Swift Fox billing moved to Spreedly for card processing: gateway configuration, customer portal payments, automatic billing, and refunds all run through tokenized card storage. ISPs can now move freely between any of Spreedly&apos;s 150+ supported merchant providers without having to transfer card data. New ISPs default to Spreedly from day one.

Network regions: Larger networks can now be organized into regions, managed from network settings. Regions work like sites do, one level of abstraction up — and backhauls that span sites in different regions let you switch between them.

Ubiquiti Wave support: Wave 60 GHz radios are now fully monitored: backhaul graphs, association lists, frequency tracking, and bandwidth counters.

Better map imagery: The network map picked up new base layers, including hybrid satellite and aerial views, for more accurate tower and customer placement.</description><pubDate>Mon, 31 Mar 2025 00:00:00 GMT</pubDate></item></channel></rss>