Platform is healthy
All monitored checks are within their thresholds.
- Last check
- 40s ago
- Open alerts
- 0
- Snapshots
- 38,435
Platform
Measured by calling the public API the way a candidate would.
API status
200
Responding normally
API response time
210ms
End-to-end, including TLS
Healthy API targets
3
API target group
API tasks running
3
of 3 desired
API traffic
The API target group in the last published minute.
Requests
0
Avg response
No data
The source was reachable but published nothing for this period.
Client errors (4xx)
0
Server errors (5xx)
0
Web frontend traffic
The Next.js target group, counted separately — it shares the load balancer with the API, so a frontend fault would otherwise read as an API fault.
Requests
0
Avg response
No data
The source was reachable but published nothing for this period.
Client errors (4xx)
0
Server errors (5xx)
0
Resources
Headroom on the API containers and the database.
API CPU
3.3%
API memory
52.1%
Database CPU
3.8%
DB connections
9
DB free memory
734 MB
Last 6 hours
Gaps mean the collector was not running.
API response time
Round trip to api.talilink.com
Requests and errors
Per published minute at the load balancer
Container utilisation
ECS service averages
Database
RDS CPU and open connections
Open alerts
Conditions currently breaching a threshold, with the AI's read on each.
Nothing is alerting
Every monitored condition is within its threshold right now.
Collection problems
Data the collector could not gather on its last run. Treat these figures as unknown, not healthy.
- /api/metrics/communications returned HTTP 401
- /api/metrics/pipeline-funnel returned HTTP 401
- /api/metrics/registrations returned HTTP 401