Is it down for me?
Testing digitalocean.com from your device…
D
Is DigitalOcean down right now?
Most checked
Not listed? Type its address, like example.com, to check it now.
DigitalOcean is up
Our last check from one location (UtiBox server · Newark, US) found it answering normally in 77 ms.
Checked from Newark, USNext check in 60 s
Response timelive · Newark, US
77ms
Newark, USUS77 ms
Checking from 12 regions…
Request waterfall
Do all locations agree?
Live counters
People checking
Live01 · Is it working?
Status at a glance
UtiBox check · our ownUp
77ms
DigitalOcean is up. Total time to the final page on our latest check.
FromNewark, US
ServerNear Toronto, CA
Checked Full result
Community · quick voteLast 24 hours
Is DigitalOcean working for you?
Thanks, you said it works
What’s the problem? Pick one to send your answer.
No votes yet. Be the first to answer.
0 answers in the last 24 hours · 0 problem reports
One answer per person, counted for 24 hours.
Answers per hour
24 h agoNow
No answers in the last 24 hours
See what people say 0 posts today
Regionsour server so far
1/1 up
Only our server so far. The regional checks run when the page opens.
- Newark · US77 msour server
Median 77 mslocations by DB-IP
90-day history
UpDegradedDownNo data
—No measurements yet
90 days agoToday
Last 24 hours · response time, ms
User reports are in CommunityFrom the communityLive counts
0posts today
No posts yet. Be the first to say how DigitalOcean is working for you.
- “It’s down” in the last hour0
- People who voted, 24 h0
02 · How it was reached
The journey to digitalocean.com
Our latest check, step by step. Tap a step to open its full record.
Latest check ·
Response by regionFrom Newark, US to digitalocean.com (server near Toronto, CA)
-
- DNS lookup27 ms
- Connect2 ms
- TLS handshake51 ms
- First byte17 ms
Map locations are approximate, from IP addresses.IP location by DB-IP
Test from another country
Is DigitalOcean blocked or down in your country?
Our main check runs from Newark, US. Run the same test from up to 3 internet providers in another country to see whether digitalocean.com is blocked or broken there.
Probes by Globalping, a free network run by jsDelivr. One test uses up to 3 probes, home and mobile providers first.
For long-term evidence of website blocking, see OONI Explorer, where volunteers measure censorship around the world.
DigitalOcean not working? Try these fixes
01
Reload without cache
Press Ctrl + Shift + R (⌘ + Shift + R on a Mac).
02
Try a private window
Rules out extensions and stored cookies.
03
Switch networks
Move from Wi-Fi to mobile data, or the other way round.
04
Flush DNS
Windows: ipconfig /flushdns · macOS: sudo dscacheutil -flushcache
05
Pause VPN or ad blocker
They can block or reroute requests.
06
Check the time on your device
A wrong clock breaks secure connections.
Still stuck? Find out if the problem is your own connection.Test my connection
Outage historyAll outages
| Date | Problem | Duration | Peak reports | Status |
|---|---|---|---|---|
| No confirmed incidents recorded for DigitalOcean. | ||||
Share this statusFree to embed
The badge shows whether digitalocean.com is up and the share of our checks that were up over the last 7 days. It updates every few minutes.
Status report (PDF)
A landscape PDF of this page: the result now, 90 days of uptime, every layer of the latest check, other places, outages and the response headers. Each copy gets its own reference and a QR code anyone can scan to verify it.
Community · digitalocean.com
DigitalOcean community
What people say about DigitalOcean, in their own words, kept apart from our own checks.
0posts today
0“it’s down” in the last hour
0people voted, 24 h
Live counts · real numbers, refreshed with the page
Share how DigitalOcean is working for you
What’s the problem? (optional)
0 / 280
Optional. We never show your exact location.
Posts are public after a quick review. Don’t share personal details or links.
Posts
No posts yet.
Be the first to say how DigitalOcean is working for you.
No posts of this type yet.
That’s every post from the last 30 days.
Is DigitalOcean working for you?
Last 24 hours0say it works
0have a problem
No votes yet
What’s the problem? Pick one to send your answer.
One answer per person, counted for 24 hours.
User reports, last 24 h
0 total24 h ago12 hNow
Problem types
last 24 hoursHaving one of these? Tap it to start a report.
Official · provider-reported
DigitalOcean official status
What DigitalOcean status says about its own service, read from its public status page. A separate signal from our own check and from what people report.
Official · reported by DigitalOcean status
status.digitalocean.com
Maintenance
Service Under Maintenance
Read from the official feed · the provider last updated it .
What DigitalOcean status reports about DigitalOcean. A site can answer our own check while the provider reports a problem with one of its features, and the other way round.
Status information is provided by the service operator. UtiBox is independent and isn’t affiliated with DigitalOcean. It may not reflect regional or account-specific problems.
Components
27 of 28 operational- NetworkingUnder maintenance
- APIOperational
- BillingOperational
- BYOIPOperational
- Cloud Control PanelOperational
- Cloud FirewallOperational
- CommunityOperational
- DNSOperational
- Support CenterOperational
- Reserved IPOperational
- WWWOperational
- Agentic Inference CloudOperational
- App PlatformOperational
- Container RegistryOperational
- DropletsOperational
- Event ProcessingOperational
Show all 28 components
- FunctionsOperational
- GPU DropletsOperational
- Managed DatabasesOperational
- MonitoringOperational
- Network File StorageOperational
- KubernetesOperational
- Load BalancersOperational
- SpacesOperational
- Spaces CDNOperational
- VPCOperational
- VolumesOperational
- CSPMOperational
Open incidents
None
None reported for DigitalOcean in the last report we read.
Planned maintenance · 1
Storage Network Maintenance in TOR1 In progress
13 Nov 15:30–19:00 UTC
AffectsTOR1
Our record of the official status
Last 30 days · the worst state we read each day30 days agoToday
OperationalMaintenanceNot read
Our first successful read in this window was on 9 Nov 2026.
Past official updates
Newest first43 resolved updates since May 2026 · 6 major · last one 27 Oct 2026 (3 h 40 min)
- Oct 2026 · 5
-
Kubernetes Cluster Management Operations
“Our Engineering team is currently investigating an issue affecting Managed Kubernetes cluster operations. During this time, Customers may experience delays or failures when attempting to create, delete, scale, or upgrade clusters, as well as with other management tasks. Existing workloads running on Managed Kubernetes are not affected and will continue to operate normally. Our Engineering team is actively investigating and treating this with the highest priority. We will provide another update as soon as more information becomes available.”
AffectedGlobalRead on DigitalOcean status -
App Platform Deployments
“Between 04:34 and 12:15 UTC, customers experienced service interruptions affecting App Platform deployment operations. During this window, customers may have been unable to deploy new applications or scale existing deployments. Applications already running prior to the incident were unaffected and continued to operate normally. The disruption was caused by a software update that prevented application containers from starting on newly provisioned infrastructure nodes. Our Engineering team rolled back the update and restored the affected nodes. App Platform deployment and scaling operations…”
AffectedGlobalRead on DigitalOcean status -
DNS Resolution for Managed Kubernetes
“Our Engineering team is investigating an issue causing intermittent external DNS lookup failures for Managed Kubernetes clusters in multiple regions. Applications running on affected clusters may intermittently fail to resolve external domain names. We apologize for the inconvenience and will provide further updates as more information becomes available.”
AffectedGlobalRead on DigitalOcean status -
VPC Networking Availability
“Our Engineering team identified a disruption affecting VPC Networking operations that began at approximately 08:48 UTC. During this time, customers may have experienced delays or failures when creating or deleting VPC peerings, VPC Native DOKS clusters, or Private Network Connections (PNCs), as well as when adding cluster members. Creating routes and subnets may also have been affected. Operations are now returning to normal, and our Engineering team is monitoring the affected systems to ensure continued stability. Existing VPC resources and network connectivity remain unaffected. We will…”
AffectedGlobalRead on DigitalOcean status -
A Network Disruption in BLR1 Region Impacted Multiple Products (Resolved)
“From 11:59 UTC to 13:02 UTC on October 3, 2026, a networking disruption in our BLR1 region affected multiple products, including Monitoring, App Platform, Managed Databases, Functions, Load Balancers, Spaces, and the Cloud Control Panel. During this period, some users experienced degraded connectivity, increased latency, or intermittent errors when accessing resources in the region. Multiple network paths operated by our upstream connectivity providers were unavailable, including redundant paths intended to maintain connectivity during a disruption. Traffic shifted to a remaining link with…”
AffectedBangaloreBLR1BLR1BLR1BLR1BLR1BLR1BLR1Read on DigitalOcean status - Sep 2026 · 2
-
Support Portal Service Disruption
“Our Support Portal is currently experiencing issues due to a third-party service disruption impacting our systems. During this time, customers may be unable to access the Support Portal or create new support tickets for their concerns. Existing support requests may also experience delayed responses from our Support team. As a workaround if you're unable to access the Support Portal or need to create a new support ticket, please submit your request via Support Contact form: https://www.digitalocean.com/company/contact/support. We apologize for the inconvenience and appreciate your patience…”
AffectedSupport CenterRead on DigitalOcean status -
Power Degradation impacting GPU Performance in ATL1
“We are investigating a power issue affecting part of our ATL1 datacenter. Redundant power systems are keeping servers online, and we have not observed any server outages. However, available power capacity is reduced, which may cause degraded performance for some GPU workloads, particularly during periods of high utilization. Our datacenter and infrastructure teams are working to restore full power redundancy. We will provide an update as more information becomes available. We apologize for the inconvenience and appreciate your patience.”
AffectedATL1Read on DigitalOcean status - Aug 2026 · 10
-
Cloud Control Panel and API
“Our Engineering team is investigating an issue impacting the DigitalOcean public API and Cloud Control Panel. At this time, users will see elevated 5xx errors for all API requests, including things like creates for various products. Users may also be unable to access cloud.digitalocean.com. We are actively investigating the root cause and will provide updates as soon as more information becomes available. We apologize for the inconvenience and appreciate your patience.”
AffectedAPICloud Control PanelRead on DigitalOcean status -
Managed Databases Creation
“Our Engineering team is investigating an issue with our Managed Database product. At this time, users may experience errors while creating clusters, both via Cloud Control Panel and API requests. We apologize for the inconvenience and will share an update once we have more information.”
AffectedNYC1NYC3Read on DigitalOcean status -
Container Registry and Spaces Accessibility
“Our Engineering team is currently investigating reports of an issue affecting Container Registry and Spaces buckets in some regions. During this time, customers may experience failures when pushing or pulling container images. Additionally, customers may experience issues accessing Spaces via the Cloud Control Panel, where the page may display "Looks like something went wrong…" Our Engineering team is actively investigating the issue and treating it with priority. We will provide another update as soon as more information becomes available.”
AffectedGlobalGlobalRead on DigitalOcean status -
Major Service Interruption in MKC1
“Our Engineering team is currently investigating an issue in the MKC1 region affecting multiple racks and nodes. During this time, customers may experience disruptions to GPU workloads, and Kubernetes (DOKS) worker nodes may enter a NotReady state. Our team is actively working to restore connectivity and bring impacted nodes back online. If you continue to experience issues, please open a support ticket from within your account.”
AffectedMKC1MKC1Read on DigitalOcean status -
Volume Attach/Detach events in FRA1
“Between Aug 13, 09:50 UTC and 14:30 UTC, customers in the FRA1 region experienced an issue affecting Block Storage Volumes attachment and detachment operations on Droplets and Managed Kubernetes clusters. During this window, customers may have encountered delays or been unable to attach and detach Block Storage Volumes from their resources. Block Storage Volumes attachment and detachment operations now appear to be functioning normally, and customers should no longer experience issues with these operations. For Managed Kubernetes clusters specifically, some residual cleanup of affected…”
AffectedFRA1Read on DigitalOcean status -
Account Registration, Droplets, and Related Services
“Our Engineering team is currently investigating reports of an issue affecting new account registration, Reserved IPs, Snapshots, Droplets and Droplet-based services across multiple regions. During this time, customers may be unable to create new accounts, create Droplets, allocate Reserved IPs, or perform Automated Backups and Snapshots operations. Droplet Autoscale scaling operations and DOKS cluster operations are also affected. Our Engineering team is actively investigating the issue and we will provide another update as soon as more information becomes available.”
AffectedGlobalGlobalGlobalReserved IPRead on DigitalOcean status -
Functions on App Platform
“Our Engineering team is investigating an issue impacting Functions on App Platform. During this time, users may experience build/deploy failures for Functions components, and requests to Functions endpoints may fail with a 504 error, caused by an SSL error when App Platform attempts to forward requests to Functions. This issue currently appears to be isolated to Functions deployed within App Platform. We apologize for the inconvenience and will share an update once we have more information.”
AffectedGlobalGlobalRead on DigitalOcean status -
Multiple Services Availability
“Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing. Customers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was…”
AffectedGlobalGlobalGlobalGlobalGlobalCloud FirewallDNSRead on DigitalOcean status -
Spaces Cold Storage Billing
“Our Engineering team is investigating an issue affecting Spaces Cold Storage billing. During this time, customers with cold storage buckets may see incorrect values reflected in their daily usage and current invoices. We apologize for the inconvenience and are actively working to resolve the issue. We will provide an update as soon as more information becomes available.”
AffectedGlobalBillingRead on DigitalOcean status -
Cloud Control Panel Access
“Beginning at 09:36 UTC on August 3, some customers may experience intermittent errors when accessing the DigitalOcean Cloud Control Panel, including an "mTLS verification failed" message. Our engineering team is actively investigating. We apologise for the inconvenience this may have caused. We will provide another update as soon as more information is available. If you have any questions related to this issue, please send us a ticket from your cloud support page. https://cloudsupport.digitalocean.com/s/createticket”
AffectedCloud Control PanelRead on DigitalOcean status - Jul 2026 · 16
-
Response Degradation Impacting Kimi-K3
“We are currently investigating this issue.”
AffectedModel ServicesRead on DigitalOcean status -
Agent Platform Requests Returning HTTP 500 Errors
“We are currently investigating this issue.”
AffectedAgent RuntimeRead on DigitalOcean status -
Network Connectivity from India to NYC
“We have noticed network connectivity issues affecting some users connecting from India to resources in the NYC region. Based on our current investigation, users on Airtel and BSNL have reported increased latency, packet loss, or intermittent connectivity. We apologize for the inconvenience and will provide an update as soon as more information becomes available.”
AffectedNYC1Read on DigitalOcean status -
Llama-4-Maverick Model Availability
“Our Engineering team is currently investigating an issue where the llama-4-maverick model is unavailable. Users may experience HTTP 500 errors while using this model with Serverless Inference. We apologize for the inconvenience. Our Engineering team is working with high priority to resolve the issue. Thank you for your patience and understanding.”
AffectedInferenceRead on DigitalOcean status -
Gradient AI Serverless Inference Requests Timing Out for qwen3.5-397b-a17b
“We are currently investigating this issue.”
AffectedInferenceRead on DigitalOcean status -
Block Storage Volume NYC1, NYC3, SGP1, SYD1 and BLR1
“Our Engineering team is investigating an issue with attaching volume to the droplets in the NYC1, NYC3, SGP1, SYD1 and BLR1 regions. During this time you may experience an issue with attaching volume to the Droplet(s). We apologize for the inconvenience and will share an update once we have more information.”
AffectedBLR1NYC1NYC3SGP1SYD1Read on DigitalOcean status -
Networking in BLR1
“We are currently investigating an issue affecting outbound network traffic for Droplets in the BLR1 region. Customers may experience timeout errors or connectivity issues when attempting to reach external services. Our Engineering team is actively investigating the issue and working to identify the root cause. We will provide additional updates as soon as more information becomes available.”
AffectedBLR1Read on DigitalOcean status -
Reserved IP routing in TOR1
“Our Engineering team is investigating an issue affecting Reserved IP routing in the TOR1 region. The issue is causing inbound and outbound traffic to and from Reserved IPs in TOR1 to fail. In the meantime, detaching and reassigning the Reserved IP to the Droplet may restore connectivity. We recommend trying this workaround if you are experiencing issues with your Reserved IP in TOR1. Our engineering team is actively investigating the root cause and working towards a resolution. We will provide updates as more information becomes available.”
AffectedReserved IPTOR1Read on DigitalOcean status -
Serverless Inference - Gemma4 Latency Issues Causing Timeouts & Slow Responses
“We are currently experiencing an issue where customers using the Gemma 4 model on our Serverless Inference and Dedicated Inference platforms may experience severe latency or request timeouts. Our engineering team has identified a backend configuration issue as the root cause, which is temporarily degrading performance. We are actively working on a fix to restore normal response times and will provide another update as soon as the mitigation is in place”
AffectedInferenceRead on DigitalOcean status -
Kubernetes Deployments in NYC1
“Our Engineering team is investigating an issue affecting Kubernetes deployments in NYC1. Users may see intermittent DNS failures and NodeNotReady events from application workloads during this time. We apologize for the inconvenience, we'll share new information on this page as soon as it is available.”
AffectedNYC1Read on DigitalOcean status -
Limited access to Deepseek V4 Pro model
“Our Engineering team is investigating reports of an incident affecting the Deepseek V4 Pro model in Serverless Inference and Agent Platform. Users may experience errors when attempting to use this model, specifically receiving error 429 messages. We apologize for the inconvenience and are working to resolve the issue as soon as possible. We will provide an update once we have more information.”
AffectedInferenceModel ServicesRead on DigitalOcean status -
Droplet Actions in NYC3
“Our Engineering team has implemented a fix to address the issue affecting Droplets in the NYC3 region. The issue, which began at 12:38 UTC, caused disruptions to customers attempting to perform actions on their Droplets in the NYC3 region. During this time, customers may also have experienced errors when trying to create Droplets in this region. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.”
AffectedNYC3NYC3Read on DigitalOcean status -
Managed Database Clusters
“Our engineering team is investigating an issue affecting Managed Database Clusters. Currently, users may encounter delays when creating/scaling/forking and restoring Standard MySQL, Standard PostgreSQL, OpenSearch, Kafka, and Valkey clusters through the Cloud Control Panel or API. We apologize for the inconvenience and will provide further updates as soon as more information is available.”
AffectedGlobalGlobalRead on DigitalOcean status -
DNS Lookup Failures for Managed Database
“As of 06:39 UTC, our Engineering team is investigating reports of intermittent DNS lookup failures for Managed Database hostnames from Managed Kubernetes, primarily affecting connections from Managed Kubernetes to Managed Database hostnames. At this point, customers in the FRA1 region may experience intermittent connectivity issues. We apologize for the inconvenience and will share an update once we have more information.”
AffectedFRA1FRA1DNSRead on DigitalOcean status -
Droplet Resize
“Our Engineering team is investigating an issue affecting Droplet resizes using the "Downscale Anytime" option. At this time users may find this option unavailable or unresponsive in the Cloud Control Panel. As a workaround, resizes can be performed via the API while we work to resolve this issue. We apologize for the inconvenience and will share an update once we have more information.”
AffectedCloud Control PanelRead on DigitalOcean status -
Agent Timeouts While Retrieving Data from Knowledge Bases
“Our Engineering team is currently investigating an issue where Agents are experiencing timeouts while retrieving data from Knowledge Bases. As a result, affected Agents may fail to retrieve data and return the following error: "Failed to retrieve data from Knowledge base(s) - timeout" Please be assured that we are treating this as a high-priority issue and are actively working to mitigate it. We sincerely apologise for any inconvenience this may have caused and appreciate your patience and understanding. If you have any further questions, please create a support ticket so that we can…”
AffectedAgent RuntimeKnowledge BasesRead on DigitalOcean status - Jun 2026 · 6
-
Droplet Backup Service
“Between 00:00 UTC & 16:00 UTC today, our Engineering team identified an issue affecting backup operations on Droplets. During this period, backups scheduled within this window may not have been created and may appear as missing. Our team has taken necessary measures to resolve the issue, and we can confirm that the backup service has been restored and is now functioning normally. Upcoming scheduled backups should be performed as expected. We sincerely apologize for any inconvenience this may have caused and appreciate your understanding. However, if you have any further questions or…”
AffectedGlobalRead on DigitalOcean status -
Anthropic Inference Model Availability
“Our Engineering team has mitigated an issue with Anthropic models. Previously, users may have encountered 400 errors when attempting to use any Anthropic model. Although the root cause of the issue is still being addressed by Anthropic, users should now be able to access and use Anthropic models again. We will continue to monitor the situation and provide updates if necessary. If you continue to experience problems, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.”
AffectedInferenceRead on DigitalOcean status -
Monitoring Graphs in the Cloud Control Panel
“Our Engineering team is currently investigating an issue affecting the visibility of monitoring graphs within the Cloud Panel. During this period, users may notice missing or unavailable monitoring graphs for services such as Droplets(with DO agent installed), Load Balancers, Databases, etc. We apologize for the inconvenience caused. We'll update once we have more information”
AffectedGlobalRead on DigitalOcean status -
Intermittent 500 Errors on Serverless/GenAI Inference API
“We are actively investigating an issue causing elevated HTTP 500 error rates for customers utilizing our Serverless/GenAI Inference API. Customer Impact: Customers making calls to the inference API—specifically targeting /v1/* endpoints—will experience intermittent HTTP 500 errors and failed requests.”
AffectedInferenceRead on DigitalOcean status -
DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"
“We are currently facing issues with Gradient AI DeepSeek V4 Pro is returning HTTP 429 "Rate limit exceeded"”
AffectedModel ServicesRead on DigitalOcean status -
DNS API Service
“Our Engineering team is investigating an issue impacting our DNS API service. During this time, users may experience issues performing domain and DNS record management operations from the Control Panel and API, including creating, updating, or deleting DNS records. As a result, services that rely on DNS API operations, such as Let's Encrypt certificate provisioning and MongoDB cluster creation, may also be impacted. We apologize for the inconvenience and will share an update once we have more information.”
AffectedGlobalGlobalGlobalDNSRead on DigitalOcean status - May 2026 · 4
-
App Platform Deployments
“Our Engineering team is currently investigating an issue with build failures on App Platform in multiple regions. Users may experience errors when attempting to build their applications, resulting in failed deployments. Our Engineering team is working to fix the issue and will share an update once we have more details. We apologize for the inconvenience this issue may be causing and appreciate your patience as we work to resolve it.”
AffectedGlobalRead on DigitalOcean status -
Cloud Firewall
“Our engineering team identified an issue impacting Cloud Firewall Product. During this time, users may notice HTTP 500 errors when updating firewalls. We apologize for the inconvenience and will share an update once more information is available.”
AffectedCloud FirewallRead on DigitalOcean status -
Cloud Firewall
“We are currently investigating an issue with incorrect Cloud Firewall rules appearing on the cloud panel. Our engineering team is aware of the situation and actively working to identify the root cause. Since this is a user interface issue, users should not experience any problems with other services or networking. We apologize for the inconvenience and appreciate your patience. We will continue to provide updates as we learn more.”
AffectedCloud FirewallRead on DigitalOcean status -
Block Storage Volume Performance
“Our Engineering team is currently investigating an ongoing infrastructure issue in the NYC3 region affecting Block Storage Volumes at the storage layer. Users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure. We apologize for the inconvenience and will continue to provide updates as more information becomes available.”
AffectedNYC3Read on DigitalOcean status
No updates of this kind.
From DigitalOcean status’s public status history. UtiBox keeps the official updates it reads for 180 days.
Frequently asked questions
Is DigitalOcean down right now?
At our last check from UtiBox server · Newark, US, DigitalOcean was up and answering normally. The page refreshes the check automatically.
What does DigitalOcean’s official status page say?
The official status page (status.digitalocean.com) reports “Maintenance” for DigitalOcean. We read it every few minutes. It’s separate from our own check of the digitalocean.com website above, so the two can differ.
Why is DigitalOcean not working for me?
If it’s up here but not for you, the problem is usually local: your connection, DNS, a browser extension, a VPN or a block on your network. Try the fixes on this page, then the Is It My Internet? check.
How do you check DigitalOcean?
Our server requests digitalocean.com and looks at every layer: DNS, the connection, the TLS certificate, the HTTP answer, redirects and the page content. We also check it from up to 12 locations in other countries, using two free probe networks (Globalping and check-host.net), so a regional outage can show here too.
How often is this page updated?
A result is shared for 60 seconds when the site is up and 30 seconds when it has problems, then checked again. You can refresh it yourself after 30 seconds.
Can I get an alert when it’s back?
Yes. Use “Alert me when it’s back” and we’ll send one email when our check reaches it again. Guests confirm their address first.