Observealphastatus

Service status

Are FLOP's public services answering?

Source and guide ↗
flop status --help
Recorded fixture

Scheduled history is unavailable. Showing bundled observations with their original dates.

Archive checked . Page cache: 5 minutes.

Source records ↗ · Download displayed JSONL

pnpm --filter @flop-lab/cli exec flop status probe --json

Content checks passed

16 / 16 probes

HTTP 200 plus the expected content.

Recorded rounds

2

Each round attempts every listed service once.

Observed failure spans

0

Sample boundaries, not continuous downtime.

01 / Public responses

The answer and the evidence.

Sample availability = passed probes / measured probes. Each probe has equal weight. No sample means no data.

Selected window: to .

Observers: local-build-c18. Sparklines use actual capture times and a separate vertical scale per service.

Gateway

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

358 ms
0 to 496 ms · elapsed time · 2 samples

· https://api.flop.network/v1/models ↗

Hosted MCP

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

329 ms
0 to 444 ms · elapsed time · 2 samples

· https://mcp.flop.network/mcp ↗

Docs

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

699 ms
0 to 699 ms · elapsed time · 2 samples

· https://docs.flop.network/llms.txt ↗

Docs assistant

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

800 ms
0 to 1382 ms · elapsed time · 2 samples

· https://ask.flop.finance/mcp ↗

Explorer page

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

536 ms
0 to 536 ms · elapsed time · 2 samples

· https://explorer.devnet.flop.network/ ↗

Faucet page

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

518 ms
0 to 1084 ms · elapsed time · 2 samples

· https://faucet.flop.network/ ↗

Technocore health

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

502 ms
0 to 502 ms · elapsed time · 2 samples

· https://technocore.chat/healthz ↗

npm SDK metadata

Content passed

Latest HTTP 200

Sample availability

100.0%

2 / 2 measured probes

Latest elapsed time

420 ms
0 to 420 ms · elapsed time · 2 samples

· https://registry.npmjs.org/@flop-labs/sdk/latest ↗

02 / Failure observations

Where a probe stopped passing.

A span joins consecutive failed samples from the same observer. Gaps over 4.5 hours break the span. A later passing sample marks observed recovery only.

No failed samples in this window. No incident duration can be inferred.

03 / Read the boundary

A passing page is a narrow claim.

01

One request

A probe makes one fixed GET or MCP initialize request. It has a total deadline and a bounded body. Redirects and retries cannot hide a failed first attempt.

02

Check the content

Model ids, protocol information, page titles, health text and SDK metadata have explicit checks. MCP tools, inference, faucet funding and explorer queries are not exercised.

03

Keep the gaps visible

Only recorded samples enter availability. Scheduled history is designed for one round every three hours. Missed runs stay missing. These observations do not prove continuous uptime or chain health.