All monitored services are currently healthy.
| Check | Status | Latency | Last update |
|---|---|---|---|
|
health http: HTTP 200 from chat.datapulse.global (x-health-status=healthy) |
healthy | 27.4 ms | 2026-09-22 14:25:48 UTC |
|
http3 quicprobe • informational: HTTP/3 supported on chat.datapulse.global (ALPN h3, TLS 1.3, 94 ms) probe_host=chat.datapulse.global • supported=true • alpn=h3 • tls_version=TLS 1.3 • server_addr=67.175.33.63:443 • handshake_ms=94 |
supported | 98.8 ms | 2026-09-22 14:23:18 UTC |
|
ping4 ping: ipv4 ping succeeded for chat.datapulse.global |
healthy | 94.6 ms | 2026-09-22 14:25:18 UTC |
|
ping6 ping: ipv6 ping succeeded for chat.datapulse.global |
healthy | 100.7 ms | 2026-09-22 14:25:18 UTC |
|
tls-cert tls: certificate valid for 87.1 days |
healthy | 81.2 ms | 2026-09-22 14:03:18 UTC |
| Check | Status | Latency | Last update |
|---|---|---|---|
|
health http: HTTP 200 from mcp.datapulse.global (x-health-status=healthy) |
healthy | 22.6 ms | 2026-09-22 14:25:48 UTC |
|
http3 quicprobe • informational: HTTP/3 supported on mcp.datapulse.global (ALPN h3, TLS 1.3, 61 ms) probe_host=mcp.datapulse.global • supported=true • alpn=h3 • tls_version=TLS 1.3 • server_addr=67.175.33.63:443 • handshake_ms=61 |
supported | 65.5 ms | 2026-09-22 14:23:18 UTC |
|
ping4 ping: ipv4 ping succeeded for mcp.datapulse.global |
healthy | 93.8 ms | 2026-09-22 14:25:18 UTC |
|
ping6 ping: ipv6 ping succeeded for mcp.datapulse.global |
healthy | 102.4 ms | 2026-09-22 14:25:18 UTC |
|
tls-cert tls: certificate valid for 86.2 days |
healthy | 147.1 ms | 2026-09-22 14:03:18 UTC |
| Check | Status | Latency | Last update |
|---|---|---|---|
|
health http: HTTP 200 from content-api.datapulse.global |
healthy | 20.9 ms | 2026-09-22 14:25:48 UTC |
|
tls-cert tls: certificate valid for 171.4 days |
healthy | 27.0 ms | 2026-09-22 14:03:18 UTC |
No active incidents.
HTTP 200 from mcp.datapulse.global (x-health-status=healthy)
2026-09-20 15:10:48 UTC
HTTP 200 from chat.datapulse.global (x-health-status=healthy)
2026-09-20 15:06:18 UTC
unexpected HTTP status 502
2026-09-20 15:03:51 UTC
unexpected HTTP status 502
2026-09-20 15:03:51 UTC
HTTP 200 from mcp.datapulse.global (x-health-status=healthy)
2026-09-19 08:36:18 UTC
response header "x-health-status" = "unhealthy", expected "healthy"
2026-09-19 08:27:18 UTC
HTTP 200 from mcp.datapulse.global (x-health-status=healthy)
2026-09-17 03:26:48 UTC
response header "x-health-status" = "unhealthy", expected "healthy"
2026-09-17 03:23:18 UTC
HTTP 200 from chat.datapulse.global (x-health-status=healthy)
2026-09-17 02:13:54 UTC
response header "x-health-status" = "unhealthy", expected "healthy"
2026-09-17 02:13:25 UTC
HTTP 200 from chat.datapulse.global (x-health-status=healthy)
2026-09-17 02:08:18 UTC
request failed: Head "https://chat.datapulse.global/health": context deadline exceeded
2026-09-17 02:07:58 UTC
HTTP 200 from mcp.datapulse.global (x-health-status=healthy)
2026-09-17 01:01:52 UTC
HTTP 200 from chat.datapulse.global (x-health-status=healthy)
2026-09-17 01:00:18 UTC
request failed: Head "https://chat.datapulse.global/health": context deadline exceeded
2026-09-17 00:59:58 UTC
response header "x-health-status" = "unhealthy", expected "healthy"
2026-09-17 00:35:18 UTC
HTTP 200 from chat.datapulse.global (x-health-status=healthy)
2026-09-16 22:38:48 UTC
request failed: Head "https://chat.datapulse.global/health": context deadline exceeded
2026-09-16 22:38:28 UTC
HTTP 200 from chat.datapulse.global (x-health-status=healthy)
2026-09-16 22:36:48 UTC
HTTP 200 from mcp.datapulse.global (x-health-status=healthy)
2026-09-16 22:36:22 UTC
Published by ip-172-31-50-36.us-east-2.compute.internal • https://status.labs.datapulse.global/