NEWTickerr MCP is live →
tickerr
Swarmsourced · Tickerr
World's first swarmsourced LLM status platform
Partial OutageResolvedOfficial report

Kagi Partial Outage - May 31, 2026

Provider incident title: “Database maintenance for Kagi Search & Kagi Assistant

Share on X

Started

Sunday, May 31, 2026

06:00 AM UTC

Duration

1d 0h

total

Resolved

06:01 AM UTC

Jun 1, 2026

Severity: Partial Outage|Affected: Kagi|Duration: 1d 0h

Incident Timeline21 updates · oldest first

08:23 PM UTCInvestigating

Type: Incident Duration: 1 minute Affected Components: [Assistant] us-east4 May 19, 20:23:00 GMT+0 - Investigating - The Assistant in the us-east4 region is taking longer to respond then normal. This incident was created by an automated monitoring service. May 19, 20:24:13 GMT+0 - Resolved - \\\\\\\[Assistant\\\\\\\] us-east4 is now operational! This update was created by an automated monitoring service.

08:37 PM UTCInvestigating

Type: Incident Duration: 4 minutes Affected Components: [Assistant] australia-southeast1 May 19, 20:37:42 GMT+0 - Investigating - \\\[Assistant\\\] australia-southeast1 cannot be accessed at the moment. This incident was created by an automated monitoring service. May 19, 20:42:09 GMT+0 - Resolved - \\\[Assistant\\\] australia-southeast1 is now operational! This update was created by an automated monitoring service.

09:49 PM UTCInvestigating

Type: Incident Duration: 2 minutes Affected Components: [Assistant] asia-southeast1 May 19, 21:50:58 GMT+0 - Resolved - \\\\\\\[Assistant\\\\\\\] asia-southeast1 is now operational! This update was created by an automated monitoring service. May 19, 21:49:18 GMT+0 - Investigating - The Assistant in the asia-southeast1 region is taking longer to respond then normal. This incident was created by an automated monitoring service.

09:53 PM UTCInvestigating

Type: Incident Duration: 1 minute Affected Components: [Assistant] australia-southeast1 May 19, 21:53:17 GMT+0 - Investigating - \\\[Assistant\\\] australia-southeast1 cannot be accessed at the moment. This incident was created by an automated monitoring service. May 19, 21:54:37 GMT+0 - Resolved - \\\[Assistant\\\] australia-southeast1 is now operational! This update was created by an automated monitoring service.

10:19 PM UTCInvestigating

Type: Incident Duration: 3 minutes Affected Components: [Assistant] europe-west4 May 19, 22:19:32 GMT+0 - Investigating - The Assistant in the europe-west4 region is taking longer to respond then normal. This incident was created by an automated monitoring service. May 19, 22:22:17 GMT+0 - Resolved - \\\[Assistant\\\] europe-west4 is now operational! This update was created by an automated monitoring service.

11:00 PM UTCInvestigating

Type: Incident Duration: 1 minute Affected Components: [Assistant] us-west2 May 19, 23:00:21 GMT+0 - Investigating - The Assistant in the us-west2 region is taking longer to respond then normal. This incident was created by an automated monitoring service. May 19, 23:01:34 GMT+0 - Resolved - \\\[Assistant\\\] us-west2 is now operational! This update was created by an automated monitoring service.

05:29 AM UTCInvestigating

Type: Incident Duration: 3 minutes Affected Components: [Search] us-east4 May 21, 05:29:46 GMT+0 - Investigating - us-east4 cannot be accessed at the moment. This incident was created by an automated monitoring service. May 21, 05:33:02 GMT+0 - Resolved - us-east4 is now operational! This update was created by an automated monitoring service.

05:30 AM UTCInvestigating

Type: Incident Duration: 3 minutes Affected Components: [Assistant] us-east4 May 21, 05:30:28 GMT+0 - Investigating - The Assistant in the us-east4 region is taking longer to respond then normal. This incident was created by an automated monitoring service. May 21, 05:33:00 GMT+0 - Resolved - \\\\\\\[Assistant\\\\\\\] us-east4 is now operational! This update was created by an automated monitoring service.

05:33 AM UTCInvestigating

Type: Incident Affected Components: [Assistant] us-west2, [Assistant] asia-southeast1, [Assistant] europe-west2, [Assistant] southamerica-east1, [Search] asia-east2, [Search] europe-west4, [Search] us-west2, [Search] asia-southeast1, [Assistant] australia-southeast1, [Search] us-east4, [Search] australia-southeast1, [Assistant] europe-west4, [Assistant] us-east4, [Assistant] us-central1, [Search] us-central1, [Assistant] asia-east2, [Search] southamerica-east1, [Search] europe-west2 May 21, 05:33:35 GMT+0 - Identified - It's an unexpected behavior when maintaining the global routing rules. We identified the root cause and are waiting for recovery. May 21, 05:36:32 GMT+0 - Monitoring - We're sorry for the inconvenience. The services are back up, and we're still monitoring to make sure there are no sustained issues.

11:27 PM UTCInvestigating

