Chronograph Outage History

Chronograph is up right now

Chronograph had 12 outages in the last 2 years totaling 54h 8m of downtime, averaging 0.5 incidents per month.

There were 12 Chronograph outages since December 4, 2024 totaling 54h 8m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.chronograph.pe

Minor September 2, 2026

Degraded Performance of Snowbank Data Sharing

Detected by Pingoru
Sep 02, 2026, 06:08 PM UTC
Resolved
Sep 03, 2026, 01:36 AM UTC
Duration
7h 28m
Timeline · 2 updates
  1. identified Sep 02, 2026, 06:08 PM UTC

    Due to a recent Snowflake update, Chronograph's data shares to client warehouses are refreshing about every 15 minutes instead of the normal 5. Data remains complete and accurate. We have escalated the incident with Snowflake and will share more details as we receive them. For the time being, no action is needed on your end.

  2. resolved Sep 03, 2026, 01:36 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor June 16, 2026

Sandbox data inaccessible for some clients

Detected by Pingoru
Jun 16, 2026, 09:40 AM UTC
Resolved
Jun 16, 2026, 03:05 PM UTC
Duration
5h 24m
Timeline · 4 updates
  1. identified Jun 16, 2026, 09:40 AM UTC

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

  2. identified Jun 16, 2026, 09:42 AM UTC

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

  3. identified Jun 16, 2026, 10:53 AM UTC

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

  4. resolved Jun 16, 2026, 03:05 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 10, 2026

Incident with Amazon S3 document storage

Detected by Pingoru
Feb 10, 2026, 10:02 PM UTC
Resolved
Feb 11, 2026, 12:35 AM UTC
Duration
2h 32m
Affected: Chronograph Main API
Timeline · 3 updates
  1. investigating Feb 10, 2026, 10:02 PM UTC

    AWS has a active issue, we are monitoring https://health.aws.amazon.com/health/status

  2. monitoring Feb 10, 2026, 10:11 PM UTC

    AWS has confirmed significant recovery for DNS resolution errors for Cloudfront distributions. Certain features of our platform rely on this to function properly and as such we have observed an increase in errors while this incident has been ongoing. We will continue to watch for AWS' full resolution of the issue.

  3. resolved Feb 11, 2026, 12:35 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 10, 2026

DNS provider instability

Detected by Pingoru
Feb 10, 2026, 05:35 PM UTC
Resolved
Feb 10, 2026, 07:43 PM UTC
Duration
2h 7m
Affected: Chronograph Main APIDNSimple Name Servers
Timeline · 5 updates
  1. monitoring Feb 10, 2026, 05:35 PM UTC

    DNSimple is reporting infrastructure instability that is impacting some users' ability to resolve some of Chronograph's domain names. The impact appears to be inconsistent and not uniform across all users.

  2. monitoring Feb 10, 2026, 05:57 PM UTC

    DNSimple is reportedly implementing a fix. We will continue to monitor for recovery. In the meantime, we have observed that our status page (status.chronograph.pe) may not be resolving due to the same upstream issues.

  3. monitoring Feb 10, 2026, 07:04 PM UTC

    DNSimple expects to have their services restored shortly. We will continue monitoring in the meantime.

  4. monitoring Feb 10, 2026, 07:36 PM UTC

    We are continuing to monitor for any further issues.

  5. resolved Feb 10, 2026, 07:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor February 2, 2026

Notifications not being sent

Detected by Pingoru
Feb 02, 2026, 09:38 PM UTC
Resolved
Feb 02, 2026, 10:11 PM UTC
Duration
33m
Affected: Courier Inbox
Timeline · 5 updates
  1. investigating Feb 02, 2026, 09:38 PM UTC

    Due to an outage with an upstream provider, we are not able to send any email notifications. We have a complete record of unsent notifications and we will ensure all notifications are sent as soon as our upstream provider restores service.

  2. investigating Feb 02, 2026, 09:38 PM UTC

    We are continuing to investigate this issue.

  3. identified Feb 02, 2026, 09:41 PM UTC

    We are waiting for our upstream service provider to restore service before we clear the backlog of unsent notifications.

  4. identified Feb 02, 2026, 09:45 PM UTC

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

  5. resolved Feb 02, 2026, 10:11 PM UTC

    We have processed the backlog of unsent notifications and confirmed that emails are being sent for new notifications.

Read the full incident report →

Minor December 1, 2025

Issue with MCP server/Claude integration

