Cookiefirst incident

Consent Api + Listing down

Resolved after 2 hours 3 minutes, affecting section-100675 (Consent Saving API) and section-100675 (Cookie listing API endpoint), on February 27, 2025.

investigating Feb 27, 2025, 09:19 AM UTC

The Consent API endpoint went down because a server node was being replaced. During this time, the server was unresponsive, returning no headers or data. Total downtime was 25 minutes. Consents we're stored in logs and re-entered in to the database when the servers were back online.

Started
Feb 27, 2025, 09:19 AM UTC
Resolved
Feb 27, 2025, 11:22 AM UTC
Duration
2h 3m
Detected by Pingoru
Feb 27, 2025, 09:19 AM UTC

Affected components

section-100675 (Consent Saving API)section-100675 (Cookie listing API endpoint)

Update timeline

  1. investigating Feb 27, 2025, 09:19 AM UTC

    The Consent API endpoint went down because a server node was being replaced. During this time, the server was unresponsive, returning no headers or data. Total downtime was 25 minutes. Consents we're stored in logs and re-entered in to the database when the servers were back online.

  2. resolved Feb 27, 2025, 11:22 AM UTC

    The issue was fixed once database node was replaced.

Your product runs on more than Cookiefirst

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →