Fieldd incident

Amazon Web Server Issue

Major Resolved View vendor source →

Fieldd experienced a major incident on March 5, 2023 affecting fieldd Online CRM and fieldd Online Bookings, lasting 4h 41m. The incident has been resolved; the full update timeline is below.

Started
Mar 05, 2023, 10:45 PM UTC
Resolved
Mar 06, 2023, 03:27 AM UTC
Duration
4h 41m
Detected by Pingoru
Mar 05, 2023, 10:45 PM UTC

Affected components

fieldd Online CRMfieldd Online Bookings

Update timeline

  1. investigating Mar 05, 2023, 08:39 PM UTC

    Unfortunately, we have experienced yet another instance of Amazon disrupting fieldd’s system without prior notice. As a result of this continued unreliability, our team is now urgently working on moving our servers away from Amazon to ensure a more stable and dependable service for our valued clients like yourself. We apologize for any inconvenience caused by Amazon’s disruptive behavior.

  2. identified Mar 05, 2023, 09:05 PM UTC

    The issue has been identified, and we are actively implementing a fix

  3. identified Mar 05, 2023, 10:01 PM UTC

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

  4. identified Mar 05, 2023, 10:45 PM UTC

    The team have opted for a permanent fix rather than a temporary one. This fix will increase long term performance and reliability. We anticipate things will be back to normal in a few hours. Thank you for your continued patience.

  5. identified Mar 06, 2023, 01:18 AM UTC

    We are finalizing the fix for this issue. Thank you for your patience.

  6. identified Mar 06, 2023, 02:51 AM UTC

    We are within 30 mins of a permanent fix. Unfortunately, we are at the mercy of large third party services such as Amazon and Google. When these companies have internal issues, that trickle down to us, without notice. Fieldd’s product itself is unaffected. The entire team have worked tirelessly on a Sunday to permanently solve this. We thank you for your patience.

  7. monitoring Mar 06, 2023, 03:21 AM UTC

    Everything is back to normal. We are monitoring the new fix.

  8. resolved Mar 06, 2023, 03:27 AM UTC

    This incident has been resolved.