Fetch AI Outage History

Fetch AI is up right now

Fetch AI had 15 outages in the last 2 years totaling 1805h 19m of downtime — averaging 0.6 incidents per month.

There were 15 Fetch AI outages since June 27, 2024 totaling 1805h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fetch.ai

Notice May 20, 2026

[Grafana] - [FIRING:1] Management PodCrashLooping Infra Monitoring

Detected by Pingoru
May 20, 2026, 02:11 AM UTC
Resolved
May 20, 2026, 02:16 AM UTC
Duration
4m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 20, 2026, 02:11 AM UTC

    **Firing** Value: B0=1 Labels: - alertname = Management PodCrashLooping - grafana_folder = Infra Monitoring Annotations: - summary = ethwatch-ethwatch-544cff579d-7cmzc Pod is in CLB in management Namespace Source: http://monitor.fetch-ai.com/alerting/grafana/ef9ffd4q26cqoa/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Def9ffd4q26cqoa&orgId=1

  2. resolved May 20, 2026, 02:16 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

[Grafana] - [FIRING:1] DatasourceNoData Ledger Monitoring (een50xvibpywwa A Alexandria Mainnet is Down)

Detected by Pingoru
May 20, 2026, 01:13 AM UTC
Resolved
May 20, 2026, 01:23 AM UTC
Duration
9m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 20, 2026, 01:13 AM UTC

    **Firing** Value: [no value] Labels: - alertname = DatasourceNoData - datasource_uid = een50xvibpywwa - grafana_folder = Ledger Monitoring - ref_id = A - rulename = Alexandria Mainnet is Down Annotations: - description = Alexandria is down in Mainnet - summary = Alexandria is down in Mainnet Source: http://monitor.fetch-ai.com/alerting/grafana/ceo80hs8yg8aob/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Dceo80hs8yg8aob&matcher=datasource_uid%3Deen50xvibpywwa&matcher=ref_id%3DA&matcher=rulename%3DAlexandria+Mainnet+is+Down&orgId=1

  2. resolved May 20, 2026, 01:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

[Grafana] - [FIRING:1] Mainnet PodCrashLooping Ledger Monitoring

Detected by Pingoru
May 20, 2026, 01:03 AM UTC
Resolved
May 20, 2026, 01:23 AM UTC
Duration
19m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 20, 2026, 01:03 AM UTC

    **Firing** Value: B0=1, B1=1 Labels: - alertname = Mainnet PodCrashLooping - grafana_folder = Ledger Monitoring Annotations: - summary = alexandria-6985946b5d-dqz84 Pod is in CLB in alexandria Namespace cache-db-0 Pod is in CLB in alexandria Namespace Source: http://monitor.fetch-ai.com/alerting/grafana/df9ff666qb1tsa/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Ddf9ff666qb1tsa&orgId=1

  2. resolved May 20, 2026, 01:23 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

[Grafana] - [FIRING:1] Prod-v2 PodCrashLooping Agentverse Monitoring

Detected by Pingoru
May 20, 2026, 12:23 AM UTC
Resolved
May 20, 2026, 12:33 AM UTC
Duration
10m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 20, 2026, 12:23 AM UTC

    **Firing** Value: B0=1 Labels: - alertname = Prod-v2 PodCrashLooping - grafana_folder = Agentverse Monitoring Annotations: - summary = elastic-sync-29653935-khd7r Pod is in CLB in toddleragi Namespace Source: http://monitor.fetch-ai.com/alerting/grafana/bf9ff97rxfqbkb/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Dbf9ff97rxfqbkb&orgId=1

  2. resolved May 20, 2026, 12:33 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

[Grafana] - [FIRING:1] fetchhub-node-sync-rpc0 Ledger Monitoring

