How do I check service status and report a useful bug?

Choose the right place for your question#

Start with Service status at the top of Help, or System status in the website footer. A known incident may already explain a problem affecting several pages or devices. A green status page does not test every video source.

For a specific symptom, try playback, downloads or sign-in troubleshooting first. Keep any session that still works.

Send a useful report or suggestion#

1. Open the affected page, then select Give feedback in the website footer. You can also start from Contact.
2. Choose the matching category: Bug Report for broken behaviour, Feature Request for an idea, Content Error for incorrect anime information, or General Feedback for something else.
3. Write a specific Title, such as “Episode list stays empty after selecting season 2”, rather than “broken”.
4. In Description, give the steps, expected result and actual result. Use the checklist below and include only details relevant to this problem.
5. Complete any displayed verification and choose Submit Feedback once. Wait for the success message. If an error appears, keep a copy of your description before retrying; closing the form is not proof it was submitted.
6. If you are signed in and the success screen offers View my feedback, use it to review your submission. For direct technical contact or a file that cannot be added to the form, use the contact method displayed on Contact.

The feedback form collects text; do not assume it has a screenshot or diagnostic-file upload. Use a contact channel that accepts a file if support needs one.

What to include: a short report template#

Copy this checklist and fill in the relevant lines:

• I was trying to: describe the task.
• Device and app: model/OS, browser or app name, version if known.
• Steps: the shortest sequence that reproduces it.
• Expected / actual: what should happen and what happens instead.
• Exact error: visible message, with private information removed.
• For playback/downloads: public anime page, season, episode, language and source name.
• Time and scope: approximate time with time zone; whether another episode, source or device works.

For example: “On Android, I open a title, choose season 2 and tap episode 3. The source starts loading but returns the message shown below. Episode 2 works in the same app.” Do not invent a version if you cannot find it; say it is unknown.

For screenshots, capture the relevant error/control, not the whole account page. Crop or obscure usernames, private messages, sign-in codes and private URLs before sending. For desktop playback-engine problems, the diagnostic guide explains the available export; inspect its contents before sharing.

Reports that need a different route#

• Wrong episode, audio or subtitles: on the episode page, use its Report menu if offered, or choose Content Error in feedback. Include the expected and actual content.
• A comment/review breaks the rules: use community reporting so the report identifies the specific contribution.
• Access, export or deletion of your own data: follow account data requests. Hiding a profile or deleting a download does not submit an erasure request.
• A copyright notice: use the DMCA information and the contact details provided there.

Never send passwords, login QR/device codes, authentication tokens or full private media links. Diagnostics may still contain personal details despite automatic redaction. A submitted report is not a promised fix date; if you follow up, include your earlier report reference rather than repeatedly submitting the same issue.