Bitware Labs Est. 2022

Bitware Labs/Status

Estate status

We sell monitoring and incident response, so here is ours — probed every five minutes from the estate itself, published whether or not it flatters us.

All systems operational

Every public service is answering normally.

Last checked

bitwarelabs.com This site and the contact form
Operational
15 ms · 100.00% (30 d)
45 days agotoday
bitwaretunes.com The label, catalogue and player
Operational
51 ms · 100.00% (30 d)
45 days agotoday
luna-v7.com Luna research agent and daybook
Operational
72 ms · 100.00% (30 d)
45 days agotoday
tv.bitwarelabs.com Media stack
Operational
30 ms · 100.00% (30 d)
45 days agotoday
Mail delivery Inbound SMTP for hosted domains
Operational
1 ms · 100.00% (30 d)
45 days agotoday

How this is measured

§ — Method

A cron job probes each service every five minutes. HTTP services get a full request with certificate verification on; the mail service gets a TCP connection and has to return a 220 greeting. A failed probe is retried once two seconds later before it counts — a single dropped packet is not an outage, and a status page that cries wolf is worse than none.

Anything slower than two seconds is recorded as degraded rather than down. Uptime is the share of successful checks over the last 30 days; the bars show one day each for the last 45, and grey means no data rather than no service.

The honest caveat

The probe runs on the estate. It confirms the services are answering, not that the route from your network to them is healthy — if the upstream link were down, this page would be unreachable and cheerfully green. It is deliberately not a substitute for external monitoring; it is the lab showing its own instrumentation.

Seeing something red that should not be, or green that should not be? Tell me.