Detected by Pingoru
May 20, 2026, 12:22 AM UTC
Resolved
May 20, 2026, 12:27 AM UTC
Duration
4m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 20, 2026, 12:22 AM UTC

    **Firing** Value: B0=0 Labels: - alertname = fetchhub-node-sync-rpc0 - grafana_folder = Ledger Monitoring Annotations: - summary = node-health-service.fetchhub-d.svc.cluster.local:80 is down Source: http://monitor.fetch-ai.com/alerting/grafana/deo7u6hbt5x4wf/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Ddeo7u6hbt5x4wf&orgId=1

  2. resolved May 20, 2026, 12:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 20, 2026

[Grafana] - [FIRING:1] Agents Memory Agents Monitoring

Detected by Pingoru
May 20, 2026, 12:02 AM UTC
Resolved
May 20, 2026, 12:07 AM UTC
Duration
5m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 20, 2026, 12:02 AM UTC

    **Firing** Value: B0=99.91770833333334 Labels: - alertname = Agents Memory - grafana_folder = Agents Monitoring Annotations: - summary = agents / agents-postgres-db-1: 99.91770833333334% Source: http://monitor.fetch-ai.com/alerting/grafana/bfcn049lokwzka/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Dbfcn049lokwzka&orgId=1

  2. resolved May 20, 2026, 12:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 19, 2026

[Grafana] - [FIRING:1] Prod LLM Proxy broken pipe alert Infra Monitoring

Detected by Pingoru
May 19, 2026, 10:30 PM UTC
Resolved
May 19, 2026, 10:35 PM UTC
Duration
5m
Affected: ASI1-mini
Timeline · 2 updates
  1. investigating May 19, 2026, 10:30 PM UTC

    **Firing** Value: B0=491 Labels: - alertname = Prod LLM Proxy broken pipe alert - grafana_folder = Infra Monitoring Annotations: - summary = write: broken pipe Error occurred in the last 5 min Source: http://monitor.fetch-ai.com/alerting/grafana/bfh686tibusqob/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Dbfh686tibusqob&orgId=1

  2. resolved May 19, 2026, 10:35 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 19, 2026

[Grafana] - [FIRING:1] Testnet Indexer CrashLoopBackOff pod alert Ledger Monitoring

Detected by Pingoru
May 19, 2026, 04:42 PM UTC
Resolved
May 19, 2026, 09:22 PM UTC
Duration
4h 39m
Affected: ASI1-mini
Timeline · 3 updates
  1. investigating May 19, 2026, 04:42 PM UTC

    **Firing** Value: B0=1 Labels: - alertname = Testnet Indexer CrashLoopBackOff pod alert - grafana_folder = Ledger Monitoring Annotations: - description = Pod [no value]/[no value] ([no value]) is in waiting state (reason: "CrashLoopBackOff"). - summary = Indexer Pod is crash looping. Source: http://monitor.fetch-ai.com/alerting/grafana/aeo87b93us1dse/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Daeo87b93us1dse&orgId=1

  2. identified May 19, 2026, 04:49 PM UTC

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

  3. resolved May 19, 2026, 09:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 19, 2026

[Grafana] - [FIRING:1] Spike Unacknowledged Msg Infra Monitoring

Detected by Pingoru
May 19, 2026, 02:06 PM UTC
Resolved
May 19, 2026, 02:11 PM UTC
Duration
5m
Affected: ASI1-mini
Timeline · 3 updates
  1. investigating May 19, 2026, 02:06 PM UTC

    **Firing** Value: B0=121 Labels: - alertname = Spike Unacknowledged Msg - grafana_folder = Infra Monitoring Annotations: - summary = agent_data_queue queue in toddleragi namespace Unacknowledged messages are above: 121% Source: http://monitor.fetch-ai.com/alerting/grafana/aeo46mdlhdhq8c/view?orgId=1 Silence: http://monitor.fetch-ai.com/alerting/silence/new?alertmanager=grafana&matcher=__alert_rule_uid__%3Daeo46mdlhdhq8c&orgId=1

  2. identified May 19, 2026, 02:07 PM UTC

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

  3. resolved May 19, 2026, 02:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Major September 13, 2024

