Found 15 AKA Mismatch Nodes

Expected Address Hostname Protocol Announced AKAs Location Last Tested Actions
2:240/5700 datenbahn.ydns.eu BinkP
BinkP: 2:240/5832@fidonet 2:240/5833@fidonet 2:240/5834@fidonet 2:240/1@fidonet 2:240/3@fidonet 2:240/0@fidonet 2:24/0@fidonet 2:2454/0@fidonet 21:493/1700@zone21 21:493/1701@zone21 39:17/0@amiganet 39:17/1@amiganet 39:17/170@amiganet 39:17/5832@amiganet 39:17/5833@amiganet 39:17/5834@amiganet 39:170/0@amiganet 39:170/1@amiganet 39:170/170@amiganet 39:170/5832@amiganet 39:170/5833@amiganet 39:170/5834@amiganet
Hamburg, DE
Vodafone Kabel Deutschland
2026-06-19 06:46
1:218/930 cpmden.ddns.net BinkP
BinkP: 21:2/165@fsxnet
Madison, US
Charter Communications
2026-06-19 06:34
1:218/602 wastelands-bbs.net BinkP
BinkP: 1:218/601@fidonet
Copperopolis, US
Calaveras Internet Company
2026-06-19 05:20
1:267/150 csbbs.dyndns.org BinkP
BinkP: 1:267/800@fidonet 1:267/0@fidonet
Troy, US
Charter Communications
2026-06-19 03:12
2:240/5833 N/A BinkP
BinkP: 2:240/5832@fidonet 2:240/5833@fidonet 2:240/5834@fidonet 2:240/1@fidonet 2:240/3@fidonet 2:240/0@fidonet 2:24/0@fidonet 2:2454/0@fidonet 21:493/1700@zone21 21:493/1701@zone21 39:17/0@amiganet 39:17/1@amiganet 39:17/170@amiganet 39:17/5832@amiganet 39:17/5833@amiganet 39:17/5834@amiganet 39:170/0@amiganet 39:170/1@amiganet 39:170/170@amiganet 39:170/5832@amiganet 39:170/5833@amiganet 39:170/5834@amiganet
Hamburg, DE
Vodafone Kabel Deutschland
2026-06-18 17:11
3:633/420 bbs.tassiebob.com BinkP
BinkP: 21:3/169@fsxnet 1337:2/106@tqwnet
Melbourne, AU
SUPERLOOP (AUSTRALIA) PTY LTD
2026-06-18 05:27
1:229/308 centralontarioremote.net BinkP
BinkP: 1:229/307@fidonet 954:11/1@hobbynet 999:11/1@health 86:400/12@nixnet 21:1/159@fsxnet 454:1/308@ilink
Campbellford, CA
EastLink
2026-06-18 00:30
1:322/320 bbs.lostcrypt.com BinkP
BinkP: 1:320/9999@fidonet
Worcester, US
Charter Communications
2026-06-17 00:43
1:220/60 im.ifidonet.com BinkP
BinkP: 1:106/201.0@fidonet 1:106/0 1:1/133 21:4/116@fsxnet 115:1502/226@pascalnet
Houston, US
AT&T Enterprises, LLC
2026-06-17 00:09
2:203/910 eljaco.se BinkP
BinkP: 2:203/0@fidonet 2:20/0@fidonet 2:2/2@fidonet 2:203/2@fidonet
Nol, SE
Bahnhof AB
2026-06-16 19:35
1:106/101 darkmatt.synchro.net BinkP
BinkP: 21:2/155@fsxnet 1337:3/208@tqwnet
Bryan, US
Frontier Communications of America, Inc.
2026-06-16 12:48
1:154/80 cpmden.ddns.net BinkP
BinkP: 21:2/165@fsxnet
Madison, US
Charter Communications
2026-06-15 18:07
1:105/46 x-bit.org BinkP
BinkP: 911:1503/2@zeronet
Forest Grove, US
Wholesail networks LLC
2026-06-15 14:47
2:240/5832 N/A BinkP
BinkP: 2:240/5832@fidonet 2:240/5833@fidonet 2:240/5834@fidonet 2:240/1@fidonet 2:240/3@fidonet 2:240/0@fidonet 2:24/0@fidonet 2:2454/0@fidonet 21:493/1700@zone21 21:493/1701@zone21 39:17/0@amiganet 39:17/1@amiganet 39:17/170@amiganet 39:17/5832@amiganet 39:17/5833@amiganet 39:17/5834@amiganet 39:170/0@amiganet 39:170/1@amiganet 39:170/170@amiganet 39:170/5832@amiganet 39:170/5833@amiganet 39:170/5834@amiganet
Hamburg, DE
Vodafone Kabel Deutschland
2026-06-15 12:07
1:124/75 hamshack.synchro.net BinkP
BinkP: 1:19/42@fidonet 954:200/59 618:250/47@micronet
Oklahoma City, US
Verizon Business
2026-06-08 05:05

What is an AKA mismatch? During BinkP or IFCICO handshakes, nodes announce their addresses (AKAs). An AKA mismatch occurs when the expected nodelist address (zone:net/node) is not found in the list of addresses the node announces.

Common causes: Misconfigured mailer software, outdated address lists, node address changes, or AKA consolidation where a node responds for multiple addresses.

Note: This report shows nodes that were operational (responded successfully) but announced different addresses than expected over the last 30 days.

Tip: Click on a node address to view its full test history and details, including all announced AKAs over time.