SEEK status history
Current state: operational — “All Systems Operational” per https://status.seek.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do SEEK incidents last?
From 32 incidents with a vendor-posted start and resolve time. Longest on record: Ad Performance data delay — 38.8 h (2026-05-07 00:21 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (32)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-02 23:12 UTC | Delay in Ad Performance data | resolved | minor | 3 h 45 min |
| 2026-08-26 06:48 UTC | Delay in linking position opening to position profiles | resolved | major | 36 min |
| 2026-08-21 01:53 UTC | System Degredation | resolved | minor | 5 min |
| 2026-08-03 01:08 UTC | System degradation | resolved | none | 0 min |
| 2026-07-14 06:00 UTC | Degraded apply experience | resolved | minor | 13 min |
| 2026-07-14 06:00 UTC | Webhook missing | resolved | none | 0 min |
| 2026-07-13 20:00 UTC | Webhook delivery issue | resolved | none | 0 min |
| 2026-07-06 05:32 UTC | Partial network outage affecting degraded performances across services | resolved | minor | 13 min |
| 2026-06-30 03:26 UTC | Degraded candidate profile summaries view for hirers | resolved | minor | 11 min |
| 2026-06-22 00:42 UTC | SEEK API auth outage | resolved | major | 29 min |
| 2026-06-19 00:43 UTC | System degradation | resolved | major | 52 min |
| 2026-06-16 10:02 UTC | Delay in integration health data ingestion | resolved | major | 15 h 45 min |
| 2026-06-16 00:00 UTC | Degraded application attachment retrieval | resolved | none | 0 min |
| 2026-06-11 03:32 UTC | Profile summaries and verifications outage | resolved | critical | 15 min |
| 2026-06-10 00:00 UTC | Job querying outage | resolved | major | 1 h 26 min |
| 2026-06-09 01:27 UTC | System degredation | resolved | minor | 1 h 05 min |
| 2026-05-18 23:18 UTC | Ad Performance data delay | resolved | minor | 4 h 33 min |
| 2026-05-18 03:06 UTC | SEEK API performance degraded | resolved | minor | 2 h 00 min |
| 2026-05-07 00:21 UTC | Ad Performance data delay | resolved | minor | 38 h 48 min |
| 2026-04-24 03:54 UTC | Job posting edit degredation | resolved | none | 0 min |
| 2026-04-21 06:00 UTC | Apply with SEEK degredation | resolved | minor | 14 min |
| 2026-04-19 23:30 UTC | Job Posting Outage | resolved | none | 0 min |
| 2026-03-17 00:33 UTC | Major SEEK API Outage | resolved | critical | 1 h 28 min |
| 2026-03-12 23:38 UTC | Questionnaires outage | resolved | major | 22 min |
| 2026-02-09 00:22 UTC | Job posting partial outage | resolved | none | 5 min |
| 2026-02-04 23:47 UTC | Missing webhook events | resolved | none | 0 min |
| 2026-01-09 08:16 UTC | SEEK API elevated error rate | postmortem | critical | 2 h 08 min |
| 2025-12-15 04:03 UTC | Elevated API errors | resolved | minor | 12 min |
| 2025-12-10 03:00 UTC | Elevated API errors | resolved | minor | 2 h 57 min |
| 2025-10-01 23:30 UTC | SEEK web components partial outage | resolved | none | 0 min |
| 2025-08-15 02:04 UTC | Elevated errors during job posting | resolved | major | 3 h 17 min |
| 2025-08-14 01:53 UTC | Job posting partial outage | resolved | major | 6 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch SEEK with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"seek"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}