Detected by Pingoru
Dec 01, 2025, 07:02 PM UTC
Resolved
Dec 01, 2025, 10:09 PM UTC
Duration
3h 6m
Affected: Chronograph Main APIDNSimple Name Servers
Timeline · 4 updates
  1. investigating Dec 01, 2025, 07:02 PM UTC

    We are currently investigating this issue.

  2. investigating Dec 01, 2025, 07:33 PM UTC

    Investigation has revealed upstream issues with dnsimple are preventing the resolution of the ai.chronograph.pe domain. We are still working to resolve this issue with dnsimple.

  3. monitoring Dec 01, 2025, 09:35 PM UTC

    DNS resolution for ai.chronograph.pe is beginning to stabilize. We continue to monitor the situation closely and will provide confirmation once full service restoration is verified.

  4. resolved Dec 01, 2025, 10:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 29, 2025

Microsoft Azure Outage - xConnectJS Unavailable

Detected by Pingoru
Oct 29, 2025, 04:11 PM UTC
Resolved
Oct 30, 2025, 12:34 AM UTC
Duration
8h 22m
Affected: Chronograph Main API
Timeline · 2 updates
  1. monitoring Oct 29, 2025, 04:11 PM UTC

    Due to a Microsoft outage, xConnectJS (as well as other OfficeJS add-ins) is currently unavailable. We are monitoring the situation and will update with more details as they come in.

  2. resolved Oct 30, 2025, 12:34 AM UTC

    Microsoft has confirmed that the incident is fully resolved.

Read the full incident report →

Notice October 20, 2025

Continuing Issues related to AWS Outage

Detected by Pingoru
Oct 20, 2025, 02:10 PM UTC
Resolved
Oct 20, 2025, 10:58 PM UTC
Duration
8h 47m
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 02:10 PM UTC

    Chronograph is currently experience issues with its Snowbank service and is unable to sync data to the data warehouse due to Snowflake issues related to the ongoing AWS Outage. Other services and features of the site may be affected.

  2. monitoring Oct 20, 2025, 08:29 PM UTC

    As the AWS outage continues, we are continuing to monitor for any issues. Services including the Data Sync tool and document access may be affected.

  3. resolved Oct 20, 2025, 10:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice October 20, 2025

AWS outage related issues

Detected by Pingoru
Oct 20, 2025, 09:35 AM UTC
Resolved
Oct 20, 2025, 12:53 PM UTC
Duration
3h 17m
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 09:35 AM UTC

    Chronograph is currently experiencing intermittent issues with several services due to the AWS outage this morning.

  2. monitoring Oct 20, 2025, 10:29 AM UTC

    Services across Chronograph appear to be working as normal. We will continue to monitor for any further disruption.

  3. resolved Oct 20, 2025, 12:53 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 21, 2025

Authentication Provider Disruption

Detected by Pingoru
Aug 21, 2025, 06:40 PM UTC
Resolved
Aug 21, 2025, 07:57 PM UTC
Duration
1h 16m
Affected: Auth0 Authentication APIAuth0 Multi Factor Authentication
Timeline · 3 updates
  1. investigating Aug 21, 2025, 06:40 PM UTC

    Chronographs authentication provider, Auth0, is experiencing issues with authenticating certain requests. We are monitoring the situation and will provide an update as soon as we receive new information.

  2. identified Aug 21, 2025, 06:46 PM UTC

    Our authentication provider is working towards a fix. We will provide an update when the fix has been implemented.

  3. resolved Aug 21, 2025, 07:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 30, 2025

Intermittent Delays in Email Delivery

Detected by Pingoru
Jul 30, 2025, 08:47 PM UTC
Resolved
Jul 31, 2025, 01:22 AM UTC
Duration
4h 34m
Timeline · 2 updates
  1. investigating Jul 30, 2025, 08:47 PM UTC

    We are currently experiencing delayed email delivery affecting a subset of our users. We are working actively with our third-party email delivery provider toward resolution.

  2. resolved Jul 31, 2025, 01:22 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor December 4, 2024

Degraded email delivery service

Detected by Pingoru
Dec 04, 2024, 03:24 AM UTC
Resolved
Dec 04, 2024, 10:01 AM UTC
Duration
6h 36m
Affected: SendGrid API v3
Timeline · 2 updates
  1. monitoring Dec 04, 2024, 03:24 AM UTC

    We are monitoring queued but undelivered emails by our email notification provider SendGrid. We have reached out to their support team for further information and are awaiting a response. Task emails, user invitations, password reset, and other transactional emails may be delayed.

  2. resolved Dec 04, 2024, 10:01 AM UTC

    This incident has been resolved.

Read the full incident report →