One platform, several workloads
Chat, image generation, video, voice and music are separate workloads. A working homepage does not establish that every generation pipeline is available. Likewise, one failed request does not prove that all services are down. Look for the affected function and the time of the problem.
Read a status report carefully
An operational report needs a timestamp and a description of the affected service. Queue length, uptime and response time are measurements, not values that can be inferred from a loading screen. Consult service notices together with the behavior you can reproduce. For recurring issues, the troubleshooting guide provides account and browser checks.
Make an issue reproducible
Record the time, the affected action and any visible error. Note whether it concerns chat, images, video, voice or music, and whether it happens in another browser. Do not share session tokens or passwords. A clear description helps distinguish an account problem, a failed generation and a broader interruption.