Yes, it was a typo. “4bf2e9…” had resurrections problem (it reappeared 5 times) but it was in section “0100”. Source information is in json part of OP which lists all nodes having more than 2 birth dates.
I don’t have “36a94f…” log, nor any log of problematic nodes. The only logs I have are for nodes “bb922f…”, “96260a…” and “1c4562…” which “properly” died (meaning without any subsequent resurrections).
All the information I have about other nodes (node ids and section prefixes) were obtained with MessageContent::RoutingTableRequest message sent initially from “96260a…” and later from “1c4562…”.
I have identified 39 nodes having resurrections problem listed in json part of OP, namely:
"143156.."
"14dbba.."
"15b812.."
"1f2df8.."
"26c398.."
"3022d9.."
"3101b5.."
"3271a1.."
"32cc41.."
"336045.."
"3453d0.."
"34badc.."
"3512ee.."
"353d82.."
"35e5f4.."
"36a94f.."
"37bdf9.."
"4bf2e9.."
"5086b9.."
"515b32.."
"519d35.."
"51be37.."
"522189.."
"5305f5.."
"53d215.."
"53d3fd.."
"5410da.."
"5413fd.."
"567bb3.."
"56d73d.."
"9b2818.."
"c008ea.."
"c26ebf.."
"c273ee.."
"c2b336.."
"c3287b.."
"c3e5cd.."
"c3f46e.."
"e34b56.."
If Maidsafe doesn’t have the log of any of them, then a call to the community could be launched to try to get some of them.