Fieldd Outage History

Fieldd is up right now

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

There were 3 Fieldd outages since March 17, 2026 totaling 3h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.fieldd.co

Notice October 5, 2026

Cloudflare Validation Error

Detected by Pingoru
Oct 05, 2026, 01:01 PM UTC
Resolved
Oct 05, 2026, 01:46 PM UTC
Duration
44m
Affected: fieldd Online Bookings
Timeline · 4 updates
  1. investigating Oct 05, 2026, 01:01 PM UTC

    A known outage is being experienced with Cloudflare which is impacting Online Booking pages.

  2. monitoring Oct 05, 2026, 01:30 PM UTC

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

  3. monitoring Oct 05, 2026, 01:30 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 05, 2026, 01:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 12, 2026

Cloudflare Connectivity Issue

Detected by Pingoru
Aug 12, 2026, 11:15 AM UTC
Resolved
Aug 12, 2026, 12:29 PM UTC
Duration
1h 13m
Affected: fieldd Online Bookings
Timeline · 3 updates
  1. identified Aug 12, 2026, 12:20 PM UTC

    Overnight, Cloudflare developed a connectivity issue with our online booking servers. Some regions are affected. We are investigating now and will share an update soon.

  2. identified Aug 12, 2026, 12:21 PM UTC

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

  3. resolved Aug 12, 2026, 12:29 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 17, 2026

Partial Outage

Detected by Pingoru
Mar 17, 2026, 10:31 PM UTC
Resolved
Mar 18, 2026, 12:07 AM UTC
Duration
1h 36m
Affected: fieldd API
Timeline · 3 updates
  1. identified Mar 17, 2026, 10:31 PM UTC

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

  2. identified Mar 18, 2026, 12:03 AM UTC

    Thank you for your continued patience whilst we look into this issue.

  3. resolved Mar 18, 2026, 12:07 AM UTC

    This incident has been resolved.

Read the full incident report →