All Systems Operational

About This Site

We attempt to update our customers in realtime as issues either directly or indirectly impact DPS Cloud Services. All users of the DPS Support Desk are automatically registered for updates. If you'd like to receive realtime communications, please click subscribe on the top of this page.

The majority of the time, issues are related to customer Internet Service Providers (ISPs) or hand-offs between them. To check on current known Global ISP Issues, check both https://app.fing.com/internet/outages and https://downdetector.com

All systems are hosted in the Microsoft Azure Cloud. To check for Global Issues and Outages related to Microsoft Azure, visit https://status.azure.com and click on the continent that your system is hosted in. For issues related to Microsoft Office, visit https://status.office.com and click on the services you use.

For Global Issues and Outages related to Adobe Creative Cloud, visit http://status.adobe.com and click on the services you use.

If you are having an issue unrelated to any of this, please log a ticket at https://dpsadtracker.zendesk.com

Uptime over the past 90 days. View historical uptime.
DPS AdTracker®:Cloud Platform Services Operational
90 days ago
100.0 % uptime
Today
Order Entry / Business System Feeds Operational
AdTracker:Online (ATOL) Websites Operational
ATOL Services (Submission, Proofing, Insert, Mail) Operational
Output Systems (AutoEPS, Preflight, Toning) Operational
Third-Party Vendor Integrations Operational
Customer Provided Systems / Other Operational
FTP / SFTP Intake Services Operational
DPS AdTracker:AI Ad Copy Assistant Operational
90 days ago
100.0 % uptime
Today
DPS AdTracker®:Customer Support + Development Operational
DPS Connect Remote Support (connect.dpsadtracker.com) Operational
DPS Help Desk (dpsadtracker.zendesk.com) Operational
Microsoft Azure + Office Cloud Services Operational
90 days ago
100.0 % uptime
Today
Azure Active Directory (AAD) Operational
Microsoft Teams + Phone System Operational
Windows Virtual Desktop (WVD) Operational
Datacenter / Internet Connectivity Operational
DPSCLOUD - USA-based Hosting Operational
DPSCLOUD - East Asia/Oceania-based Hosting Operational
DPSCLOUD - India-based Hosting Operational
Azure - North Central US (Chicago) Region Operational
Azure - South Central US (San Antonio) Region Operational
Azure - East Central (Virginia) Region Operational
Azure - East Asia (Hong Kong) Region Operational
Azure - New Zealand (Auckland) Region Operational
Azure - West India (Mumbai) Region Operational
Microsoft Office 365 Services Operational
Microsoft Bing Search Engine and Services Operational
90 days ago
100.0 % uptime
Today
Microsoft Copilot Operational
90 days ago
100.0 % uptime
Today
Azure OpenAI Services Operational
90 days ago
100.0 % uptime
Today
Third-Party Cloud Services + Applications Operational
90 days ago
100.0 % uptime
Today
Google Apps Google Docs Operational
Google Apps Google Drive Operational
Google Apps Google Chat Operational
Google Apps Gmail Operational
1Password AWS S3 (us-standard) Operational
1Password AWS CloudFront Operational
1Password AWS route53 Operational
1Password Syncing items between your devices Operational
1Password Sign in Operational
1Password Sign in Operational
1Password Syncing items between your devices Operational
1Password Access to passwords and other items Operational
1Password Multi-factor Authentication (MFA) Operational
1Password Saving password and other items Operational
1Password SSO (Single Sign On) Operational
1Password Multi-factor Authentication (MFA) Operational
1Password Saving password and other items Operational
1Password Access to passwords and other items Operational
Akamai Edge Delivery Operational
Akamai Global Traffic Management Operational
Akamai Image Management Operational
GitHub Copilot Operational
GitHub Actions Operational
GitHub API Requests Operational
GitHub Codespaces Operational
GitHub Git Operations Operational
GitHub Issues Operational
GitHub Packages Operational
GitHub Pages Operational
GitHub Pull Requests Operational
GitHub Webhooks Operational
GitHub Visit www.githubstatus.com for more information Operational
SendGrid API Operational
SendGrid Billing Operational
SendGrid Email Activity Operational
SendGrid API v3 Operational
SendGrid SMTP Operational
SendGrid API v2 Operational
SendGrid Marketing Campaigns Operational
SendGrid Statistics Operational
SendGrid Website Operational
SendGrid Event Webhook Operational
SendGrid Parse API Operational
OpenAI ChatGPT Operational
90 days ago
100.0 % uptime
Today
Google Search Engine and Services Operational
90 days ago
100.0 % uptime
Today
DuckDuckGo Search Engine and Services Operational
90 days ago
100.0 % uptime
Today
Adobe Creative Cloud (Login, Licensing, Cloud Services) Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 29, 2026

