Hashly Status

All systems operational

Every service Hashly depends on answered its last check.

Operational

8 of 8

Uptime 30d

99.92%

all services

Incidents

since monitoring began

Last check

11:15 UTC

every 15 minutes

Monitoring since 16 Sep 2026. Days before that have no data, so the bars and the longer uptime figures fill in as it runs.

Hashly

Database

Operational

Every page, vote and profile is read from it.

Latency

46 ms

35 ms avg 24h

24h

100%

30d

99.96%

30 days ago60 days ago90 days agoToday

NFT market sync

Operational

Sales, floors and listings, written every fifteen minutes.

24h

100%

30d

99.93%

Newest hour 2h 15m old

30 days ago60 days ago90 days agoToday

Collection snapshots

Operational

The daily read of every active collection: traits, listings, holders.

24h

100%

30d

99.93%

Last write 6m ago · 810 collections today

30 days ago60 days ago90 days agoToday

Hedera

Hedera mirror node

Operational

Balances, holdings, voting power and wallet history.

Latency

118 ms

78 ms avg 24h

24h

100%

30d

100%

Newest block 3s old

30 days ago60 days ago90 days agoToday

HCS vote topic

Operational

Where every vote is recorded on-chain, read back through the mirror node.

Latency

98 ms

88 ms avg 24h

24h

100%

30d

100%

Latest vote 20m ago

30 days ago60 days ago90 days agoToday

Market data

SaucerSwap

Operational

Token prices, pools and charts.

Latency

198 ms

376 ms avg 24h

24h

100%

30d

100%

30 days ago60 days ago90 days agoToday

SentX

Operational

NFT floors, sales, listings and Forever Mints.

Latency

197 ms

255 ms avg 24h

24h

100%

30d

99.86%

30 days ago60 days ago90 days agoToday

GeckoTerminal

Operational

Token pools across Hedera DEXes.

Latency

275 ms

310 ms avg 24h

24h

100%

99.85%

30d

99.72%

30 days ago60 days ago90 days agoToday

Incidents

90 days

GeckoTerminalDegraded
1 Oct, 17:45 → 18:15 UTC · 2 checks
Slow: 3.9s
30m
NFT market syncDegraded
27 Sep, 06:00 → 06:30 UTC · 2 checks
Newest hour is 4h 15m old
30m

How this is measured

Every fifteen minutes a Hashly server in Stockholm asks each service for something small and real: a block, a token price, a floor. Hashly's own pipelines are judged by how fresh the data they write is.
Operational means it answered in under three seconds. Degraded means it answered slowly, rate limited or incompletely, or that the data is older than it should be. Down means no answer within eight seconds, or an error.
Uptime counts every check that was not down. A bar turns amber or red when two checks in a row failed; a single failed check lowers uptime but is not an incident.
Votes are read back from the HCS topic on the mirror node. Nothing is written on-chain to test it.
The current state is also available as JSON at /api/status.