### Example Incident: Clients Page Loading Issue

Source: https://statusfield.com/status/virtuagym/incidents

An example incident report detailing a problem with the 'Clients' page not loading properly, including its resolution status and timestamps.

```APIDOC
{
  "id": "558-849c-9664f4ebc34f",
  "incident": {
    "id": "4643ac60-afe7-5558-849c-9664f4ebc34f",
    "title": "'Clients' page not loading properly",
    "updates": [
      {
        "status": "resolved",
        "message": "This incident has been resolved",
        "timestamp": "2023-06-02T19:28:42.299Z"
      },
      {
        "status": "investigating",
        "message": "We are currently investigating the issue",
        "timestamp": "2023-06-02T18:54:31.179Z"
      }
    ],
    "lastUpdate": "2023-06-02T19:28:42.312Z"
  },
  "createdAt": "2025-06-04T17:48:48.717Z",
  "updatedAt": "2023-06-02T19:28:42.312Z"
}
```

--------------------------------

### Zimbra Connector for Outlook (ZCO) Installation Guide

Source: https://statusfield.com/status/synaq/incidents

Step-by-step instructions for installing the Zimbra Connector for Outlook (ZCO) to resolve intermittent email sending issues. This guide covers prerequisites, uninstallation of old versions, downloading the correct build, installation steps, and creating a new Outlook profile with Zimbra account details.

```APIDOC
Zimbra Connector for Outlook (ZCO) Installation Guide:

**Before You Begin:**
*   **Outlook Version:** Determine if your Outlook installation is 32-bit or 64-bit to download the correct ZCO version.
*   **Administrative Permissions:** Administrative privileges are required on your computer to install software.
*   **Close Outlook:** Ensure Outlook is closed before proceeding with the installation.

**Installation Steps:**

1.  **Uninstall Old ZCO (if applicable):**
    *   If a previous version of ZCO is installed, uninstall it via your computer's Control Panel.

2.  **Download the New ZCO Build:**
    *   Download the ZCO installer file matching your Outlook version (32-bit or 64-bit) from the designated download location.
    *   Download URL: https://www.zimbra.com/product/addons/zimbra-connector-for-outlook-download/

3.  **Install ZCO:**
    *   Double-click the downloaded ZCO .msi file.
    *   Click 'Run' to start the installation.
    *   Click 'Next' on the initial screen.
    *   Accept the license agreement by clicking 'I accept the terms in the License Agreement' and then 'Next'.
    *   Click 'Next' again to begin the installation.
    *   Click 'Close' when the installation completes.

4.  **Create a New Outlook Profile:**
    *   Open 'Mail' from the Control Panel.
    *   Click 'Show Profiles'.
    *   Click 'Add' to create a new profile.
    *   Select 'Manual Setup' and then 'Other'.
    *   In the 'Other' dialog box, ensure 'Zimbra Collaboration Server' is selected and click 'Next'.

5.  **Enter Account Information:**
    *   **Server Name:** cloudmail.synaq.com
    *   **Use Secure Connection:** Check this box.
    *   **Email Address:** Enter your full email address.
    *   **Password:** Enter your mailbox password.

6.  **Complete Installation:**
    *   Click 'Apply' to finish setting up the new profile.

**Support Contact:**
*   Phone: 011 262 3632
*   Email: support@synaq.com
```

--------------------------------

### Pendo Guides Failing to Display

Source: https://statusfield.com/status/pendo/incidents

An incident where Pendo Guides were failing to display for users. The provided snippet is incomplete, only indicating the start of the incident report.

```APIDOC
Incident: Pendo Guides Failing to Display

Description: Pendo Guides were not displaying correctly for users.

Updates:
- Resolved: 
```

--------------------------------

### Example Service Entry

Source: https://statusfield.com/status/magiceden

An example of a single service entry from the provided data, illustrating the typical fields and their values. This format is common for service monitoring dashboards.

```json
{
  "id": "e6e9d98a-c2a8-5423-a5f0-91e6a91c0979",
  "name": "Access Worldpay",
  "slug": "access-worldpay",
  "domainURL": "access.worldpay.com",
  "icon": "access-worldpay.png",
  "lastCheckAt": "2025-07-26T10:03:43.305Z",
  "category": "OTHER",
  "status": "OPERATIONAL"
}
```

--------------------------------

### Incident: Active Issue Alert – Guided Fundraising - 000598003

Source: https://statusfield.com/status/blackbaud/incidents

Details an active issue with Guided Fundraising. The provided snippet is incomplete, but it indicates the start of an incident report for this service.

```APIDOC
Incident: Active Issue Alert – Guided Fundraising - 000598003
  Updates: [
    
```

--------------------------------

### Example Service Entry

Source: https://statusfield.com/status/baremetrics

An example of a single service entry from the provided data, illustrating the typical fields and their values for a service like 'Abnormal Security'.

```json
{
  "id": "ce05411e-9a90-5b30-8a2b-f7aefd6b7220",
  "name": "Abnormal Security",
  "slug": "abnormal-security",
  "domainURL": "abnormalsecurity.com",
  "icon": "abnormal-security.png",
  "lastCheckAt": "2025-07-26T10:03:12.410Z",
  "category": "OTHER",
  "status": "OPERATIONAL"
}
```

--------------------------------

### Example Service Entry

Source: https://statusfield.com/status/chef

An example of a single service entry as it appears in the data. This illustrates the typical values for properties like ID, name, domain, and status.

```json
{
  "id": "83ef78be-671a-5f8b-9bbc-7f7884eca3bd",
  "name": "A Bet A",
  "slug": "a-bet-a",
  "domainURL": "abeta.co.uk",
  "icon": "a-bet-a.png",
  "lastCheckAt": "2025-07-26T10:04:37.797Z",
  "category": "OTHER",
  "status": "OPERATIONAL"
}
```

--------------------------------

### Example Incident Report: Long Delays Restoring Files

Source: https://statusfield.com/status/digital-pigeon/incidents

An example incident report detailing long delays in restoring files, caused by specific tasks getting stuck. It includes updates on monitoring a deployed fix and resolution.

```json
{
  "id": "b682a1e7-6ce1-5a92-bdd4-8417d996df09",
  "incident": {
    "id": "b682a1e7-6ce1-5a92-bdd4-8417d996df09",
    "title": "Long delays restoring files",
    "updates": [
      {
        "status": "resolved",
        "message": "This incident has been resolved.",
        "timestamp": "2016-02-25T19:36:03.365-07:00"
      },
      {
        "status": "monitoring",
        "message": "We've deployed a fix. Restore tasks are processing but please allow several hours for the system to catch up.",
        "timestamp": "2016-02-24T03:04:50.364-07:00"
      },
      {
        "status": "identified",
        "message": "We are experiencing long delays in restoring files. The delays seem to be caused by specific restore tasks getting stuck which in turn blocks the restore process for other files. We are working to mitigate the issue but at the moment have no ETA.",
        "timestamp": "2016-02-24T02:42:29.250-07:00"
      }
    ],
    "lastUpdate": "2016-02-25T19:36:03.397-07:00"
  },
  "createdAt": "2025-06-04T17:45:46.472Z",
  "updatedAt": "2016-02-26T02:36:03.397Z"
}
```

--------------------------------

### Example Incident: System Failures

Source: https://statusfield.com/status/fourth/incidents

An example incident report for 'Failures impacting Adaco ordering, People System gateway messaging & RME reporting'. This snippet shows the start of an incident report, indicating a 'resolved' status.

