HomeBloks System Status

Bridging real estate and blockchain with transparent system health
HomeBloks Logo

Live System Status

BrokerIDXsites Admin

Status: ✅Up
Response Time: 245ms
24h Average: 242.2ms

Websites Server

Status: ✅Up
Response Time: 11,355ms
24h Average: 354.1ms

Websites Server 2

Status: ✅Up
Response Time: 10,441ms
24h Average: 276.6ms

Master Database Server

Status: ✅Up
Response Time: 13ms
24h Average: 58.6ms

Slave Database Server

Status: ✅Up
Response Time: 377ms
24h Average: 329.0ms

BlastPad

Status: ✅Up
Response Time: 29ms
24h Average: 22.8ms

Performance History

BrokerIDXsites Admin

Websites Server

Websites Server 2

Master Database Server

Slave Database Server

BlastPad

Recent Incident Alerts

⚠️Warning at 11:30 PM EDT2026-04-02 23:30:23
Websites Server 2 is experiencing excessive loading, beginning at 11:30pm EDT. Our team has been alerted to the issue and are currently responding.
⚠️Warning at 11:30 PM EDT2026-04-02 23:30:13
Websites Server is experiencing excessive loading, beginning at 11:30pm EDT. Our team has been alerted to the issue and are currently responding.
ℹ️Info at 7:42 PM EDT2026-04-02 19:42:03
Master Database Server response times have returned to normal levels. The performance issue has been resolved.
⚠️Warning at 7:36 PM EDT2026-04-02 19:36:04
Master Database Server is experiencing excessive loading, beginning at 7:36pm EDT. Our team has been alerted to the issue and are currently responding.
✅Service Recovered - BrokerIDXsites Admin2026-04-02 15:42:01
BrokerIDXsites Admin is back online as of 3:42pm EDT on 4/2/2026. The service outage has been resolved. Resolved from TIMEOUT.
🔴Service Outage - BrokerIDXsites Admin2026-04-02 15:38:01
BrokerIDXsites Admin is currently down as of 3:38pm EDT on 4/2/2026. Our team has been alerted to the issue and are currently responding. Current diagnosis: Request timed out while waiting for response (TIMEOUT).
Diagnosis: Request timed out while waiting for response
ℹ️Info at 10:24 AM EDT2026-04-02 10:24:02
Master Database Server response times have returned to normal levels. The performance issue has been resolved.
⚠️Warning at 10:18 AM EDT2026-04-02 10:18:04
Master Database Server is experiencing excessive loading, beginning at 10:18am EDT. Our team has been alerted to the issue and are currently responding.
ℹ️Info at 5:54 AM EDT2026-04-02 05:54:06
BrokerIDXsites Admin is up and functioning properly. No issues detected in the past 24 hours.
ℹ️Info at 3:54 AM EDT2026-04-02 03:54:05
Slave Database Server is up and functioning properly. No issues detected in the past 24 hours.

Detailed Uptime History

BrokerIDXsites Admin

Timestamp Status Response Time (ms) ⓘ Down Reason
2026-04-02T23:30:01-04:00 up 244.82 —
2026-04-02T23:24:02-04:00 up 258.95 —
2026-04-02T23:18:02-04:00 up 244.82 —
2026-04-02T23:12:02-04:00 up 238.89 —
2026-04-02T23:06:01-04:00 up 225.12 —
2026-04-02T23:00:02-04:00 up 251.70 —
2026-04-02T22:54:02-04:00 up 226.13 —
2026-04-02T22:48:01-04:00 up 247.50 —
2026-04-02T22:42:02-04:00 up 234.46 —
2026-04-02T22:36:02-04:00 up 249.37 —

Websites Server

Timestamp Status Response Time (ms) ⓘ Down Reason
2026-04-02T23:30:13-04:00 up 11,355.07 —
2026-04-02T23:24:02-04:00 up 307.54 —
2026-04-02T23:18:02-04:00 up 27.45 —
2026-04-02T23:12:02-04:00 up 294.74 —
2026-04-02T23:06:02-04:00 up 294.32 —
2026-04-02T23:00:02-04:00 up 293.41 —
2026-04-02T22:54:02-04:00 up 330.59 —
2026-04-02T22:48:02-04:00 up 297.82 —
2026-04-02T22:42:02-04:00 up 351.70 —
2026-04-02T22:36:02-04:00 up 287.97 —

Websites Server 2

Timestamp Status Response Time (ms) ⓘ Down Reason
2026-04-02T23:30:23-04:00 up 10,440.64 —
2026-04-02T23:24:02-04:00 up 225.72 —
2026-04-02T23:18:02-04:00 up 27.90 —
2026-04-02T23:12:03-04:00 up 234.20 —
2026-04-02T23:06:02-04:00 up 247.73 —
2026-04-02T23:00:02-04:00 up 253.99 —
2026-04-02T22:54:03-04:00 up 281.67 —
2026-04-02T22:48:02-04:00 up 242.68 —
2026-04-02T22:42:02-04:00 up 257.35 —
2026-04-02T22:36:03-04:00 up 241.70 —

Master Database Server

Timestamp Status Response Time (ms) ⓘ Down Reason
2026-04-02T23:30:23-04:00 up 13.44 —
2026-04-02T23:24:02-04:00 up 12.58 —
2026-04-02T23:18:02-04:00 up 11.85 —
2026-04-02T23:12:03-04:00 up 12.78 —
2026-04-02T23:06:02-04:00 up 12.62 —
2026-04-02T23:00:02-04:00 up 12.86 —
2026-04-02T22:54:03-04:00 up 13.06 —
2026-04-02T22:48:02-04:00 up 12.49 —
2026-04-02T22:42:02-04:00 up 13.20 —
2026-04-02T22:36:03-04:00 up 11.11 —

Slave Database Server

Timestamp Status Response Time (ms) ⓘ Down Reason
2026-04-02T23:30:24-04:00 up 376.84 —
2026-04-02T23:24:03-04:00 up 459.02 —
2026-04-02T23:18:02-04:00 up 381.68 —
2026-04-02T23:12:03-04:00 up 376.78 —
2026-04-02T23:06:02-04:00 up 376.67 —
2026-04-02T23:00:03-04:00 up 367.83 —
2026-04-02T22:54:03-04:00 up 376.72 —
2026-04-02T22:48:02-04:00 up 391.23 —
2026-04-02T22:42:03-04:00 up 477.58 —
2026-04-02T22:36:03-04:00 up 315.66 —

BlastPad

Timestamp Status Response Time (ms) ⓘ Down Reason
2026-04-02T23:30:24-04:00 up 29.40 —
2026-04-02T23:24:03-04:00 up 21.00 —
2026-04-02T23:18:02-04:00 up 21.94 —
2026-04-02T23:12:03-04:00 up 20.27 —
2026-04-02T23:06:02-04:00 up 25.47 —
2026-04-02T23:00:03-04:00 up 26.62 —
2026-04-02T22:54:03-04:00 up 25.29 —
2026-04-02T22:48:02-04:00 up 25.92 —
2026-04-02T22:42:03-04:00 up 26.51 —
2026-04-02T22:36:03-04:00 up 24.48 —