1. Find the official status destination
Start from the provider’s own help center or product navigation. Avoid treating an unfamiliar search result, social post, or status-looking domain as official without a connection from the provider. Bookmark the confirmed destination alongside the support page so it is easier to find during a disruption.
GitHub provides a useful documented example: its support guidance points to GitHub Status for current and past incidents and identifies a Status API. That establishes where GitHub reports service information. It does not establish that GitHub, or another service you use, is experiencing an incident now.
Sources: [1]
2. Match the report to the failing task
Write down the action that failed: opening a page, starting a download, saving an edit, or receiving a confirmation. Then compare that action with the components or services named in the incident. If the report specifies a region, account group, or feature, keep that limitation in your notes.
A warning about one component should not become a claim that the entire company is offline. Equally, a normal summary is not a guarantee that your individual account or connection is working. If the report does not cover your symptom, record the relationship as unknown instead of forcing a match.
3. Read the update time and incident history
Check when the incident began, when the latest update was posted, and which timezone is displayed. Separate the time of the provider’s statement from the time you opened it. A screenshot without a date can be easy to misread when it is forwarded later.
Follow the sequence of updates before summarizing the result. A later recovery update may change the meaning of an earlier warning. If the provider gives an estimate, attribute it to the provider and retain any conditions. Do not convert an estimated recovery time into a promise to your own readers or clients.
4. Keep a short evidence note
Use three fields: “Provider reports,” “I observed,” and “Still unknown.” For a fictional example, a provider might report delayed processing while your own upload remains unconfirmed. Those are related observations; neither proves whether the upload completed in the background.
Record the incident URL, checked time, affected task, and a redacted error message. Before repeating an action that could create a charge, duplicate submission, or public post, inspect the relevant transaction or activity history. Keep account identifiers and private project details out of public screenshots. An access block alone is not evidence of permanent closure.
5. Choose a proportionate next step
If the report closely matches your problem, choose a sensible time to check its next update and preserve unfinished work where possible. If it does not match, collect the minimum details needed for the official support channel. Keep any troubleshooting changes small enough that you can tell what changed.
Close your note with the eventual result: the provider marked the incident resolved, your task succeeded on a later attempt, or the problem remains unresolved. These are separate outcomes. A useful status record helps the next person understand what was known at each point without inventing a cause or a company-wide outage.
Your quick checklist
- The status destination is linked by the provider.
- The affected component matches the task, or the mismatch is recorded.
- Incident and observation times include the timezone.
- Provider claims and personal observations are separate.
- The follow-up result does not overstate the evidence.
Sources & scope
GitHub documentation supports the official status-page example. The incident-reading workflow and fictional scenario are ATN editorial guidance. This article reports no current outage and does not test service availability.
- GitHub Docs: About GitHub status (opens in a new tab)Source checked October 9, 2026
Published October 9, 2026. No affiliate links or paid placements in this guide.