```json
{
  "id": "ddaf3399-c5a8-5832-89e5-35c3c95299e7",
  "incident": {
    "id": "ddaf3399-c5a8-5832-89e5-35c3c95299e7",
    "title": "P2 - Failures impacting Adaco ordering, People System gateway messaging \u0026 RME reporting",
    "updates": [
      {
        "status": "resolved"
      }
    ]
  }
}
```

--------------------------------

### Example Service Entry

Source: https://statusfield.com/status/nanonets

An example of a single service object as found in the status field data, illustrating the expected properties and their typical values.

```json
{
  "id": "572ca8b4-3987-56c3-99b4-bc49532a9dec",
  "name": "AccuWeather",
  "slug": "accuweather",
  "domainURL": "accuweather.com",
  "icon": "accuweather.png",
  "lastCheckAt": "2025-07-26T10:04:35.965Z",
  "category": "SAAS",
  "status": "OPERATIONAL"
}
```

--------------------------------

### Example Service Entry

Source: https://statusfield.com/status/sharpspring

An example of a single service entry as found in the status data, illustrating the typical fields and their values.

```json
{
  "id": "868ff8a0-cfd4-58eb-bdf8-129665be84be",
  "name": "Actionstep",
  "slug": "actionstep",
  "domainURL": "actionstep.com",
  "icon": "actionstep.png",
  "lastCheckAt": "2025-07-26T10:08:42.438Z",
  "category": "OTHER",
  "status": "OPERATIONAL"
}
```

--------------------------------

### Example Status Update: Maintenance Period

Source: https://statusfield.com/status/epic-games-public

Demonstrates a status update for a component that was UNDER_MAINTENANCE, showing the start and end times of the maintenance, and the final status change to OPERATIONAL.

```APIDOC
{
  "component": {
    "id": "7b865594-24ab-582d-a283-a3536fd8609c",
    "name": "LEGO Fortnite",
    "slug": "lego-fortnite",
    "parentId": "916ae43d-01c5-5b91-a798-5962bbc6b489",
    "isRoot": false
  },
  "eventStart": "2025-07-15T08:03:43.672Z",
  "eventEnd": "2025-07-15T16:33:31.426Z",
  "lastUpdate": "2025-07-15T16:33:31.426Z",
  "statusChanges": [
    {
      "component": {
        "id": "7b865594-24ab-582d-a283-a3536fd8609c",
        "name": "LEGO Fortnite",
        "slug": "lego-fortnite",
        "parentId": "916ae43d-01c5-5b91-a798-5962bbc6b489",
        "isRoot": false
      },
      "status": "OPERATIONAL",
      "timestamp": "2025-07-15T16:33:31.426Z",
      "durationInMinutes": 0,
      "affectedComponents": []
    },
    {
      "component": {
        "id": "7b865594-24ab-582d-a283-a3536fd8609c",
        "name": "LEGO Fortnite",
        "slug": "lego-fortnite",
        "parentId": "916ae43d-01c5-5b91-a798-5962bbc6b489",
        "isRoot": false
      },
      "status": "UNDER_MAINTENANCE",
      "timestamp": "2025-07-15T08:03:43.672Z",
      "durationInMinutes": 510,
      "affectedComponents": []
    }
  ],
  "affectedComponents": []
}
```

--------------------------------

### Example Incident: API Downtime and Timeouts

Source: https://statusfield.com/status/open-exchange-rates/incidents

An example incident report detailing API downtime and timeouts. It specifies the start and end times of the service degradation, the cause (misconfiguration during updates combined with cache recovery), and the impact (500 error messages). It also states that recurrence is not anticipated.

