Status, freshness targets, and incident history.
Public status summarizes customer-visible API availability, result freshness, collection issues, and incident history.
Catalog games
195
Operationally tracked
195
Fresh result rows
171
Late or blocked
0
Current target
F3 2h
Coverage snapshot as of Sep 1, 2026, 08:07 AM UTC
API availability
This status page runs in the same application as the API. Independent uptime percentages are not published until external synthetic probes provide measured 7-, 30-, and 90-day evidence.
Collection summary
Current public feed state
Buckets summarize customer-visible collection states. Private source diagnostics and review notes are excluded.
0
Recent draw collection is following the expected schedule.
0% of observed rows
190
The draw is not due yet or is waiting for official publication.
94% of observed rows
0
The expected publish window is open and polling is active.
0% of observed rows
0
A result is past the expected window and remains under review.
0% of observed rows
0
A published source is temporarily unavailable for automated collection.
0% of observed rows
0
Repeated source errors are affecting collection for this game.
0% of observed rows
0
The game has not reported a clear collection state yet.
0% of observed rows
12
This collection state is tracked internally and summarized publicly.
6% of observed rows
0
This collection state is tracked internally and summarized publicly.
0% of observed rows
0
This collection state is tracked internally and summarized publicly.
0% of observed rows
0
This collection state is tracked internally and summarized publicly.
0% of observed rows
94
Source health score / 100
Source health score
Public reliability score backed by collection evidence
Most tracked games are either current or waiting for their normal draw window.
190
On track or waiting
0
Monitoring window
0
Blocked or failing
Source health uses public collection buckets only
The score is calculated from customer-visible status buckets for supported number games and distinguishes normal, watch, and degraded states.
On track or waiting
Rows that are current or not due yet improve the public score.
Monitoring window
Due, late, or unknown rows reduce the score gently because they can still recover inside the normal collection window.
Blocked or failing
Blocked and repeated-failure rows reduce the score more strongly because they can delay customer-visible latest-result and history data.
A source warning becomes a public incident only after blocked, failing, or late rows cross the public threshold and can affect customer-visible result delivery.
The score is a public summary, not an SLA. Private source diagnostics and credentials are excluded.
Data freshness
Schedule freshness is incomplete
12 of 202 customer-visible games do not have a recognized schedule state.
Newest draw date
2026-08-31
On schedule
190
Needs attention
0
Unknown state
12
Tracked lottery
Paused · latest stored draw 2026-07-29 (34 days old)
Tracked lottery
Paused · latest stored draw 2026-07-29 (34 days old)
Tracked lottery
Paused · latest stored draw 2026-07-29 (34 days old)
This customer-facing signal uses expected draw-window states. Latest draw dates are context only and do not define freshness for games with non-daily schedules.
Freshness policy
Plan delivery delays are separate from ingestion and uptime
The status page separates source publication, feed ingestion, plan delivery delay, and public cache refresh.
Clock start
F1-F7 measure plan delivery delay after the feed first stores or observes a result. Collection lag from official publication is measured separately.
No guarantee
F1-F7 are plan delivery-delay targets, not guarantees of ingestion speed or uptime. The delay clock starts after the feed first stores or observes a result; upstream publication and ingestion can add time before that point.
Official-source boundary
If an official lottery source delays publication, including during major jackpot events or additional validation processes, the feed can only publish after the official result becomes available.
Enterprise path
F7 applies a 5-minute plan delivery delay and is not included in standard subscriptions. It does not guarantee five-minute ingestion from draw time or official publication.
Freshness targets
Plan delivery delay starts after feed storage
The current standard subscription uses F3 2h access, applying a 2-hour plan delivery delay after the feed first stores or observes a result. F1-F7 are plan delivery-delay targets, not guarantees of ingestion speed or uptime. The delay clock starts after the feed first stores or observes a result; upstream publication and ingestion can add time before that point.
F1
Daily
after a 24-hour plan delivery delay
F2
4h
after a 4-hour plan delivery delay
F3
2h
after a 2-hour plan delivery delay
F4
1h
after a 1-hour plan delivery delay
F5
30m
after a 30-minute plan delivery delay
F6
15m
after a 15-minute plan delivery delay
F7
5m
after a 5-minute plan delivery delay
Target clock
F1-F7 measure plan delivery delay after the feed first stores or observes a result. Collection lag from official publication is measured separately.
Official-source boundary
If an official lottery source delays publication, including during major jackpot events or additional validation processes, the feed can only publish after the official result becomes available.
Near real-time
F7 applies a 5-minute plan delivery delay and is not included in standard subscriptions. It does not guarantee five-minute ingestion from draw time or official publication.
Incident history
Current and recent customer-visible incidents
This log shows customer-impacting service incidents and their current lifecycle state.
Incident history is a bounded customer-visible lifecycle log for service-impacting events.
No public customer-impacting incidents have been recorded in this product status log yet.
Individual source checks appear here only when there is a clear customer-visible impact.
Reliability FAQ
How to interpret status and freshness
These answers keep the public status page aligned with the API docs and customer integration guidance.
Are freshness targets service guarantees?
No. F1-F7 are plan delivery-delay targets, not guarantees of ingestion speed or uptime. The delay clock starts after the feed first stores or observes a result; upstream publication and ingestion can add time before that point. F1-F7 measure plan delivery delay after the feed first stores or observes a result. Collection lag from official publication is measured separately.
When does the freshness clock start?
F1-F7 measure plan delivery delay after the feed first stores or observes a result. Collection lag from official publication is measured separately.
Why can official lottery results still be delayed?
If an official lottery source delays publication, including during major jackpot events or additional validation processes, the feed can only publish after the official result becomes available.
What should API clients do during an incident?
Keep requests idempotent, respect retry and rate-limit headers, use cached latest results where acceptable, and avoid overwriting stored draws without comparing game_code, draw_date, and numbers_formatted.
Sample feed rows
Bounded watchlist preview
A compact sample helps customers understand the latest customer-visible game states.
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29
Tracked lottery
Latest stored draw: 2026-07-29