From the source.
Official status JSON, service-by-service component matching, incident metadata and visible fetch timestamps.
The tools you rely on, in one clear view. Know what providers actually report, what people are experiencing, and what remains unknown.
Cloud compute, managed databases and platform services. The status indicator below comes from the public DigitalOcean status feed, not from anonymous reports or independently tested endpoints.
Verify on the official DigitalOcean status page ↗Check the relevant datacenter or region and inspect service-specific metrics before assuming a platform-wide incident.
The provider-wide status published on its public status page. Specific accounts, integrations and regions may behave differently.
Read the official evidence, inspect affected components, and separate community reports from provider statements.
Official feeds have not finished verification. Browse these sources directly, or retry shortly.
Actual provider-published incident notices, not user speculation. Related services are grouped when they share one incident.
Most dashboards blur the line between what a provider said and what strangers reported. We refuse to.
Official status JSON, service-by-service component matching, incident metadata and visible fetch timestamps.
Recent, rate-limited reports offer another perspective. They never turn a green provider status red.
If a feed fails or a requested component is missing, we show what we don’t know. No invented uptime percentages.
Independent by design. Not affiliated with or endorsed by the companies monitored.
No. Signalroom reflects official vendor status feeds, with optional user reports separately. It does not continuously measure service endpoints or your personal availability.
Provider health may exclude region-specific, account-specific, recent or unreported failures. Check your setup and the exact component on the provider's official page.
No. Their volume and timing are displayed as unverified context, but only the provider's published status determines its official indicator.
The browser polls approximately every 90 seconds, while edge responses are normally cached for up to 75 seconds. The UI shows when each source was contacted and marks responses stale when their check timestamp ages beyond five minutes.
No account is required. Reporting must first be enabled by the site operator with Cloudflare D1 storage and abuse-prevention configuration. Only aggregated report counts are displayed.