```json
{
  "id": "5d1c3c0c-a84c-5b15-9b6f-8c0eda1fc397",
  "incident": {
    "id": "5d1c3c0c-a84c-5b15-9b6f-8c0eda1fc397",
    "title": "API downtime and timeouts",
    "updates": [
      {
        "status": "resolved",
        "message": "This incident has been resolved. The service degradation began at approximately 07:10 UTC, and was resolved by 08:10 UTC. During this time, some clients received 500 error messages in response to their API requests. This was the result of a misconfiguration during regular scheduled platform updates that was caused by a cache recovery event that occurred at the same time. We do not anticipate a recurrence.",
        "timestamp": "2023-05-21T09:20:31.346Z"
      },
      {
        "status": "monitoring",
        "message": "A fix has been implemented and we are monitoring the results.",
        "timestamp": "2023-05-21T08:16:24.630Z"
      },
      {
        "status": "identified",
        "message": "The issue has been identified and a fix is being implemented.",
        "timestamp": "2023-05-21T08:00:43.901Z"
      },
      {
        "status": "investigating",
        "message": "We are currently investigating a platform issue that is resulting in API timeouts. Please stand by for updates.",
        "timestamp": "2023-05-21T07:38:49.301Z"
      }
    ],
    "lastUpdate": "2023-05-21T09:20:31.361Z"
  },
  "createdAt": "2025-06-04T17:34:44.450Z",
  "updatedAt": "2023-05-21T09:20:31.361Z"
}
```

--------------------------------

### Example Service Status Entries

Source: https://statusfield.com/status/medium

This snippet shows example entries from a list of services, detailing their status, domain, and category. It illustrates the typical data format used for tracking the operational health of various services.

```JSON
[
  {
    "id": "e6e9d98a-c2a8-5423-a5f0-91e6a91c0979",
    "name": "Access Worldpay",
    "slug": "access-worldpay",
    "domainURL": "access.worldpay.com",
    "icon": "access-worldpay.png",
    "lastCheckAt": "2025-07-26T10:03:43.305Z",
    "category": "OTHER",
    "status": "OPERATIONAL"
  },
  {
    "id": "f594ce57-c5fb-5846-a5f1-1c6095dd5e68",
    "name": "Accredible",
    "slug": "accredible",
    "domainURL": "accredible.com",
    "icon": "accredible.png",
    "lastCheckAt": "2025-07-26T10:09:32.977Z",
    "category": "EDUCATION",
    "status": "OPERATIONAL"
  }
]
```

--------------------------------

### Example Incident: Studio Campaign Builder Inaccessible

Source: https://statusfield.com/status/gofundme-pro/incidents

An example incident report for the Studio Campaign Builder being inaccessible. It details the 'investigating' status and provides a message about the ongoing investigation and impact on transaction processing.

```APIDOC
Incident:
  id: "b057255b-b0df-575c-afc3-e333a8745a18"
  incident:
    id: "b057255b-b0df-575c-afc3-e333a8745a18"
    title: "Studio Campaign Builder Inaccessible"
    updates:
      - status: "investigating"
        message: "We are actively investigating reports of Studio Campaign builder not loading. This is not impacting transaction processing or the donor experience. Our team is investigating and will provide updates when available."
        timestamp: "2025-07-06T15:13:44.729-07:00"
    lastUpdate: "2025-07-06T15:13:44.731-07:00"
  createdAt: "2025-07-06T22:14:59.820Z"
  updatedAt: "2025-07-06T22:13:44.731Z"
```

--------------------------------

### Example Incident: ADSS-Engine Staging Maintenance

Source: https://statusfield.com/status/digicert/incidents

Reports for maintenance activities on the ADSS-Engine Staging environment. These entries track the start and completion of scheduled maintenance, indicating the system status throughout the process.

```APIDOC
IncidentReport:
  id: "647895ee-ab76-50a1-8d31-1c23e259f002"
  incident:
    id: "647895ee-ab76-50a1-8d31-1c23e259f002"
    title: "Maintenance - ADSS-Engine Staging"
    updates:
      - status: "resolved"
        message: "Maintenance is now completed."
        timestamp: "2024-11-28T08:45:07.167Z"
      - status: "investigating"
        message: "ADSS-Engine Staging is currently undergoing maintenance.\nThank you for your understanding."
        timestamp: "2024-11-28T06:24:42.802Z"
    lastUpdate: "2024-11-28T08:45:07.179Z"
  createdAt: "2025-06-04T17:49:47.740Z"
  updatedAt: "2024-11-28T08:45:07.179Z"
```

