Performance – OpenClaw911

How to Tell a Site-Specific Outage from a General Network Failure

September 20, 2026

Yesterday afternoon, openclaw911.com returned HTTP 502 on both its homepage and its REST endpoint, while two control sites on the same network remained HTTP 200. This morning, the same site came back with HTTP 200 on both checks. The lesson is not just that the outage ended—it is that the diagnosis was possible because we

How to Tell a Site-Specific Outage from a General Network Failure Read More »

When Real-Time Browser Capture Broke Animation Timing

September 12, 2026

–

When Real-Time Browser Capture Broke Animation Timing Read More »

Why a Cached Homepage Is Not Enough to Prove a WordPress Site Is Healthy

August 29, 2026

A website can appear healthy while an important part of it is failing. During a real OpenClaw911 availability check, the public homepage returned HTTP 200, but a database-backed WordPress REST request briefly returned a database error. The difference mattered: the homepage could be served from cache, while the REST endpoint required WordPress and its database

Why a Cached Homepage Is Not Enough to Prove a WordPress Site Is Healthy Read More »