Send your hosting provider the exact URL, the time and time zone, and the response you received. Add whether the problem persists when you try manually. This gives support a specific case to investigate instead of a general message like “the site wasn’t working well yesterday.”
reChecker data shows responses at the times of its requests. You can share it along with your manual check and any known site changes. You don’t need to forward your entire account or name the hosting provider as the cause in advance.
Gather the URL, time, and response
Provide the main domain and the affected URL. If the error occurs after navigating from another page, include the original page. For a form, describe the step where the action fails: the hosting provider may refer the issue to the application developer.
Record the event time in monitoring and the time of your own attempt separately. Don’t replace them with the time you read the email. If a visitor gave only an approximate time, mark it as approximate.
Include the error code or exact error text, if available. Distinguish between a connection failure, an incorrect page, and a slow response. For help reading events, see the availability monitoring guide.
Include any known update and its time. If you don’t have this information, say so. A release close to the error is a lead to investigate, not a confirmed cause. The person handling the issue can compare the server’s technical records, or logs, with the time interval you provide.
Copy a short template
Fill in the fields before sending. This is text for your support request, not an automatic message from reChecker.
Домен и проблемный адрес:
Ожидаемое поведение:
Событие reChecker — время, часовой пояс и ответ:
Ручная попытка — время, устройство/сеть и результат:
Сохраняется ли проблема сейчас:
Известные изменения сайта и их время:
Просьба к поддержке:If a detail is unknown, add a clear explanation. Don’t make up an exact start time: a five-minute check shows a response at a particular moment, not every second before it.
Example support request: “example.ru, /catalog. We expect the catalog page, but reChecker reported a response error at 10:05 MSK on 04.10. At 10:12, the URL didn’t open on either the office or mobile network; the home page works. At 09:40, we released a catalog update. Please check the current response and the server logs for this time interval, and report the confirmed status and next step.”
Attach a screenshot or the exact error message, without passwords, access codes, or visitor data. If support needs additional access, the owner should provide it according to the agreed procedure.
Clarify what support actually checked
Keep the support ticket number and the name of the person who started investigating. Ask what the next step is and when you can expect a response. If information is needed from the developer, assign someone to gather it.
If the response is “the server is working,” you can calmly ask: “Did you check /catalog during the specified interval? What response did you get? Our home page opens, but the catalog doesn’t.” This narrows down the question without arguing over which source is correct.
If the hosting provider has referred the issue to the developer, keep their findings and the checks they performed in the same ticket. The technical task fields are in the developer template. The next person handling the issue won’t have to piece everything together from different chats.
Check the specific result you asked to restore
After hearing back from support, open the original URL under the same conditions as before. Compare it with the expected behavior: the catalog should display products, not just return a technical placeholder page.
Check the next actual results in the site monitoring dashboard. If the problem involves submitting a request, confirm separately that it was received; a page response doesn’t prove that.
Record the outcome: “At 10:42, the catalog opened on both networks; the cause is still being investigated.” Recovery and finding the cause may happen at different times. Keep the original case, the change in who handled it, and the result check; they will help you compare the two incidents if the problem happens again.