Vendor Status Watch

← all vendors

SEEK status history

Current state: operational — “All Systems Operational” per https://status.seek.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

3incidents, last 30 days
11incidents, last 90 days
32incidents on record
Incidents per week, last 12 weeks:

How long do SEEK incidents last?

14 minmedian incident duration32 measured
3.8 h90th percentile1 in 10 ran longer
52 minmedian, major/critical only11 incidents

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)

StartedIncidentStatusImpactDuration
2026-09-02 23:12 UTCDelay in Ad Performance dataresolvedminor3 h 45 min
2026-08-26 06:48 UTCDelay in linking position opening to position profilesresolvedmajor36 min
2026-08-21 01:53 UTCSystem Degredationresolvedminor5 min
2026-08-03 01:08 UTCSystem degradationresolvednone0 min
2026-07-14 06:00 UTCDegraded apply experienceresolvedminor13 min
2026-07-14 06:00 UTCWebhook missingresolvednone0 min
2026-07-13 20:00 UTCWebhook delivery issueresolvednone0 min
2026-07-06 05:32 UTCPartial network outage affecting degraded performances across servicesresolvedminor13 min
2026-06-30 03:26 UTCDegraded candidate profile summaries view for hirersresolvedminor11 min
2026-06-22 00:42 UTCSEEK API auth outageresolvedmajor29 min
2026-06-19 00:43 UTCSystem degradationresolvedmajor52 min
2026-06-16 10:02 UTCDelay in integration health data ingestionresolvedmajor15 h 45 min
2026-06-16 00:00 UTCDegraded application attachment retrievalresolvednone0 min
2026-06-11 03:32 UTCProfile summaries and verifications outageresolvedcritical15 min
2026-06-10 00:00 UTCJob querying outageresolvedmajor1 h 26 min
2026-06-09 01:27 UTCSystem degredationresolvedminor1 h 05 min
2026-05-18 23:18 UTCAd Performance data delayresolvedminor4 h 33 min
2026-05-18 03:06 UTCSEEK API performance degradedresolvedminor2 h 00 min
2026-05-07 00:21 UTCAd Performance data delayresolvedminor38 h 48 min
2026-04-24 03:54 UTCJob posting edit degredationresolvednone0 min
2026-04-21 06:00 UTCApply with SEEK degredationresolvedminor14 min
2026-04-19 23:30 UTCJob Posting Outageresolvednone0 min
2026-03-17 00:33 UTCMajor SEEK API Outageresolvedcritical1 h 28 min
2026-03-12 23:38 UTCQuestionnaires outageresolvedmajor22 min
2026-02-09 00:22 UTCJob posting partial outageresolvednone5 min
2026-02-04 23:47 UTCMissing webhook eventsresolvednone0 min
2026-01-09 08:16 UTCSEEK API elevated error ratepostmortemcritical2 h 08 min
2025-12-15 04:03 UTCElevated API errorsresolvedminor12 min
2025-12-10 03:00 UTCElevated API errorsresolvedminor2 h 57 min
2025-10-01 23:30 UTCSEEK web components partial outageresolvednone0 min
2025-08-15 02:04 UTCElevated errors during job postingresolvedmajor3 h 17 min
2025-08-14 01:53 UTCJob posting partial outageresolvedmajor6 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
}