@mischk indeed, a configuration error. only affected retro-IP (IPv4); IPv6 was running throughout the night. Should now be fixed.