Read a service bulletin with coverage and freshness intact

Keep reports and measurements distinct

The bulletin normalizes publisher component states and shows the worst reported component state, with separate active incident and maintenance information. GitHub's scope includes services such as Copilot. These are publisher reports, not active probes of every product or measurements of affected users.

Follow the affected scope back to the source

1. Check how many of the four sources are readable and keep an unknown source visible.
2. Read the affected components and incident update, then open the official page for its full scope and timeline.
3. Compare the publisher update time with the retrieval time. A fresh retrieval or cache refresh does not mean a new incident occurred.

Understand aggregation and fallback

The own-origin aggregation reuses a result for 60 seconds and shares an in-flight refresh. It reads only the four fixed feeds with time and body bounds and rejects redirects. If the aggregation is unavailable, the browser can try the same fixed reports directly; CORS or connection restrictions can still make a source unreadable. Unknown or missing incident coverage is not changed into an invented zero.