Visit Outage History

Visit is up right now

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

There were 3 Visit outages since September 22, 2024 totaling 3h 43m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.visitcloud.com

Notice October 20, 2025

HTML editor

Detected by Pingoru
Oct 20, 2025, 08:27 AM UTC
Resolved
Oct 20, 2025, 11:24 AM UTC
Duration
2h 56m
Affected: Create
Timeline · 2 updates
  1. monitoring Oct 20, 2025, 08:27 AM UTC

    At the moment, there is an issue with editing HTML text in Visit Create. Visit uses a licensed library. This service is currently down and it affects our application. You can check the status at https://status.tiny.cloud

  2. resolved Oct 20, 2025, 11:24 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 24, 2025

System slow/interruptions

Detected by Pingoru
Jan 24, 2025, 10:39 AM UTC
Resolved
Jan 24, 2025, 11:12 AM UTC
Duration
33m
Affected: CreateConnectDiscoverRegisterDocument DownloadApi
Timeline · 3 updates
  1. investigating Jan 24, 2025, 10:39 AM UTC

    Sorry, we’re having a small technical issue. Our engineers have been informed and are working to fix it. Please try again soon.

  2. monitoring Jan 24, 2025, 11:07 AM UTC

    We experienced a peak load on our system, which sometimes caused slight delays. After investigation, we found that this had little impact on live registrations. We are closely monitoring the situation.

  3. resolved Jan 24, 2025, 11:12 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 22, 2024

Release issue

Detected by Pingoru
Sep 22, 2024, 09:33 PM UTC
Resolved
Sep 22, 2024, 09:46 PM UTC
Duration
13m
Affected: CreateConnectDiscoverRegisterDocument DownloadApi
Timeline · 3 updates
  1. investigating Sep 22, 2024, 09:33 PM UTC

    Due to unexpected complications, the release process is taking longer than expected. We are urgently working on a solution.

  2. monitoring Sep 22, 2024, 09:43 PM UTC

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

  3. resolved Sep 22, 2024, 09:46 PM UTC

    This incident has been resolved.

Read the full incident report →