Live Status\Incident History

June 11, 2024

Missed Execution

Outage

Opened: Jun 11, 2024, 9:23 AM UTC

Duration: 163h 15m 32s

Affected services:Pihole Backup


  • Opened
    Jun 11, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

June 1, 2024

Missed Execution

Outage

Opened: Jun 1, 2024, 9:23 AM UTC

Duration: 23h 59m 43s

Affected services:Pihole Backup


  • Opened
    Jun 1, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

  • Resolved
    Jun 2, 2024, 9:22 AM UTC

    Issue resolved on monitor recovery.

May 22, 2024

Missed Execution

Outage

Opened: May 22, 2024, 9:23 AM UTC

Duration: 24h 12m 36s

Affected services:Pihole Backup


  • Opened
    May 22, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

  • Resolved
    May 23, 2024, 9:35 AM UTC

    Issue resolved on monitor recovery.

May 13, 2024

Missed Execution

Outage

Opened: May 13, 2024, 9:23 AM UTC

Duration: 167h 59m 29s

Affected services:Pihole Backup


  • Opened
    May 13, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

  • Resolved
    May 20, 2024, 9:22 AM UTC

    Issue resolved on monitor recovery.

May 11, 2024

Failed Execution

Outage

Opened: May 11, 2024, 4:00 PM UTC

Duration: 8m 53s

Affected services:wrt backup


  • Opened
    May 11, 2024, 4:00 PM UTC

    Issue opened on monitor failure.

  • Resolved
    May 11, 2024, 4:09 PM UTC

    Issue resolved on monitor recovery.

  • Resolved
    May 11, 2024, 4:09 PM UTC

    doing a openwrt migration

May 10, 2024

Missed Execution

Outage

Opened: May 10, 2024, 4:01 PM UTC

Duration: 11m 42s

Affected services:wrt backup


  • Opened
    May 10, 2024, 4:01 PM UTC

    Issue opened on monitor failure.

  • Resolved
    May 10, 2024, 4:12 PM UTC

    Issue resolved on monitor recovery.

  • Resolved
    May 10, 2024, 4:13 PM UTC

    Trying re-install openwrt

April 26, 2024

Missed Execution

Outage

Opened: Apr 26, 2024, 9:23 AM UTC

Duration: 23h 59m 11s

Affected services:Pihole Backup


  • Opened
    Apr 26, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

  • Resolved
    Apr 27, 2024, 9:22 AM UTC

    Issue resolved on monitor recovery.

April 17, 2024

Missed Execution

Outage

Opened: Apr 17, 2024, 9:23 AM UTC

Duration: 48h 5m 38s

Affected services:Pihole Backup


  • Opened
    Apr 17, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

  • Resolved
    Apr 19, 2024, 9:28 AM UTC

    Issue resolved on monitor recovery.

  • Resolved
    Apr 19, 2024, 9:36 AM UTC

    The device is down due to power cable issues

April 15, 2024

Missed Execution

Maintenance

Posted: Apr 15, 2024, 4:01 PM UTC

Affected services:wrt backup


  • Opened
    Apr 15, 2024, 4:01 PM UTC

    Issue opened on monitor failure.

  • Resolved
    Apr 16, 2024, 3:51 PM UTC

    Issue resolved on monitor recovery.

  • Resolved
    Apr 16, 2024, 3:52 PM UTC

    Re-doing openwrt backup workflow

April 14, 2024

Missed Execution

Degraded Performance

Opened: Apr 14, 2024, 4:01 PM UTC

Duration: 20h 6m 34s

Affected services:wrt backup


  • Opened
    Apr 14, 2024, 4:01 PM UTC

    Issue opened on monitor failure.

  • Resolved
    Apr 15, 2024, 12:07 PM UTC

    Issue resolved on monitor recovery.

  • Resolved
    Apr 15, 2024, 12:08 PM UTC

    System clock skew caused by proxy server

Incomplete Execution

Missing Data

Opened: Apr 14, 2024, 9:26 AM UTC

Duration: 26h 36m 35s

Affected services:Pihole Backup


  • Opened
    Apr 14, 2024, 9:26 AM UTC

    Issue opened on monitor failure.

  • Resolved
    Apr 15, 2024, 12:03 PM UTC

    Issue resolved on monitor recovery.

  • Resolved
    Apr 15, 2024, 12:04 PM UTC

    Some networking issue caused by proxy software installed on the openwrt, the proxy software prevents proper backup to the cloud storage.

March 21, 2024

Missed Execution

Missing Data

Opened: Mar 21, 2024, 9:23 AM UTC

Duration: 3m 16s

Affected services:Pihole Backup


  • Opened
    Mar 21, 2024, 9:23 AM UTC

    Issue opened on monitor failure.

  • Resolved
    Mar 21, 2024, 9:26 AM UTC

    Issue resolved on monitor recovery.

  • Resolved
    Mar 21, 2024, 9:28 AM UTC

    Didn't know cronitor adds an agent to the crontab job, need to wrap the original set of commands in " to get the job triggered properly.