The incident also happened once with me.
Have you tried it before with a router reboot?
Kungfooman had advised me and then it went away.
I wish you luck anyway to find the error in the haystack.