```APIDOC
IncidentReport:
  id: "c6ade312-d600-5767-bfe4-a2c8876680af"
  incident:
    id: "c6ade312-d600-5767-bfe4-a2c8876680af"
    title: "Maintenance - ADSS-Engine Staging"
    updates:
      - status: "resolved"
        message: "maintenance successfully completed."
        timestamp: "2024-11-01T08:43:17.019Z"
      - status: "investigating"
        message: "ADSS-Engine Staging is currently undergoing maintenance.\nThank y"
        timestamp: "2024-11-01T08:00:00.000Z"
```

--------------------------------

### Example Service Entry

Source: https://statusfield.com/status/argyle

An example of a single service object as it might appear in a list of services. This demonstrates the typical fields and their expected values.

```json
{
  "id": "e6e9d98a-c2a8-5423-a5f0-91e6a91c0979",
  "name": "Access Worldpay",
  "slug": "access-worldpay",
  "domainURL": "access.worldpay.com",
  "icon": "access-worldpay.png",
  "lastCheckAt": "2025-07-26T10:03:43.305Z",
  "category": "OTHER",
  "status": "OPERATIONAL"
}
```

--------------------------------

### Services Status Event (Maintenance)

Source: https://statusfield.com/status/f5

Records a maintenance event for the 'Services' component. It specifies the start and end times of the maintenance, the status change to UNDER_MAINTENANCE, and lists the affected services. The example shows a maintenance period for 'Routed Originated Services'.

```JSON
{
  "component": {
    "id": "c5f403cf-268f-5305-8092-83cbaa5585ce",
    "name": "Services",
    "slug": "services",
    "parentId": "093c9156-36ea-58d8-8826-3e696f472ccc",
    "isRoot": false
  },
  "eventStart": "2025-07-17T17:07:10.927Z",
  "eventEnd": "2025-07-17T23:07:13.859Z",
  "lastUpdate": "2025-07-17T23:07:13.859Z",
  "statusChanges": [
    {
      "component": {
        "id": "c5f403cf-268f-5305-8092-83cbaa5585ce",
        "name": "Services",
        "slug": "services",
        "parentId": "093c9156-36ea-58d8-8826-3e696f472ccc",
        "isRoot": false
      },
      "status": "OPERATIONAL",
      "timestamp": "2025-07-17T23:07:13.859Z",
      "durationInMinutes": 0,
      "affectedComponents": []
    },
    {
      "component": {
        "id": "c5f403cf-268f-5305-8092-83cbaa5585ce",
        "name": "Services",
        "slug": "services",
        "parentId": "093c9156-36ea-58d8-8826-3e696f472ccc",
        "isRoot": false
      },
      "status": "UNDER_MAINTENANCE",
      "timestamp": "2025-07-17T17:07:10.927Z",
      "durationInMinutes": 360,
      "affectedComponents": [
        "Routed Originated Services"
      ]
    }
  ],
  "affectedComponents": [
    "Routed Originated Services"
  ]
}
```

--------------------------------

### Example Incident Reports

Source: https://statusfield.com/status/activecampaign/incidents

Illustrates common incident scenarios and their corresponding data structures, including issues with platform access, specific features like landing pages, and login processes.

