Guadeloupe Proxies

Start from the documented clean state, verify the exit, navigate the same path, and capture URL, visible variant marker, response status where available, cookies created, and UTC time. Repeat from a second clean profile before calling a result stable. Give every GLP attempt a stable ID and preserve the authorized endpoint, expected outcome, proxy configuration, exit observation, status class, safe response fingerprint, connection count, and time. Keep the failed IDs in the final calculation. Use only an endpoint permitted for the Guadeloupe test, keep missing measurements explicit, and never rotate around a refusal or other mandatory stop.

Do not infer city, ZIP, coordinates, carrier, ASN, language, or resident identity from country success. If a narrower field matters, confirm that the chosen product supports it and validate that field in a separate test. The North America list places Belize's 15,612 and Barbados's 13,793 nearest to the Guadeloupe historical total. That placement helps audit the catalogue; it neither confirms current supply nor ranks buyer outcomes. Keep GLP comparator rows labelled and diagnose the requested Guadeloupe route from its own evidence rather than a neighbouring count. Record why each comparator belongs in the authorized review before using it.

Treat the route as suitable for redirect work only when the intended country is observed and the chain can be reproduced from a clean baseline. Reject conclusions based on a cached terminal URL or an undocumented client setting. For GLP, separate mandatory requirements from preferences. Mark country observation, client compatibility, session behavior, response validity, usage measurement, and retry handling as pass or fail, then buy only if the written Guadeloupe threshold survives a repeat run. Reject any Guadeloupe conclusion built from an unverified exit, hidden failures, or a changed rule, and repeat GLP verification after a material configuration change.