Found 15 AKA Mismatch Nodes
| Expected Address | Hostname | Protocol | Announced AKAs | Location | Last Tested | Actions |
|---|---|---|---|---|---|---|
| 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
1200:1/11@anothern
23:400/11@sysopnet
|
Campbellford, CA
EastLink |
2026-10-16 02:59 | |
| 1:154/80 | cpmden.ddns.net | BinkP |
BinkP:
21:2/165@fsxnet
|
Madison, US
Charter Communications |
2026-10-16 00:15 | |
| 1:267/161 | 150.136.85.172 | BinkP |
BinkP:
256:2816/3841.39
|
Ashburn, US
Oracle Corporation |
2026-10-15 02:07 | |
| 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-10-14 04:37 | |
| 1:267/150 | csbbs.dyndns.org | BinkP |
BinkP:
1:267/800@fidonet
1:267/0@fidonet
|
Troy, US
Charter Communications |
2026-10-14 04:27 | |
| 3:633/420 | bbs.tassiebob.com | BinkP |
BinkP:
21:3/169@fsxnet
1337:2/106@tqwnet
|
Melbourne, AU
SUPERLOOP (AUSTRALIA) PTY LTD |
2026-10-13 16:47 | |
| 1:218/930 | cpmden.ddns.net | BinkP |
BinkP:
21:2/165@fsxnet
|
Madison, US
Charter Communications |
2026-10-13 04:30 | |
| 2:5101/1 | fido.feliksas.lv | BinkP |
BinkP:
2:5020/2332@fidonet
|
Helsinki, FI
Hetzner Online GmbH |
2026-10-12 22:04 | |
| 2:250/999 | applewoodbbs.linkpc.net | BinkP |
BinkP:
2:250/1@fidonet
2:25/21@fidonet
2:250/0@fidonet
2:25/0@fidonet
|
Catford, GB
Virgin Media Limited |
2026-10-12 20:10 | |
| 2:5020/113 | horris.privatedns.org | BinkP |
BinkP:
2:5001/100@fidonet
2:5001/5001@fidonet
|
Unknown | 2026-10-12 17:34 | |
| 2:31/747 | ip82-165-93-17.pbiaas.com | BinkP |
BinkP:
2:319/747@fidonet
2:319/0@fidonet
|
Courbevoie, FR
IONOS SE |
2026-10-12 17:27 | |
| 1:226/1701 | bbs.sfhqbbs.org | IFCICO |
IFCICO:
1:2215/1701@fidonet.org
21:3/171@fsxnet.ftn
|
Cuyahoga Falls, US
AT&T Enterprises, LLC |
2026-10-12 17:06 | |
| 1:322/320 | bbs.lostcrypt.com | BinkP |
BinkP:
1:320/9999@fidonet
|
Worcester, US
Charter Communications |
2026-10-12 17:00 | |
| 1:218/602 | wastelands-bbs.net | BinkP |
BinkP:
1:218/601@fidonet
|
Copperopolis, US
Calaveras Internet Company |
2026-10-12 07:29 | |
| 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
21:493/1700@zone21
21:493/1701@zone21
39:17/0@amiganet
39:170/0@amiganet
39:170/1@amiganet
39:170/5832@amiganet
39:170/5833@amiganet
39:170/5834@amiganet
|
Hamburg, DE
Vodafone Kabel Deutschland |
2026-10-12 04:17 |
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.