```APIDOC
Example Incident: Platform Access Issue
{
  "id": "a1b2c3d4-e5f6-7890-1234-567890abcdef",
  "incident": {
    "id": "a1b2c3d4-e5f6-7890-1234-567890abcdef",
    "title": "Customers encounter error messages when accessing the platform",
    "updates": [
      {
        "status": "investigating",
        "message": "Engineers are investigating an issue where customers encounter error messages when accessing the platform.",
        "timestamp": "2024-08-14T15:03:23.664-05:00"
      }
    ],
    "lastUpdate": "2024-08-14T17:04:46.052-05:00"
  },
  "createdAt": "2025-06-04T17:38:45.684Z",
  "updatedAt": "2024-08-14T22:04:46.052Z"
}

Example Incident: MFA Login Error
{
  "id": "e3ae9973-4059-5bea-9c81-13b3e45ce419",
  "incident": {
    "id": "e3ae9973-4059-5bea-9c81-13b3e45ce419",
    "title": "Customers attempting to log in using MFA see an error page with HTTP Code 500",
    "updates": [
      {
        "status": "resolved",
        "message": "This incident has been resolved.",
        "timestamp": "2024-08-01T02:00:44.000-05:00"
      },
      {
        "status": "identified",
        "message": "This issue occurs when attempting to login using email address. Logging in with username is unaffected. A fix is in progress.",
        "timestamp": "2024-07-31T22:07:49.000-05:00"
      },
      {
        "status": "identified",
        "message": "Engineers have identified an issue where customers attempting to log in to ActiveCampaign using Multi Factor Authentication encounter an error. A fix has been identified and will be deployed shortly",
        "timestamp": "2024-07-31T21:05:52.273-05:00"
      }
    ],
    "lastUpdate": "2024-08-01T06:04:28.973-05:00"
  },
  "createdAt": "2025-06-04T17:38:45.684Z",
  "updatedAt": "2024-08-01T11:04:28.973Z"
}

Example Incident: Landing Page Builder Issue
{
  "id": "b26d2f94-43fc-5e23-b610-30159dec381b",
  "incident": {
    "id": "b26d2f94-43fc-5e23-b610-30159dec381b",
    "title": "Landing pages builder application cannot be loaded",
    "updates": [
      {
        "status": "resolved",
        "message": "Customers trying to load Landing Pages would have experienced an issue where the page did not load correctly and instead shows a link to be clicked to redirect to the correct page. Previously published pages were accessible at all times, only the Page Builder application itself was impacted.",
        "timestamp": "2024-07-23T11:02:41.346-05:00"
      }
    ],
    "lastUpdate": "2024-07-23T11:56:49.314-05:00"
  },
  "createdAt": "2025-06-04T17:38:45.684Z",
  "updatedAt": "2024-07-23T16:56:49.314Z"
}
```

--------------------------------

### Component Event Log Example

Source: https://statusfield.com/status/pagero-service

Details a historical event for a component, including start and end times, last update, and a series of status changes. It also lists specific affected sub-components during the event.

```json
{
  "component": {
    "id": "bd629638-ddb4-56b0-bf61-e4966a45e47a",
    "name": "Pagero Health Solutions",
    "slug": "pagero-health-solutions",
    "parentId": "af768079-67ad-588f-940d-b6e930d54008",
    "isRoot": false
  },
  "eventStart": "2025-07-17T10:17:00.585Z",
  "eventEnd": "2025-07-17T10:40:23.890Z",
  "lastUpdate": "2025-07-17T10:40:23.890Z",
  "statusChanges": [
    {
      "component": {
        "id": "bd629638-ddb4-56b0-bf61-e4966a45e47a",
        "name": "Pagero Health Solutions",
        "slug": "pagero-health-solutions",
        "parentId": "af768079-67ad-588f-940d-b6e930d54008",
        "isRoot": false
      },
      "status": "OPERATIONAL",
      "timestamp": "2025-07-17T10:40:23.890Z",
      "durationInMinutes": 0,
      "affectedComponents": []
    },
    {
      "component": {
        "id": "bd629638-ddb4-56b0-bf61-e4966a45e47a",
        "name": "Pagero Health Solutions",
        "slug": "pagero-health-solutions",
        "parentId": "af768079-67ad-588f-940d-b6e930d54008",
        "isRoot": false
      },
      "status": "PARTIAL_OUTAGE",
      "timestamp": "2025-07-17T10:17:00.585Z",
      "durationInMinutes": 23,
      "affectedComponents": [
        "Health Center/Health Mobile",
        "Hospital Shop",
        "Health OCR Order",
        "HBS Invoice",
        "Aposervice",
        "Health Center AS2",
        "Health Center SFTP",
        "OFTP2"
      ]
    }
  ],
  "affectedComponents": [
    "Health Center/Health Mobile",
    "Hospital Shop",
    "Health OCR Order",
    "HBS Invoice",
    "Aposervice",
    "Health Center AS2",
    "Health Center SFTP",
    "OFTP2"
  ]
}
```