No incidents reported today.

Jun 28, 2026

No incidents reported.

Jun 27, 2026

No incidents reported.

Jun 26, 2026

No incidents reported.

Jun 25, 2026

No incidents reported.

Jun 24, 2026

No incidents reported.

Jun 23, 2026

No incidents reported.

Jun 22, 2026

No incidents reported.

Jun 21, 2026

No incidents reported.

Jun 20, 2026

No incidents reported.

Jun 19, 2026

No incidents reported.

Jun 18, 2026

No incidents reported.

Jun 17, 2026

No incidents reported.

Jun 16, 2026

No incidents reported.

Jun 15, 2026
Azure Website Errors
Resolved - Earlier today, some customers experienced intermittent errors or timeouts connecting to our hosted services. We want to share what happened and what we're doing about it.

What Happened

The root cause was SNAT (Source Network Address Translation) port exhaustion on the Azure App Service infrastructure hosting our platform. Each instance of our App Service is allocated a finite pool of SNAT ports, which Azure uses to manage outbound network connections. When demand for those ports exceeds what's available — even briefly — new connections are queued or dropped until ports are freed.

Two factors converged to create the condition:
Scaling behavior — An auto-scale rule reduced our instance count during a period of declining usage, as designed. However, usage began climbing again shortly after — and did so very rapidly, faster than the platform could provision additional instances to compensate. The reduced number of instances had a smaller combined SNAT port pool to absorb the increased connection demand.
Shared infrastructure pressure — Our App Service runs on an Azure stamp (a regional cluster of shared infrastructure) that also serves other Microsoft customers unrelated to DPS. A significant uptick in activity across that stamp created substantial additional pressure on available port capacity — and it was this pressure that ultimately pushed the environment over the edge into exhaustion.

What We Did

Microsoft was engaged and implemented mitigation steps on their end to help restore normal port availability. We also worked with them to identify configuration and architectural improvements on our side.

What We're Changing
Scaling policy adjustment — We are updating our auto-scale rules to be less aggressive about scaling down during active hours. Keeping additional instances running provides a larger SNAT port pool and reduces our exposure to demand spikes that follow a dip in usage. In today's case, usage rebounded very rapidly after the scale-down — faster than the platform could provision additional instances to compensate.
Connection pooling improvement — We have identified a code-level optimization that will reduce the number of SNAT ports consumed by implementing more efficient connection pooling. This improvement is being developed and will be delivered as a platform update.

What to Expect Next
We will continue to monitor closely and adjust our scaling configuration as needed. This is the first time we have encountered this condition, and we are treating it as a priority to ensure it does not recur.

Regarding the connection pooling update: when this change is ready for your BETA environment, we will need your prompt cooperation in testing and signing off so we can move quickly to production and realize the full benefit of the fix. We'll reach out with specifics as that work progresses — timing is still being assessed and could range from a quick turnaround to a few days of development work.

This type of condition has never happened in the 11 years we've been operating in Microsoft Azure, but is something we're now adjusting for.
Jun 15, 20:48 EDT
Identified - We have identified the issue across multiple customer Azure tenants -- including those owned and managed by customers not DPS -- as generating Socket Errors.

Here's where we're seeing that the Azure App Service is sometimes just not responding -- it's not even getting to code execution. The website calls the API and the API's web server doesn't even answer: "System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond."

This is outside of DPS control and we are escalating to Microsoft.
Jun 15, 14:00 EDT
Investigating - We are currently investigating an issue where multiple customer ATOL and other hosted websites are reporting a 500 Internal Server Error message. No code or database change has happened and we are gathering information to escalate to Microsoft, as these seem to be related to a socket error that's happening before any our code or customer provided code is involved. The random nature of this seems to make this harder to pinpoint -- making it likely it is something on the provided infrastructure.

This issue is degrading performance for some customers but others are fine. Even within the same customer, some users are fine.
Jun 15, 13:52 EDT
← Incident History Powered by Atlassian Statuspage