rewindex

CompaniesNetlifyIncidents

Netlify: Delays in build logs appearing in the UI

MinorStatus: identifiededitedStarted Not resolved7 updatesstspg.io (opens in new tab)

Affected components: Build PipelineNetlify Application UI

Timeline of updates

  1. investigating

    We are investigating an issue causing delays in build logs appearing in the Netlify UI. Our team is actively investigating and will provide updates as we learn more.

  2. investigating

    We are continuing to investigate delays in build logs appearing in the Netlify UI. Our team is working to identify the cause and will provide further updates as information becomes available.

  3. investigating

    We are continuing to investigate delays in build logs appearing in the Netlify UI. We are still actively investigating and will provide further updates as information becomes available.

  4. investigating

    We are continuing to investigate the delays affecting build log availability in the Netlify UI. We will share further updates as more information becomes available.

  5. investigating

    We have identified an ongoing issue with an upstream service provider that may be contributing to delays in build logs appearing in the Netlify UI. We are in contact with the provider and are continuing to monitor the situation. We will provide further updates as more information becomes available.

  6. investigating

    We continue to experience delays in build logs appearing in the Netlify UI. We remain in contact with our upstream service provider as the investigation continues. We will provide further updates as more information becomes available.

  7. identified

    We've identified the cause of the delays in build logs appearing in the Netlify UI as an issue with an upstream service provider, who is working on a fix

Changes Rewindex caught on this incident

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run () commits it.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Netlify profileRecent Netlify incidentsMarkdownJSON