Ragie Outage History

Ragie is up right now

Pingoru has recorded 4 incidents for Ragie: 3 in the last 12 months and 0 in the last 90 days.

Source: ragie.statuspage.io

4incidents recorded
3last 12 months
0last 90 days
26 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Ragie in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 573 (0%)

Incidents, newest first

Major December 19, 2025 MCP Server Partial Outage 3d 5h API

Started Dec 19, 2025, 12:00 PM UTC· resolved Dec 22, 2025, 05:39 PM UTC

  1. investigating Dec 22, 2025, 05:37 PM UTC

    MCP tools are unavailble

  2. identified Dec 22, 2025, 05:38 PM UTC

    The root cause has been identified as a security patch that had unexpected interactions with Ragie's production environment.

  3. resolved Dec 22, 2025, 05:39 PM UTC

    We have deployed a fix.

Read the full incident report →

Critical December 6, 2025 Basechat application is currently unavailable 4m Basechat

Started Dec 06, 2025, 11:26 PM UTC· resolved Dec 06, 2025, 11:31 PM UTC

  1. investigating Dec 06, 2025, 11:26 PM UTC

    We are currently investigating this issue.

  2. identified Dec 06, 2025, 11:26 PM UTC

    The issue has been identified and a fix is being implemented.

  3. resolved Dec 06, 2025, 11:31 PM UTC

    We had a misconfigured DNS entry. This incident has now been resolved.

Read the full incident report →

Critical December 6, 2025 APIs and web app are unavailable 10m App, API, Basechat

Started Dec 06, 2025, 11:20 PM UTC· resolved Dec 06, 2025, 11:30 PM UTC

  1. investigating Dec 06, 2025, 11:20 PM UTC

    We are currently investigating this issue.

  2. identified Dec 06, 2025, 11:21 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified Dec 06, 2025, 11:23 PM UTC

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

  4. resolved Dec 06, 2025, 11:30 PM UTC

    We had a misconfigured DNS entry. This incident has now been resolved.

Read the full incident report →

Minor October 22, 2025 Retrieval Rerank - Degraded Performance –

Started Oct 22, 2025, 04:00 PM UTC· resolved Oct 22, 2025, 04:00 PM UTC

  1. resolved Oct 24, 2025, 06:37 PM UTC

    We are experiencing higher response times for reranking during retrieval.

Read the full incident report →