A useful connection report lets someone understand what failed without asking five follow-up questions. You do not need to know the cause. The exact message, when it happened, and the checks you already tried are enough to start.
Record the failure before changing anything
Copy the whole error message or take a screenshot of the error window. Note whether the server list failed to load, joining stopped before the world appeared, or you disconnected after playing. Those are different stages of the connection.
Write down the local time and time zone. “It broke yesterday” is hard to compare with a restart; “September 15, 19:40 UTC” identifies a specific attempt. If the issue happened more than once, include a short time range rather than sending a new message for every retry.
Copy and fill in this template
Replace the bracketed parts. Leave a field as “not tested” if you have not checked it; guessing makes the report less useful.
Server address: play.unstablesmp.gg (no added port) Edition and version: Java [version shown in the game] Device / operating system: [for example, Windows laptop] Client: [unmodified, or launcher / mod loader name] Time and time zone: [date, time, zone] Failure stage: [server list / joining / after entering] Exact error: [copy the complete message] Does it happen every time?: [yes / no / not sure] Status page result and time checked: [result / not checked] Checks tried and results: [one line per check] Did it work before?: [when / first attempt] Screenshot: [attach a cropped, redacted image if useful]
Include outcomes, not just a list of actions
“Restarted” does not say what happened next. “Restarted the game; the same Unknown Host message appeared” tells the reader that the symptom persisted. If a clean Java installation works but a modified client does not, say so. That comparison can save a lot of unnecessary network troubleshooting.
Check the matching error section first and record the result of one relevant step. Do not change your DNS, reinstall the game, and reset your router all at once: even if it works afterward, you will not know which change mattered.
Hide information that support does not need
Crop screenshots to the game error. Hide email addresses, personal conversations, browser tabs, and desktop notifications. Do not include passwords, Microsoft sign-in or recovery codes, session tokens, or your home IP address. A report about a public server does not require those details.
Full game logs can contain server addresses, chat, usernames, or identifying file paths. Start with the error text instead of uploading the whole log publicly. If further details are requested, review the relevant excerpt before sharing it through the community's designated support route.
Send it through the community, then keep it together
Open the official Unstable SMP Discord and follow the current instructions for requesting help. Channel names and availability can change, so use the instructions there. Keep follow-up observations in the same conversation and add whether a later retry worked.
A direct message offering to fix the issue by logging into your Microsoft account is not a troubleshooting step. See the account-safety warning if someone asks you to share a code or approve an unfamiliar login.
If you can join but gameplay is slow
Describe what is delayed: the camera, other players, blocks, or everything. Use the lag versus low FPS checks and add those observations to your report. A server-list response alone does not measure gameplay performance.