BreakingHistory made: Canada storm to their first-ever World Cup win, thrashing Qatar 6-0Updated daily · 7 AM Mountain TimeNext up · June 24 vs Switzerland
Canada Men's National TeamWorld Cup Squad Tracker

Platform operations · Canada MNT

System report · No. 06

Operations Dashboard

A public, sanitized view of platform health for the CMNT Squad Tracker. No secrets, ARNs, account IDs, or internal infrastructure details are exposed here.

Loading…Last refreshed Jun 2, 2026, 01:05 PM

Healthyoverall status

Platform Status

Overall statusHealthy
Environmentproduction
Last successful runJun 2, 2026, 01:04 PM
Data freshness417.5hwarn ≥ 24h
App versiona1b2c3d
Last site deployJun 19, 2026, 10:35 PM

Data Pipeline

Run duration1m 39s
Players processed46
Players updated44
API requests255
API failures2
Retry queue2
S3 uploadSuccess

Website · CloudFront

Edge metrics for the public site over the trailing 24h, plus a synthetic check of the homepage.

Requests (24h)4,218
4xx error rate0.71%
5xx error rate0%
Data transferred1.82 GB
Homepage probeHTTP 200
Response time64ms
TLS expires in68dcert validity

CloudWatch Alarms

Live state of the alarms wired to this platform — 0 firing of 3.

OK
cmnt-prod-cloudfront-5xx-rateCloudFront 5xx error rate is within budget
OK
cmnt-prod-data-stalenessplayers.json not updated in over 36 hours
OK
cmnt-prod-updater-errorsECS updater task logged errors or failed

Health Checks

passing
Updater PipelineScheduled ECS/Fargate updater completed successfully
passing
Player Data44 of 46 players refreshed with new club data
passing
S3 UploadGenerated JSON was published to the static site data path
passing
API Error Budget2 of 255 upstream API requests failed or were rate-limited
passing
HomepageSite reachable through CloudFront (HTTP 200, 64ms)

Operational Notes

Data freshness
Age of the latest published data, computed live from updatedAt. Warns past 24h, critical past 48h.
CloudWatch alarms
Live alarm state pulled at run time — updater errors, data staleness, and website 5xx — all routed to an SNS alert topic.
Synthetic canary
Each run probes the public homepage for reachability, response time, and TLS certificate days-to-expiry.
API failures
Expected occasionally — the upstream football API can be rate-limited or inconsistent. Handled by retry logic within an error budget.
Retry queue
Players that returned no fresh data and are retried by the next scheduled run (the updater is idempotent).
Sanitization
No secrets, API keys, account IDs, ARNs, or raw logs are exposed on this page.

How This Platform Runs

  1. EventBridge schedule triggers the nightly updater.
  2. ECS / Fargate runs the updater container.
  3. Updater calls api-football and refreshes the player JSON data.
  4. Refreshed data is uploaded to S3.
  5. CloudFront serves the static site and JSON data globally.
  6. CloudWatch metrics & alarms monitor the pipeline.