Celigo Outage History

Celigo is up right now

Pingoru has recorded 14 incidents for Celigo: 0 in the last 12 months and 0 in the last 90 days.

Source: status.celigo.com

14incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Celigo 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 528 (0%)

Incidents, newest first

Major October 20, 2025 integrator.io degraded performance 13h 48m integrator.io

Started Oct 20, 2025, 07:30 AM UTC· resolved Oct 20, 2025, 09:19 PM UTC

  1. investigating Oct 20, 2025, 11:29 AM UTC

    We are seeing an increased error rates in our application.

  2. investigating Oct 20, 2025, 11:31 AM UTC

    There is an ongoing issue with our cloud provider, AWS, in the us-east-1 region, and we are experiencing some performance degradation in our service as a result.

  3. identified Oct 20, 2025, 11:33 AM UTC

    AWS has identified the root cause for the issue and is working on mitigating the same.

  4. identified Oct 20, 2025, 11:35 AM UTC

    AWS has identified the root cause and provided initial mitigations.

  5. monitoring Oct 20, 2025, 11:37 AM UTC

    We are still seeing issues with some of the AWS services and they are still working on it.

  6. monitoring Oct 20, 2025, 12:57 PM UTC

    Most of the services are back to normal and we are still seeing some issues with scaling due to new EC2 intances provisioning issue. AWS is still working on resolving it.

  7. monitoring Oct 20, 2025, 05:52 PM UTC

    We are continuing to monitor as AWS is still working on the AWS EC2 instances provisioning.

  8. resolved Oct 20, 2025, 09:19 PM UTC

    Earlier today, AWS experienced increased error rates and latencies across multiple services in the US-EAST-1 region. The issue was traced to AWS’s internal Domain Name System (DNS), which impacted connectivity and caused downstream disruptions for several AWS services and dependent applications. AWS has implemented a fix, and the Celigo platform has recovered. Backlogs have been processed successfully, and we are closely monitoring the situation. We sincerely apologize for any disruption this incident may have caused and appreciate your patience and understanding.

Read the full incident report →

Major May 2, 2025 Partial degradation of API routes (EU) –

Started May 02, 2025, 07:00 AM UTC· resolved May 02, 2025, 07:00 AM UTC

  1. resolved May 02, 2025, 08:11 AM UTC

    We are currently investigating this issue.

Read the full incident report →

Major April 9, 2025 Issue with Flow processing 1h 59m integrator.io

Started Apr 09, 2025, 01:07 PM UTC· resolved Apr 09, 2025, 03:07 PM UTC

  1. identified Apr 09, 2025, 01:07 PM UTC

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

  2. monitoring Apr 09, 2025, 02:48 PM UTC

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

  3. monitoring Apr 09, 2025, 03:01 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Apr 09, 2025, 03:07 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 21, 2024 Flows are in stuck status 5h 47m integrator.io

Started Nov 21, 2024, 09:13 PM UTC· resolved Nov 22, 2024, 03:01 AM UTC

  1. investigating Nov 21, 2024, 09:13 PM UTC

    We are currently investigating this issue.

  2. investigating Nov 21, 2024, 09:14 PM UTC

    We are continuing to investigate this issue.

  3. identified Nov 21, 2024, 09:53 PM UTC

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

  4. monitoring Nov 22, 2024, 02:35 AM UTC

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

  5. monitoring Nov 22, 2024, 02:35 AM UTC

    We are continuing to monitor for any further issues.

  6. resolved Nov 22, 2024, 03:01 AM UTC

    This incident has been resolved.

Read the full incident report →