Babel bug discovered

It figures...   After several months of testing, a bug in the Babel implementation surfaced - naturally after a product release.  Somewhat randomly and rarely, after a reboot or upgrade, the Babel connection between two nodes will not operate correctly. Symptoms are lack of connectivity with Babel nodes, usually in one direction rather than both. If you're experiencing this, open up the panel on a Local or Neighborhood node. The issue is evidenced by the Babel Metric in the lower right having a value of -1.

Restarting Babel at either end of the connection should resolve it, as it appears to be a boot-up timing issue. Rebooting one of the nodes is the easiest way to do this.  But consider updating to production release 3.25.5.1 which will resolve the issue.