GuestPoint Outage History

GuestPoint is up right now

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

There were 3 GuestPoint outages since April 19, 2026 totaling 20h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://statuspage.guestpoint.com

Minor June 10, 2026

Availability Updates not going through for GuestPoint Premium / Su

Detected by Pingoru
Jun 10, 2026, 06:35 AM UTC
Resolved
Jun 10, 2026, 07:12 AM UTC
Duration
36m
Timeline · 2 updates
  1. investigating Jun 10, 2026, 06:35 AM UTC

    Availability updates are currently returning errors from Su. Su support have been informed and are investigating. Reservation collection is not affected.

  2. resolved Jun 10, 2026, 07:12 AM UTC

    Availability updates are going through OK again now. We will re-push the latest availability for the failed updates.

Read the full incident report →

Minor June 2, 2026

Issues updating availability and rates to Guestpoint Premium/Su

Detected by Pingoru
Jun 02, 2026, 04:18 AM UTC
Resolved
Jun 02, 2026, 05:51 AM UTC
Duration
1h 33m
Timeline · 5 updates
  1. investigating Jun 02, 2026, 04:18 AM UTC

    When switching to a new authentication model required by su, updates for availability and rates sent to Su are being rejected. Cause is being investigated by Su.

  2. investigating Jun 02, 2026, 04:28 AM UTC

    Note that reservation collection is also impacted.

  3. investigating Jun 02, 2026, 04:54 AM UTC

    Reservations are now being being collected using the old method. Rates and Availability updates remain impacted.

  4. monitoring Jun 02, 2026, 05:22 AM UTC

    Availability and Rate updates are being processed OK now. A full update of all rates and availability is underway for all connected properties to ensure the channel manager has the latest data. Reservations are being collected OK. We will continue monitoring the systems.

  5. resolved Jun 02, 2026, 05:51 AM UTC

    The issue has been resolved and all communication is OK now.

Read the full incident report →