--------------------------------

### Example Incident: Jira Align Downtime

Source: https://statusfield.com/status/jira-align/incidents

Documents a specific downtime incident for Jira Align, detailing the start and end times of the outage and the resolution status. It also includes a monitoring update and investigation details.

```APIDOC
Incident:
  id: "30c11a8c-46e2-5eec-8fc1-cd4191e06775"
  incident:
    id: "30c11a8c-46e2-5eec-8fc1-cd4191e06775"
    title: "Some products are hard down"
    updates:
      - status: "resolved"
        message: "Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Jira Align. The issue has been resolved and the service is operating normally."
        timestamp: "2024-07-04T00:34:47.621Z"
      - status: "monitoring"
        message: "We have mitigated the problem and continue looking into the root cause.\nThe outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC\nWe are now monitoring closely."
        timestamp: "2024-07-03T21:45:05.036Z"
      - status: "investigating"
        message: "We are investigating an issue with \u003cFUNCTIONALITY IMPACTED\u003e that is impacting \u003cSOME/ALL\u003e Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Atlassian Analytics, and Rovo Cloud customers. We will provide more details within the next hour."
        timestamp: "2024-07-03T20:51:01.463Z"
    lastUpdate: "2024-07-04T00:34:47.634Z"
  createdAt: "2025-06-04T17:39:44.772Z"
  updatedAt: "2024-07-04T00:34:47.634Z"
```

--------------------------------

### Monitor Action Entry Point

Source: https://statusfield.com/status/findify-by-maropost

Defines a monitor action with a URL template for managing monitoring and specifies the platforms it supports. This structured data is typically used for web indexing or programmatic access.

```json
{
  "@type": "EntryPoint",
  "urlTemplate": "https://statusfield.com/status/findify-by-maropost/manage/monitoring",
  "actionPlatform": [
    "http://schema.org/DesktopWebPlatform",
    "http://schema.org/MobileWebPlatform"
  ]
}
```

--------------------------------

### API: Reservation and Message Webhooks Affected

Source: https://statusfield.com/status/airbnb-api/incidents

Reports an issue impacting the sending of reservation and message-related webhooks. Details the start date, monitoring of a fix, and guidance for retrieving missing data via the GET Reservations API.

```APIDOC
Incident: Issue Affecting Reservation and Message Related Webhooks
Status: resolved
Timestamp: 2024-07-29T11:18:26.456-07:00
Message: This incident has been resolved. If you need additional help, please contact the API Integrations Team through the Support Portal.

Monitoring Timestamp: 2024-07-19T13:44:26.161-07:00
Monitoring Message: A fix has been implemented and we are monitoring the results.

Investigating Timestamp: 2024-07-19T12:30:35.495-07:00
Investigating Message: We have identified an issue affecting the sending of reservation and message related webhooks starting on July 18th. We are actively working on it and will post more updates when we have them. This incident does not affect all reservations and messages. If you notice that some of your Hosts' reservations webhooks are missing after accepting make_reservation synchronous check, use the GET Reservations API to retrieve the reservation status.
```

--------------------------------

### Example Service Entry: A Cloud Guru

Source: https://statusfield.com/status/maestroqa

