Skip to main content
Service disruption

HostingSwift status

Every number here is measured, not claimed. We probe each service as a customer would, every 60 seconds, from 3 independent locations, and publish the results unedited.

Updated Oct 28, 2026, 09:56 PM UTC · public monitoring since 2026-10-20

Services

Website
Operational· 234 ms
90 days ago7d 98.56% · 30d 98.76% · 90d 98.76%Today
Client area & billing
Operational· 105 ms
90 days ago7d 98.74% · 30d 98.85% · 90d 98.85%Today
Platform API & database
Operational· 22 ms
90 days ago7d 99.993% · 30d 99.994% · 90d 99.994%Today
Global edge network
Operational· 882 ms
90 days ago7d 100% · 30d 100% · 90d 100%Today
GeoDNS
Operational· 107 ms
90 days ago7d 99.997% · 30d 99.997% · 90d 99.997%Today
Radio streaming
Operational· 64 ms
90 days ago7d 100% · 30d 100% · 90d 100%Today
Video streaming
Operational· 25 ms
90 days ago7d 100% · 30d 100% · 90d 100%Today
AI API gateway
Operational· 5 ms
90 days ago7d 99.02% · 30d 99.14% · 90d 99.14%Today
dnsdigi.com
Outage
90 days ago7d 98.24% · 30d 98.48% · 90d 98.48%Today

Grey bars are days before monitoring began, or with no samples. Uptime counts a service as up when it passes its probes; a partial degradation (for example one edge location down while traffic is re-routed) is shown amber but is not counted as downtime. OurSLA sets the commitment.

Incident history

Last 90 days. Automatic detections are opened by monitoring; staff add the root cause afterwards.

Resolved

Website unavailable

Website

Oct 28, 2026, 01:57 PM UTC · 7 minutes

Our automated monitoring detected that Website is not responding from multiple locations. We are investigating.

  1. investigating — Detected by automated monitoring. Oct 28, 2026, 02:00 PM UTC
  2. resolved — Monitoring confirms service has recovered. Oct 28, 2026, 02:04 PM UTC
Resolved

Website unavailable

Website

Oct 27, 2026, 06:29 PM UTC · 10 minutes

Our automated monitoring detected that Website is not responding from multiple locations. We are investigating.

  1. investigating — Detected by automated monitoring. Oct 27, 2026, 06:32 PM UTC
  2. resolved — Monitoring confirms service has recovered. Oct 27, 2026, 06:39 PM UTC
Resolved

Website unavailable

Website

Oct 26, 2026, 07:33 PM UTC · 7 minutes

Our automated monitoring detected that Website is not responding from multiple locations. We are investigating.

  1. investigating — Detected by automated monitoring. Oct 26, 2026, 07:36 PM UTC
  2. resolved — Monitoring confirms service has recovered. Oct 26, 2026, 07:40 PM UTC
Resolved

Website unavailable

Website

Oct 26, 2026, 05:17 PM UTC · 5 minutes

Our automated monitoring detected that Website is not responding from multiple locations. We are investigating.

  1. investigating — Detected by automated monitoring. Oct 26, 2026, 05:20 PM UTC
  2. resolved — Monitoring confirms service has recovered. Oct 26, 2026, 05:22 PM UTC
Resolved

AI API gateway unavailable

AI API gateway

Oct 23, 2026, 05:03 AM UTC · 99 minutes

Our automated monitoring detected that AI API gateway is not responding from multiple locations. We are investigating.

  1. investigating — Detected by automated monitoring. Oct 23, 2026, 05:06 AM UTC
  2. resolved — Monitoring confirms service has recovered. Oct 23, 2026, 06:42 AM UTC
Resolved

AI API gateway unavailable

AI API gateway

Oct 20, 2026, 04:30 PM UTC · 7 minutes

Automated monitoring detected the AI API gateway returning errors while its routing configuration was being updated.

  1. investigating — Detected by automated monitoring: the public AI API returned errors from multiple locations. Oct 20, 2026, 04:30 PM UTC
  2. resolved — Monitoring confirms service has recovered. The gateway routing configuration was being updated at the time. Oct 20, 2026, 04:37 PM UTC
Resolved

Brief website outage during an application restart

Website

Oct 20, 2026, 02:11 PM UTC · 90 seconds

The web application took 90 seconds to stop during a routine restart because it did not respond to the shutdown signal, so the site returned errors for about 90 seconds. This was a single event; we found no repeat in the previous 14 days.

  1. resolved — Service restarted and the site recovered. Oct 20, 2026, 02:12 PM UTC
  2. resolved — Root cause fixed: the stop timeout was cut from 90s to 15s and the service now restarts in about 11 seconds. We also added a second and third web node so a restart on one is invisible to visitors. Oct 20, 2026, 02:26 PM UTC

See something wrong?

If a service looks unhealthy on your side, open a ticket or email us and we will investigate immediately.