Exely Outage History

Exely is up right now

Pingoru has recorded 7 incidents for Exely: 7 in the last 12 months and 3 in the last 90 days.

Source: status.exely.com

7incidents recorded
7last 12 months
3last 90 days
38 minutestypical duration

Incidents, newest first

Notice September 2, 2026 Investigating issue with the Extranet –

Started Sep 02, 2026, 03:18 AM UTC· resolved Sep 02, 2026, 03:18 AM UTC

  1. resolved Sep 02, 2026, 09:45 AM UTC

    We are currently investigating an issue with the displaying room type names in the "Reports" > "Bookings" section. Our team is actively working to identify the root cause. No products or services are affected.

Read the full incident report →

Notice August 19, 2026 Investigating issue with secure.exely.uz –

Started Aug 19, 2026, 07:44 AM UTC· resolved Aug 19, 2026, 07:44 AM UTC

  1. resolved Aug 19, 2026, 12:12 PM UTC

    We are currently investigating an issue affecting secure.exely.uz. Users may experience slow loading of their Exely account. Our team is actively working to identify the root cause. Thank you for your patience.

Read the full incident report →

Minor August 3, 2026 Investigating issue with Notifications in Exely PMS –

Started Aug 03, 2026, 04:59 AM UTC· resolved Aug 03, 2026, 04:59 AM UTC

  1. resolved Aug 03, 2026, 02:09 PM UTC

    We are currently investigating an issue affecting Exely PMS. The information about updates of PMS is still displaying even after closing it. Please click ESC button to skip it. Our team is actively working to identify the root cause. Thank you for your patience.

Read the full incident report →

Minor June 1, 2026 Investigating issue with Staystore 58m

Started Jun 01, 2026, 09:53 AM UTC· resolved Jun 01, 2026, 10:52 AM UTC

  1. investigating Jun 01, 2026, 09:53 AM UTC

    We are currently investigating an issue affecting Staystore. The issue affects, for example, all changes made in the extranet, availability/quotas/prices. The developers are investigating. Thank you for your patience.

  2. investigating Jun 01, 2026, 09:55 AM UTC

    All new events from 12:40 UTC+3 onward are being processed successfully. The incident impact window was from 12:45 to 12:54 UTC+3. All new changes made after 12:54 have been applied successfully

  3. resolved Jun 18, 2026, 10:52 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 17, 2026 StayStore - Incident resolved 3h 24m

Started Mar 17, 2026, 10:20 AM UTC· resolved Mar 17, 2026, 01:45 PM UTC

  1. investigating Mar 17, 2026, 10:20 AM UTC

    The issue affecting StayStore has been resolved. All systems are operating normally. We apologize for the disruption.

  2. investigating Jun 02, 2026, 12:40 PM UTC

    We are continuing to investigate this issue.

  3. resolved Jun 18, 2026, 10:54 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 1, 2026 This is an example incident –

Started Mar 01, 2026, 08:54 AM UTC· resolved Mar 01, 2026, 08:54 AM UTC

  1. investigating Mar 02, 2026, 08:38 AM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified Mar 02, 2026, 08:38 AM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring Mar 02, 2026, 08:38 AM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved Mar 02, 2026, 08:38 AM UTC

    Empathize with those affected and let them know everything is operating as normal.

Read the full incident report →