Kagi

Affected: https://kagifeedback.org, https://orionfeedback.org

Failure mode: Security incident or emergency response to a vulnerability. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-21 12:57 UTC

   We're sorry for the inconvenience. Due to the php2shell security bug, we must turn on maintenance mode for feedback sites while waiting for the new PHP release. See more at

2. resolved 2026-10-21 16:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [Translate] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-21 09:38 UTC

   Kagi Translate in us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-21 09:39 UTC

   Kagi Translate in us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [Search] europe-west2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 06:07 UTC

   europe-west2 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. identified 2026-10-20 06:49 UTC

   We have identified the cause and are fixing it.

3. identified 2026-10-20 07:36 UTC

   We are continuing to work on a fix for this incident. In the meantime, the europe-west2 region has been temporarily removed from our global load balancer to reduce the negative impact on users.

4. resolved 2026-10-20 14:15 UTC

   europe-west2 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] europe-west2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 06:04 UTC

   [API] europe-west2 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. identified 2026-10-20 07:36 UTC

   We are continuing to work on a fix for this incident. In the meantime, the europe-west2 region has been temporarily removed from our global load balancer to reduce the negative impact on users.

3. resolved 2026-10-20 14:15 UTC

   [API] europe-west2 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] europe-west2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 10:28 UTC

   [API] europe-west2 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-19 10:29 UTC

   [API] europe-west2 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [Search] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 09:05 UTC

   us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-19 09:19 UTC

   us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: https://kagi.com/summarizer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-19 09:04 UTC

   https://kagi.com/summarizer cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-19 09:06 UTC

   https://kagi.com/summarizer is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 09:03 UTC

   [API] us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-19 09:06 UTC

   [API] us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 22:37 UTC

   API cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-14 22:58 UTC

   API is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-14 18:34 UTC

   API cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-14 18:45 UTC

   API is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-12 09:01 UTC

   [API] us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-12 09:03 UTC

   [API] us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: https://news.kagi.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-11 06:48 UTC

   https://news.kagi.com cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-11 06:49 UTC

   https://news.kagi.com is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [Translate] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 08:35 UTC

   Kagi Translate in us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-10-09 08:41 UTC

   Kagi Translate in us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] asia-east2

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-30 13:28 UTC

   [API] asia-east2 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-09-30 13:32 UTC

   [API] asia-east2 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: https://kagi.com/summarizer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-23 00:24 UTC

   https://kagi.com/summarizer cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-09-23 01:05 UTC

   https://kagi.com/summarizer is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-19 04:40 UTC

   [API] us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-09-19 04:41 UTC

   [API] us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [Search] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-12 09:24 UTC

   us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. identified 2026-09-12 10:08 UTC

   We are continuing to work on a fix for this incident.

3. identified 2026-09-12 10:08 UTC

   We are continuing to work on a fix for this incident.

4. resolved 2026-09-12 10:25 UTC

   us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] us-central1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-12 09:22 UTC

   [API] us-central1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-09-12 10:25 UTC

   [API] us-central1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [API] australia-southeast1

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 05:16 UTC

   [API] australia-southeast1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-09-11 05:18 UTC

   [API] australia-southeast1 is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: https://news.kagi.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-08 15:01 UTC

   https://news.kagi.com cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-09-08 15:02 UTC

   https://news.kagi.com is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: [Assistant] southamerica-east1, [Assistant] europe-west4, [Assistant] australia-southeast1, [Assistant] europe-west2, [Assistant] us-east4, [Assistant] us-central1, [Assistant] asia-east2, [Assistant] asia-southeast1, [Assistant] us-west2

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-01 14:47 UTC

   We have gotten reports of slow responses from the the Assistant, and responses timing out. We are currently investigating this incident.

2. resolved 2026-09-01 16:52 UTC

   We have rolled back to a previous version and are working to identify the cause of the issue.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: https://kagi.com/summarizer

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-27 08:02 UTC

   https://kagi.com/summarizer cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-08-27 08:14 UTC

   https://kagi.com/summarizer is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-26 11:47 UTC

   API cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-08-26 11:52 UTC

   API is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-20 14:00 UTC

   API cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-08-20 14:11 UTC

   API is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.

Affected: https://news.kagi.com

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-08-18 06:08 UTC

   https://news.kagi.com cannot be accessed at the moment. This incident was created by an automated monitoring service.

2. resolved 2026-08-18 06:10 UTC

   https://news.kagi.com is now operational! This update was created by an automated monitoring service.

Excerpts are shortened. Read the full incident on Kagi's status page.