Database connection issues following update

Detected by Pingoru
Sep 13, 2024, 11:18 AM UTC
Resolved
Sep 13, 2024, 12:05 PM UTC
Duration
46m
Affected: Agentverse - Hosting
Timeline · 2 updates
  1. investigating Sep 13, 2024, 11:18 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 13, 2024, 12:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 8, 2024

Users reported instability with hosted agents

Detected by Pingoru
Jul 08, 2024, 01:00 PM UTC
Resolved
Aug 12, 2024, 10:39 AM UTC
Duration
34d 21h
Affected: Agentverse - Hosting
Timeline · 3 updates
  1. investigating Jul 08, 2024, 01:00 PM UTC

    We are currently investigating this issue.

  2. investigating Jul 08, 2024, 02:23 PM UTC

    Updated hosting-api. Interactions are temporarily unavailable until later update.

  3. resolved Aug 12, 2024, 10:39 AM UTC

    Stability issues have been resolved.

Read the full incident report →

Major July 5, 2024

Potential Outage for Fetchub REST Endpoints

Detected by Pingoru
Jul 05, 2024, 03:34 PM UTC
Resolved
Jul 05, 2024, 05:45 PM UTC
Duration
2h 11m
Affected: rest-fetchhub.fetch.aiFetchhub - node sync - rest0Fetchhub - node sync - rest1
Timeline · 3 updates
  1. investigating Jul 05, 2024, 03:34 PM UTC

    We are currently investigating this issue.

  2. monitoring Jul 05, 2024, 05:32 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 05, 2024, 05:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 4, 2024

Potential issue with Hosted Agents not registering to Almanac

Detected by Pingoru
Jul 04, 2024, 10:57 AM UTC
Resolved
Aug 12, 2024, 10:39 AM UTC
Duration
38d 23h
Affected: Agentverse - Hosting
Timeline · 4 updates
  1. investigating Jul 04, 2024, 10:57 AM UTC

    We are currently investigating this issue.

  2. identified Jul 04, 2024, 11:35 AM UTC

    We discovered a potential issue with some hosted agents. This is not affecting any public users.

  3. identified Aug 12, 2024, 10:38 AM UTC

    Issues have been resolved.

  4. resolved Aug 12, 2024, 10:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Major July 3, 2024

Hosted agents not reachable from outside

Detected by Pingoru
Jul 03, 2024, 10:27 AM UTC
Resolved
Jul 04, 2024, 07:05 AM UTC
Duration
20h 37m
Affected: Agentverse - Hosting
Timeline · 4 updates
  1. investigating Jul 03, 2024, 10:27 AM UTC

    AI Engine / DeltaV / non agentverse agent shows agent offline/unreachable for Agentverse hosted agents. We are investigating, fix expected later on today.

  2. identified Jul 03, 2024, 05:26 PM UTC

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

  3. identified Jul 04, 2024, 07:00 AM UTC

    uAgents 0.13 has been released and it solves the issue about not being able to send message to hosted agents. Corresponding fetch-ai-engine 0.3.0 has also been released. AI Engine dependency on uAgents has been updated and released. Agent communication with hosted agent should work now from AI Engine/DeltaV. If you send message from local agent to hosted agent please update the uAgents package.

  4. resolved Jul 04, 2024, 07:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice June 27, 2024

Agentverse Upgrade

Detected by Pingoru
Jun 27, 2024, 02:13 PM UTC
Resolved
Jun 27, 2024, 04:52 PM UTC
Duration
2h 38m
Affected: Agentverse - WebsiteAgentverse - HostingAgentverse - MailboxAgentverse - Almanac
Timeline · 2 updates
  1. identified Jun 27, 2024, 02:13 PM UTC

    Fetch.ai Agentverse upgrade is under maintenance. A few Agentverse services might be unresponsive during the upgrade.

  2. resolved Jun 27, 2024, 04:52 PM UTC

    This incident has been resolved.

Read the full incident report →