Vendor Status Watch

← all vendors

SEOmonitor status history

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

2incidents, last 30 days
8incidents, last 90 days
51incidents on record
Incidents per week, last 12 weeks:

How long do SEOmonitor incidents last?

4.7 hmedian incident duration51 measured
7.8 days90th percentile1 in 10 ran longer
22.6 hmedian, major/critical only7 incidents

From 51 incidents with a vendor-posted start and resolve time. Longest on record: Issues with the 100 results crawl — 56.9 days (2026-02-11 16:12 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 (51)

StartedIncidentStatusImpactDuration
2026-09-12 06:40 UTCDelays in processing daily ranksresolvedminor9 min
2026-08-24 09:14 UTCDelays in processing daily ranksresolvedminor46 h 46 min
2026-07-29 12:40 UTCDelay in processing AIO citation data for Mobileresolvedminor5 d 21 h
2026-07-27 14:03 UTCDelays in processing daily ranksresolvedminor29 d 18 h
2026-07-07 13:43 UTCSlow loading times (or downtime) across the platformresolvedminor15 min
2026-07-06 07:06 UTCDelays in processing daily ranksresolvedminor26 h 17 min
2026-06-27 18:59 UTCIncident at our data storage provider causing downtime throughout the platformresolvedcritical36 h 56 min
2026-06-18 14:27 UTCSlow loading times (or downtime) across the platformresolvedminor5 min
2026-06-17 11:05 UTCSlow loading times (or downtime) across the platformresolvedminor10 min
2026-06-15 16:07 UTCSlow loading times (or downtime) across the platformresolvedminor9 min
2026-06-15 15:34 UTCSlow loading times (or downtime) across the platformresolvedminor15 min
2026-06-15 14:13 UTCSlow loading times (or downtime) across the platformresolvedminor14 min
2026-06-15 13:32 UTCSlow loading times (or downtime) across the platformresolvedminor5 min
2026-06-11 08:09 UTCDellays in article generationresolvedminor47 min
2026-06-10 16:47 UTCSlow loading times (or downtime) across the platformresolvedminor25 min
2026-05-13 14:22 UTCSlow loading times (or downtime) across the platformresolvedminor5 min
2026-05-12 20:26 UTCSlow loading times (or downtime) across the platformresolvedminor10 min
2026-05-12 14:13 UTCSlow loading times (or downtime) across the platformresolvedminor10 min
2026-05-11 16:59 UTCSlow loading times (or downtime) across the platformresolvedminor5 min
2026-05-11 16:21 UTCSlow loading times (or downtime) across the platformresolvedminor20 min
2026-05-11 14:22 UTCSlow loading times (or downtime) across the platformresolvedminor9 min
2026-04-16 08:36 UTCSecondary Device Rank Processing Delayresolvedminor4 h 41 min
2026-04-09 09:32 UTCDelays in processing new keywords and campaignsresolvedminor4 h 03 min
2026-03-19 17:57 UTCDatabase server issuesresolvedminor6 min
2026-03-19 10:33 UTCIssus with processing AI Search data for new keywordsresolvedminor21 h 23 min
2026-03-19 09:27 UTCSlow loading times (or downtime) across the platformresolvedminor10 min
2026-03-17 08:03 UTCDatabase server issuesresolvedminor1 h 27 min
2026-03-13 13:31 UTCSlow loading times (or downtime) across the platformresolvedminor5 min
2026-02-19 12:49 UTCIssues with detecting AI Overview dataresolvedminor7 d 19 h
2026-02-12 07:09 UTCDelays in processing new keywords and campaignsresolvedminor2 h 10 min
2026-02-11 16:12 UTCIssues with the 100 results crawlresolvedminor56 d 21 h
2026-02-11 08:48 UTCDelays in processing AI Search dataresolvedminor12 d 3 h
2026-01-28 23:26 UTCIncident with our data storage providerresolvedcritical9 h 28 min
2026-01-23 15:59 UTCDelays in processing new keywords and campaignsresolvedminor1 h 41 min
2026-01-12 10:25 UTCDelays in processing daily ranksresolvedminor28 h 04 min
2026-01-09 13:54 UTCDelays in processing new keywords and campaignsresolvedminor3 d 18 h
2026-01-08 13:32 UTCDelays in processing new keywords and campaignsresolvedminor19 h 14 min
2025-12-19 11:38 UTCIncident at one of our 3rd party providersresolvednone20 d 1 h
2025-12-13 07:00 UTCIssues with processing new ranksresolvedminor28 h 54 min
2025-12-09 10:40 UTCDesktop data issuesresolvedminor21 h 59 min
2025-12-01 13:29 UTCDelays in processing daily ranksresolvedmajor27 h 41 min
2025-11-25 15:15 UTCDelays in processing AI Search dataresolvedminor14 d 17 h
2025-11-18 12:09 UTCDowntime accross the entire platformresolvedcritical22 h 35 min
2025-11-04 13:21 UTCContent Writer AI Version not available due to latest updatesresolvedcritical25 min
2025-10-22 07:36 UTCDelays in processing daily ranksresolvednone7 h 58 min
2025-10-20 03:00 UTCDelays in processing payments and slow loading timesresolvedminor29 h 28 min
2025-09-17 07:24 UTCDelays in processing new keywords and campaignsresolvedminor28 h 38 min
2025-09-17 07:11 UTCCompetition section issuesresolvedminor28 h 39 min
2025-09-04 10:35 UTCDelays in processing new keywords and campaignsresolvedminor2 h 56 min
2025-09-01 21:43 UTCIncident at one of our 3rd party providers causing downtime throughout the platformresolvedmajor37 h 01 min
2025-08-24 21:32 UTCIncident at one of our 3rd party providers causing downtime throughout the platformresolvedmajor12 h 10 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 SEOmonitor with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "seomonitor"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}