DocNetwork Outage History

DocNetwork is up right now

DocNetwork had 2 outages in the last 2 years totaling 3h 9m of downtime — averaging 0.1 incidents per month.

There were 2 DocNetwork outages since October 20, 2025 totaling 3h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.docnetwork.org

Critical November 18, 2025

CampDoc and SchoolDoc unreachable

Detected by Pingoru
Nov 18, 2025, 12:06 PM UTC
Resolved
Nov 18, 2025, 03:06 PM UTC
Duration
2h 59m
Affected: Application
Timeline · 5 updates
  1. identified Nov 18, 2025, 12:06 PM UTC

    CampDoc and SchoolDoc are unreachable due to a problem with a primary networking provider. The provider has acknowledged the problem and is working to resolve it.

  2. identified Nov 18, 2025, 01:02 PM UTC

    Our networking provider continues to investigate the problem. No estimated resolution time is yet available.

  3. identified Nov 18, 2025, 01:53 PM UTC

    Our networking provider, Cloudflare, continues to investigate the problem. No estimated resolution time is yet available.

  4. monitoring Nov 18, 2025, 02:53 PM UTC

    Our networking provider, Cloudflare, has marked this issue as Resolved. Access to CampDoc and SchoolDoc is working at this time. We are monitoring the fix and will mark the issue Resolved if the correction is sustained.

  5. resolved Nov 18, 2025, 03:06 PM UTC

    Access to CampDoc and SchoolDoc has been restored. We will continue to monitor Cloudflare's status throughout the day.

Read the full incident report →

Minor October 20, 2025

Reports problem

Detected by Pingoru
Oct 20, 2025, 10:34 AM UTC
Resolved
Oct 20, 2025, 10:44 AM UTC
Duration
10m
Affected: Application
Timeline · 4 updates
  1. identified Oct 20, 2025, 10:34 AM UTC

    Our systems have largely recovered from this morning's widespread AWS outage. We are troubleshooting a remaining problem with producing Reports in PDF format. Reports can still be generated in CSV format.

  2. identified Oct 20, 2025, 10:35 AM UTC

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

  3. monitoring Oct 20, 2025, 10:40 AM UTC

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

  4. resolved Oct 20, 2025, 10:44 AM UTC

    This incident has been resolved.

Read the full incident report →