Type: Incident Affected Components: [Assistant] southamerica-east1 May 21, 23:27:57 GMT+0 - Investigating - The Assistant in the southamerica-east1 region is taking longer to respond then normal. This incident was created by an automated monitoring service.

11:28 PM UTCInvestigating

Type: Incident Affected Components: [Search] southamerica-east1 May 21, 23:28:21 GMT+0 - Investigating - southamerica-east1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

12:51 AM UTCInvestigating

Type: Incident Affected Components: https://news.kagi.com May 24, 00:51:06 GMT+0 - Investigating - We noticed that the news generation has not finished in time for today, it should be available soon. This incident was created by an automated monitoring service.

04:36 PM UTCInvestigating

Type: Incident Duration: 2 minutes Affected Components: [Assistant] us-east4 May 24, 16:36:02 GMT+0 - Investigating - The Assistant in the us-east4 region is taking longer to respond then normal. This incident was created by an automated monitoring service. May 24, 16:37:51 GMT+0 - Resolved - \\\\\\\[Assistant\\\\\\\] us-east4 is now operational! This update was created by an automated monitoring service.

06:41 PM UTCInvestigating

Type: Incident Affected Components: [Assistant] us-east4 May 24, 18:41:30 GMT+0 - Investigating - The Assistant in the us-east4 region is taking longer to respond then normal. This incident was created by an automated monitoring service.

08:48 PM UTCInvestigating

Type: Incident Duration: 3 minutes Affected Components: [API] us-west2 May 25, 20:48:36 GMT+0 - Investigating - [API] us-west2 cannot be accessed at the moment. This incident was created by an automated monitoring service. May 25, 20:51:56 GMT+0 - Resolved - [API] us-west2 is now operational! This update was created by an automated monitoring service.

08:50 PM UTCInvestigating

Type: Incident Duration: 1 minute Affected Components: [Assistant] us-west2 May 25, 20:50:37 GMT+0 - Investigating - The Assistant in the us-west2 region is taking longer to respond then normal. This incident was created by an automated monitoring service. May 25, 20:51:51 GMT+0 - Resolved - \\\[Assistant\\\] us-west2 is now operational! This update was created by an automated monitoring service.

09:58 AM UTCInvestigating

Type: Incident Affected Components: [Assistant] us-east4 May 28, 09:58:05 GMT+0 - Investigating - The Assistant in the us-east4 region is taking longer to respond then normal. This incident was created by an automated monitoring service.

12:40 PM UTCInvestigating

Type: Incident Affected Components: Summarizer API May 29, 12:40:05 GMT+0 - Investigating - Our Summarize API (<https://kagi.com/api/v0/summarize>) is unstable. The number of 500 errors has started being high, we're looking into it.

07:07 PM UTCInvestigating

Type: Incident Duration: 5 minutes Affected Components: https://news.kagi.com May 29, 19:07:35 GMT+0 - Investigating - https://news.kagi.com cannot be accessed at the moment. This incident was created by an automated monitoring service. May 29, 19:12:08 GMT+0 - Resolved - https://news.kagi.com is now operational! This update was created by an automated monitoring service.

11:11 PM UTCInvestigating

Type: Incident Duration: 1 minute Affected Components: https://news.kagi.com May 29, 23:11:29 GMT+0 - Investigating - https://news.kagi.com cannot be accessed at the moment. This incident was created by an automated monitoring service. May 29, 23:12:37 GMT+0 - Resolved - https://news.kagi.com is now operational! This update was created by an automated monitoring service.

02:25 PM UTCInvestigating

Type: Incident Duration: 1 minute Affected Components: https://news.kagi.com May 30, 14:25:12 GMT+0 - Investigating - https://news.kagi.com cannot be accessed at the moment. This incident was created by an automated monitoring service. May 30, 14:26:31 GMT+0 - Resolved - https://news.kagi.com is now operational! This update was created by an automated monitoring service.

Get alerted next time

Install Tickerr MCP — your agent auto-reports & routes around outages

When Kagi goes down again, your agent reports anonymously and instantly gets a fallback recommendation from the swarm.

$claude mcp add tickerr --transport http --url https://tickerr.ai/mcp
Install free →

Kagi is back online

View current status and uptime history

Kagi status →

About This Report

Kagi 30-day uptime: 100% based on Tickerr's independent monitoring checks.

This incident was sourced from Kagi's official status RSS feed. Tickerr polls RSS feeds every 10 minutes and merges updates from the same outage into a single incident timeline.

This incident lasted 1d 0h.

Tickerr monitors 90+ AI tools independently. View live Kagi status or all AI tool status.

Other Kagi incidents

Jul 1, 2026
Jun 27, 2026
Jun 8, 2026
Jun 6, 2026
Jun 4, 2026

View all Kagi incident history →

Get alerted next time Kagi goes down

Tickerr monitors 90+ AI tools. We'll email you when an incident starts or resolves.

Weekly AI pricing & uptime digest

Price drops, new model releases, and incident summaries - every Monday. Free.

Also on Tickerr

Kagi live statusKagi pricingAll AI tool statusAI model pricingCompare AI toolsAI updates