Vendor Change Watchdog Status

Last updated: March 24, 2026

Current Posture

Vendor Change Watchdog is currently operated as a lightweight live service.

The service is available publicly for account login and documentation, with authenticated monitoring workflows for signed-in users.

This page is intended to explain practical operating posture, not to serve as a formal incident portal or uptime commitment.

What Healthy Usually Looks Like

When the service is healthy:

• the public site loads
• /healthz returns a healthy response
• users can log in
• monitored pages continue running on schedule
• notifications and review pages render normally

What This Page Does Not Mean

This page does not currently imply:

• a formal uptime SLA
• a dedicated public incident timeline
• enterprise support-response guarantees
• a promise that every vendor page will always be fetchable

Common Failure Modes

The most common practical problems are:

• a vendor page starts blocking the fetch path
• a monitor stays stale because checks are not advancing
• alert delivery succeeds intermittently but not consistently
• a specific account or page hits a local configuration problem
• a deployment issue causes one route or feature to break while the rest of the app still loads

Practical Reliability Notes

This is not currently presented as a formally guaranteed uptime service.

Users should expect a pragmatic operated product with active monitoring and fixes, but not a separate public incident-management system or enterprise SLA page.

If Something Seems Wrong

Common symptoms:

• login failures
• dashboard errors
• stale Next check times
• repeated notification failures
• monitored pages stuck in fetch-error state
• a public page or dashboard section rendering incorrectly

If that happens:

• try a refresh first
• check whether the issue is account-specific or general
• contact the operator with the route and visible error details

What To Include In A Report

The fastest useful report usually includes:

• the page or route you were using
• what action you took right before the issue
• any visible error text
• whether the issue affects one page or the whole account
• the account email involved, if relevant

Contact For Service Issues

For service-impacting issues, contact:

• admin@teamadler.com

Include:

• the page or route you were using
• what action you took
• any error text you saw
• the account email involved, if relevant