This happened before. It seems like chat history is a separate (micro)service with lower-than-perfect availability. It came back last time, and have no reason to believe it wouldn't this time.