Troubleshoot old content or an unexpected redirect

Record where the browser goes

Start with the intended website address and note the final address shown after it loads. Capture whether the hostname changes, an old IP address appears, or only the page content is outdated. These symptoms can involve different layers of caching or routing.

Make a controlled comparison

1. Enter the full HTTPS address directly rather than following an old bookmark.
2. Compare in a private browser window or another browser.
3. Check on another device, ideally using a different connection.
4. Note which combinations work and which do not.
5. Send both the starting and final addresses to support.

A phone working while one desktop browser fails is useful evidence; it does not by itself prove the exact cache responsible.

Use the portal refresh link when appropriate

For these support portals only, opening the homepage with ?refresh_support=1 requests a browser cache refresh. Use refresh Bluegrass Cloud support or refresh Cloud Markup support. This control is specific to our portals and is not a general fix for other websites.

Before clearing browser data

Save any unsaved work. Clearing site data can sign you out or remove local drafts. Ask support for a targeted next step if the comparison still shows inconsistent results. Avoid repeatedly changing DNS while diagnosing a browser-specific symptom.