Integrity service down for all appNames (503 SERVICE_DISABLED) and provider registrar returns 409 PREWARM_PROFILE_UNAVAILABLE

[barelzrihan2002]

Summary

Both the standard Integrity endpoint (/integrity/getToken) and the provider
registrar bound flow (/{provider}/registrar/start -> /{provider}/integrity/getToken)
are failing for every appName I've tested, consistently across multiple retries.

Environment

• reghelp-client (Python) 1.7.1, installed via pip install reghelp-client
• Also reproduced with raw HTTP (no SDK involved) to rule out a client bug
• API key: g9U987D3...Fu2E (masked here; account balance confirmed working via /balance)

Steps to reproduce

1. Standard Integrity endpoint:

curl -i "https://api.reghelp.net/integrity/getToken?apiKey=<API_KEY>&appName=wa&appDevice=Android&nonce=<url-safe-base64>&appVersionCode=263009720"
Also reproduced with appName=tg and appName=w4b (different apps, same result), and with appDevice=iOS.

2. Provider registrar bound flow (whatsapp provider):


curl -i "https://api.reghelp.net/whatsapp/appParams?apiKey=<API_KEY>&app=wa"
# -> succeeds, returns real WhatsApp APK metadata

curl -i "https://api.reghelp.net/whatsapp/registrar/start?apiKey=<API_KEY>&registrarSessionId=<uuid>&appName=wa&appVersionCode=263009720"
# -> fails
3. Same result via the official Python SDK (get_integrity_token, start_registrar, get_bound_integrity_token) — ruling out a raw-HTTP-specific bug.

Actual result
/integrity/getToken -> HTTP 503, {"detail":"SERVICE_DISABLED"}
Reproduced: 2026-08-16 21:57:05 GMT, CF-RAY: a2c3b155a8aab7cb-FRA
/whatsapp/registrar/start -> HTTP 409, {"detail":"PREWARM_PROFILE_UNAVAILABLE"}
Reproduced: 2026-08-16 21:57:06 GMT, CF-RAY: a2c3b158c8fae862-FRA
/balance and /push/getToken work fine with the same key, so this doesn't look like an account/key issue.
/whatsapp/appParams also works fine and returns valid WhatsApp APK metadata, so the whatsapp provider route itself is reachable — only registrar/start and integrity/getToken fail.
Expected result
A successful task creation (status: "success" with a task id) for /integrity/getToken
with appName=wa, and a successful binding for /whatsapp/registrar/start.

Additional notes
The failure is not app-specific: wa, tg, and w4b all return the identical SERVICE_DISABLED error on the standard Integrity endpoint.
The two failures look like separate root causes: a global Integrity-service outage (503) versus an empty prewarmed-profile pool specifically for the whatsapp registrar provider (409). Happy to provide further request IDs / timestamps on request if it helps narrow this down.

[vrtcode]

Hi The Integrity Service is currently disabled on the service. We are working to restore service