Agility CMS Outage History

Agility CMS is up right now

Agility CMS had 5 outages in the last 2 years totaling 32h 39m of downtime — averaging 0.2 incidents per month.

There were 5 Agility CMS outages since July 17, 2025 totaling 32h 39m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.agilitycms.com

Notice January 20, 2026

Management API Connection Issues in Canada

Detected by Pingoru
Jan 20, 2026, 02:15 PM UTC
Resolved
Jan 20, 2026, 09:33 PM UTC
Duration
7h 18m
Affected: Canada Region: Management API
Timeline · 7 updates
  1. investigating Jan 20, 2026, 02:15 PM UTC

    We are currently investigating an issue with connections to the Management API in Canada.

  2. identified Jan 20, 2026, 02:39 PM UTC

    We have identified the source of the issue, and service has been restored. We are continuing to investigate the issue.

  3. identified Jan 20, 2026, 02:59 PM UTC

    We are continuing to monitor this service, with potential mitigation steps currently in progress.

  4. identified Jan 20, 2026, 05:09 PM UTC

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

  5. monitoring Jan 20, 2026, 05:09 PM UTC

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

  6. monitoring Jan 20, 2026, 08:52 PM UTC

    Earlier today, we observed a service outage related to a specific type of API request that a customer of ours was performing. This API request was able to exhaust a specific storage container. We were able to restore services quickly and have now released a fix to prevent this kind of call from impacting any further services.

  7. resolved Jan 20, 2026, 09:33 PM UTC

    We have monitored the fix and are confident the issue has been resolved successfully

Read the full incident report →

Notice October 29, 2025

Monitoring Infrastructure

Detected by Pingoru
Oct 29, 2025, 04:20 PM UTC
Resolved
Oct 30, 2025, 12:27 AM UTC
Duration
8h 7m
Timeline · 5 updates
  1. monitoring Oct 29, 2025, 04:20 PM UTC

    We are observing issues among multiple cloud services. Our detection systems have not indicated any effects on our services, however we are continuing to monitor the situation

  2. monitoring Oct 29, 2025, 05:05 PM UTC

    We are continuing to Monitor the situation

  3. monitoring Oct 29, 2025, 05:53 PM UTC

    We are continuing to monitor the situation.

  4. monitoring Oct 29, 2025, 07:37 PM UTC

    Our Cloud provider as indicated that the issue has been resolved, we are still observing the situation

  5. resolved Oct 30, 2025, 12:27 AM UTC

    Cloud provider reporting normal operations

Read the full incident report →

Notice September 8, 2025

Issue with Swagger Docs

Detected by Pingoru
Sep 08, 2025, 08:24 PM UTC
Resolved
Sep 09, 2025, 01:03 PM UTC
Duration
16h 38m
Timeline · 3 updates
  1. identified Sep 08, 2025, 08:24 PM UTC

    We have identified an issue with our Swagger Docs returning 400s. We are working on a hotfix to be released shortly. This does not affect production API calls.

  2. monitoring Sep 08, 2025, 09:19 PM UTC

    A fix has been implemented and we are monitoring.

  3. resolved Sep 09, 2025, 01:03 PM UTC

    The issue has been resolved. Swagger Docs are working correctly now

Read the full incident report →

Notice August 27, 2025

Fetch API: Issue with attachments on content lists

Detected by Pingoru
Aug 27, 2025, 06:03 PM UTC
Resolved
Aug 27, 2025, 06:38 PM UTC
Duration
34m
Timeline · 2 updates
  1. monitoring Aug 27, 2025, 06:03 PM UTC

    We have identified an issue where image and file attachments on content lists are not resolving correctly. A fix has been implemented and we are monitoring the issue.

  2. resolved Aug 27, 2025, 06:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice July 17, 2025

Content Infrastructure Incident in EU

Detected by Pingoru
Jul 17, 2025, 01:30 PM UTC
Resolved
Jul 17, 2025, 01:30 PM UTC
Duration
Affected: Europe Region: Content Manager Web App
Timeline · 1 update
  1. resolved Jul 17, 2025, 01:30 PM UTC

    This incident has been resolved. Content updates published in the last 8 hours may have been effected in the EU region.

Read the full incident report →