An example service entry for 'A Cloud Guru', detailing its status as 'OPERATIONAL' and its category as 'OTHER'. This snippet demonstrates the data structure for a specific service.

```json
{
  "id": "d652d807-be66-560d-8c5b-42ea3aa782e7",
  "name": "A Cloud Guru",
  "slug": "a-cloud-guru",
  "domainURL": "acloud.guru",
  "icon": "a-cloud-guru.png",
  "lastCheckAt": "2025-07-26T10:08:13.474Z",
  "category": "OTHER",
  "status": "OPERATIONAL"
}
```

--------------------------------

### EU Component Status Update Example

Source: https://statusfield.com/status/p44

This snippet represents a typical status update for a European component, detailing its maintenance period, affected sub-components, and status transitions. It includes timestamps for event start, end, and last updates.

```json
{
  "id": "3b72245d-e43f-5250-91bf-4fd2c72af74a-5",
  "component": {
    "id": "3b72245d-e43f-5250-91bf-4fd2c72af74a",
    "name": "EU - Movement",
    "slug": "eu-movement",
    "parentId": "10bf3ff0-64c7-5996-a3da-c04155a68de7",
    "isRoot": false
  },
  "events": [
    {
      "component": {
        "id": "3b72245d-e43f-5250-91bf-4fd2c72af74a",
        "name": "EU - Movement",
        "slug": "eu-movement",
        "parentId": "10bf3ff0-64c7-5996-a3da-c04155a68de7",
        "isRoot": false
      },
      "eventStart": "2025-07-23T04:32:44.919Z",
      "eventEnd": "2025-07-23T08:35:23.981Z",
      "lastUpdate": "2025-07-23T08:35:23.981Z",
      "statusChanges": [
        {
          "component": {
            "id": "3b72245d-e43f-5250-91bf-4fd2c72af74a",
            "name": "EU - Movement",
            "slug": "eu-movement",
            "parentId": "10bf3ff0-64c7-5996-a3da-c04155a68de7",
            "isRoot": false
          },
          "status": "OPERATIONAL",
          "timestamp": "2025-07-23T08:35:23.981Z",
          "durationInMinutes": 0,
          "affectedComponents": []
        },
        {
          "component": {
            "id": "3b72245d-e43f-5250-91bf-4fd2c72af74a",
            "name": "EU - Movement",
            "slug": "eu-movement",
            "parentId": "10bf3ff0-64c7-5996-a3da-c04155a68de7",
            "isRoot": false
          },
          "status": "UNDER_MAINTENANCE",
          "timestamp": "2025-07-23T04:32:44.919Z",
          "durationInMinutes": 243,
          "affectedComponents": []
        }
      ],
      "affectedComponents": []
    }
  ]
}
```

--------------------------------

### Example Incident: Reports of Slow Loading Times

Source: https://statusfield.com/status/abc-trainerize/incidents

Documents reports of slow loading times across the platform. This entry details the investigation process, the implementation of a fix, and ongoing monitoring to ensure performance restoration.

```APIDOC
Incident: Reports of Slow Loading Times
  Status: resolved
  Updates:
    - status: resolved
      message: "This incident has been resolved."
      timestamp: "2024-03-11T15:03:09.791-07:00"
    - status: monitoring
      message: "A fix has been implemented and we are monitoring the results."
      timestamp: "2024-03-11T14:48:15.295-07:00"
    - status: investigating
      message: "We've recently received reports regarding slow loading times on our platform. Our dedicated team is actively investigating the issue to ensure a swift resolution and restore optimal performance.\n\nWe understand the importance of a seamless experience, and we sincerely apologize for any inconvenience caused. Your patience and cooperation during this time are greatly appreciated.\n\nPlease rest assured that we're working diligently behind the scenes to address this matter promptly."
      timestamp: "2024-03-11T14:27:06.173-07:00"
  lastUpdate: "2024-03-11T15:03:10.154-07:00"
```