Uptime history
Healthy and degraded checks across monitored features. Gaps are excluded from uptime.
74.7% uptime
6 months
1 May 2026 UTCGray: no recorded checksNow
Vaulta Mainnet
aca376f206b8fc25a6ed44dbdc66547c36c6c33e3a119ffbeaef943642f0e906
https://api.eos.detroitledger.tech
Health, freshness, CORS, and recent check history for this endpoint.
- Producer
- eosiodetroit
- Chain
- Vaulta Mainnet
- Reported chain history
- Partial
- Location
- eos-api1-dlt
Current service health
Chain API
HealthyChain API responded normally
- Checked
- Latency
- 361 ms
- Browser requests
- Allowed
- Version
- Spring v1.2.2
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.2.2 | Chain API responded normally | 361 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 401 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 397 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 363 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 373 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 362 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 375 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 356 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 361 ms | Allowed | |
| Healthy | Spring v1.2.2 | Chain API responded normally | 361 ms | Allowed |
Account Query
Healthyaccount-query responded normally
- Checked
- Latency
- 487 ms
- Browser requests
- Allowed
- Version
- Spring v1.2.2
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Healthy | Spring v1.2.2 | account-query responded normally | 487 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 526 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 524 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 490 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 510 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 509 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 515 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 497 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 504 ms | Allowed | |
| Healthy | Spring v1.2.2 | account-query responded normally | 503 ms | Allowed |
History API
InvalidHTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json.
- Checked
- Latency
- 354 ms
- Browser requests
- Allowed
- Version
- Spring v1.2.2
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 354 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 356 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 395 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 360 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 361 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 360 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 368 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 354 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 356 ms | Allowed | |
| Invalid | Spring v1.2.2 | HTTP 404 on /v1/history/get_actions. The server has no route for this history-v1 check, so the advertised feature is not actually served. Fix the proxy routing or remove the feature from bp.json. | 359 ms | Allowed |
AtomicAssets API
UndisclosedDegradedAtomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy.
- Checked
- Latency
- 518 ms
- Browser requests
- Allowed
- Version
- 1.3.24
Recent checks
| Status | Version | Summary | Latency | CORS | Checked |
|---|---|---|---|---|---|
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 518 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 549 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 539 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 489 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 528 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 518 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 538 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 479 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 494 ms | Allowed | |
| Degraded | 1.3.24 | Atomic API modules unavailable: /atomictools/v1/config not found (HTTP 404/405). Enable the atomicassets, atomicmarket and atomictools namespaces and expose them through the proxy. | 493 ms | Allowed |