🦊StackFox

DigitalOcean

Operational— checked 3d ago

Infrastructure & Hosting

Official Status

Components

API
Operational
Billing
Operational
BYOIP
Operational
Cloud Control Panel
Operational
Cloud Firewall
Operational
Community
Operational
DNS
Operational
Support Center
Operational
Reserved IP
Operational
WWW
Operational
Agentic Inference Cloud
Operational
App Platform
Operational
Container Registry
Operational
Droplets
Operational
Event Processing
Operational
Functions
Operational
GPU Droplets
Operational
Managed Databases
Operational
Monitoring
Operational
Networking
Operational
Network File Storage
Operational
Kubernetes
Operational
Load Balancers
Operational
Spaces
Operational
Spaces CDN
Operational
VPC
Operational
Volumes
Operational
CSPM
Operational

90-Day Uptime History

90 days agoToday
Issue-Free Days54 of 87d monitored
OperationalDegradedPartialOutageUnknown

Event Log

Resolved: Agent Timeouts While Retrieving Data from Knowledge BasesRESOLVED

Jul 2, 3:39 AM

Status changed to OperationalOperational

Jul 2, 3:39 AM

Status changed to DegradedDegraded

Jul 2, 12:27 AM

Status changed to DegradedDegraded

Jul 1, 6:27 PM

Resolved: DNS Lookup Failures for Managed DatabaseRESOLVED

Jul 1, 4:28 PM

Resolved: Droplet ResizeRESOLVED

Jul 1, 1:28 PM

Status changed to DegradedDegraded

Jul 1, 12:26 PM

DNS Lookup Failures for Managed DatabaseMINOR

We are continuing to investigate this issue.

Jul 1, 11:35 AM

Droplet ResizeNONE

Our Engineering team has identified the root cause of the issue affecting Droplet resizes using the "Downscale Anytime" option and has implemented a fix. Users should now be able to resize their Droplets using the "Downscale Anytime" option without experiencing any issues or errors. We are actively monitoring the situation to ensure the fix remains effective and will provide another update once the issue has been fully resolved.

Jul 1, 11:13 AM

Status changed to DegradedDegraded

Jul 1, 6:25 AM

Agent Timeouts While Retrieving Data from Knowledge BasesNONE

Our Engineering team has identified the issue causing Agents to experience timeouts while retrieving data from Knowledge Bases. Please be assured that our Engineering team is actively working on a fix and is treating this issue with high priority. 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 investigate your specific case further.

Jul 1, 6:25 AM

Status changed to OperationalOperational

Jul 1, 3:01 AM

Status changed to OperationalOperational

Jun 30, 9:01 PM

Status changed to OperationalOperational

Jun 30, 3:01 PM

Status changed to OperationalOperational

Jun 30, 9:01 AM

Status changed to OperationalOperational

Jun 30, 3:00 AM

Status changed to OperationalOperational

Jun 29, 9:00 PM

Status changed to OperationalOperational

Jun 29, 3:00 PM

Status changed to OperationalOperational

Jun 29, 9:00 AM

Status changed to OperationalOperational

Jun 29, 3:00 AM

Status changed to OperationalOperational

Jun 28, 9:00 PM

Status changed to OperationalOperational

Jun 28, 3:00 PM

Status changed to OperationalOperational

Jun 28, 9:00 AM

Status changed to OperationalOperational

Jun 28, 3:00 AM

Status changed to OperationalOperational

Jun 27, 9:00 PM

Status changed to OperationalOperational

Jun 27, 2:59 PM

Status changed to OperationalOperational

Jun 27, 8:59 AM

Resolved: Anthropic Inference Model AvailabilityRESOLVED

Jun 27, 4:45 AM

Anthropic Inference Model AvailabilityNONE

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.

Jun 27, 4:43 AM

Status changed to OperationalOperational

Jun 27, 2:59 AM

Status changed to OperationalOperational

Jun 26, 8:59 PM

Status changed to OperationalOperational

Jun 26, 2:59 PM

Status changed to OperationalOperational

Jun 26, 8:59 AM

Status changed to OperationalOperational

Jun 26, 2:59 AM

Status changed to OperationalOperational

Jun 25, 8:59 PM

Status changed to OperationalOperational

Jun 25, 2:59 PM

Status changed to OperationalOperational

Jun 25, 8:59 AM

Status changed to OperationalOperational

Jun 25, 2:59 AM

Status changed to OperationalOperational

Jun 24, 8:59 PM

Status changed to OperationalOperational

Jun 24, 2:58 PM

Status changed to OperationalOperational

Jun 24, 8:58 AM

Status changed to OperationalOperational

Jun 24, 2:58 AM

Status changed to OperationalOperational

Jun 23, 8:57 PM

Status changed to OperationalOperational

Jun 23, 2:57 PM

Status changed to OperationalOperational

Jun 23, 8:57 AM

Status changed to OperationalOperational

Jun 23, 2:57 AM

Status changed to OperationalOperational

Jun 22, 8:56 PM

Status changed to OperationalOperational

Jun 22, 2:56 PM

Status changed to OperationalOperational

Jun 22, 8:56 AM

Status changed to OperationalOperational

Jun 22, 2:55 AM

Status data polled every 60 seconds. History retained for 90 days. Snapshots stored on status changes.