Regional status page publication

A service operator publishes an incident update but subscribers in one region still see the previous revision.

Run the check

On the owned status site, compare the incident identifier, last-update timestamp and affected component list across the approved regions. Check both the summary and individual incident page.

Choose a network and session

Independent visits from each approved region reveal which incident revision their status surfaces present. Use regional residential exits for independent observations. Rotate only between complete samples, with a fresh browser context each time. Record the observed country for every sample and keep one exit through redirects and resource loading.

Interpret the result

The summary can lag while the incident page is current. Include the observed revision and cache age to help the operator identify the stale surface.

Plan the connection

Check country coverage and compare Residential plans for the required region, assignment term and session controls.