Service Status

All Systems Operational

About This Site

This page is used to share information about planned maintenance, ongoing maintenance, and ongoing changes or updates to service status. If you are an official representative of a Technolutions client and you are seeking to report a "site down" emergency, you may call 1-203-404-4911 and leave your name, the name of the client organization, a brief description of what is happening, and a callback number and email address. Only messages from official representatives of Technolutions clients are able to be processed.

Slate Operational
90 days ago
100.0 % uptime
Today
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.
Slate
Fetching
Slate Test Environments
Fetching
Jun 26, 2025

No incidents reported today.

Jun 25, 2025

No incidents reported.

Jun 24, 2025

No incidents reported.

Jun 23, 2025

No incidents reported.

Jun 22, 2025

No incidents reported.

Jun 21, 2025

No incidents reported.

Jun 20, 2025

No incidents reported.

Jun 19, 2025

No incidents reported.

Jun 18, 2025

No incidents reported.

Jun 17, 2025

No incidents reported.

Jun 16, 2025

No incidents reported.

Jun 15, 2025

No incidents reported.

Jun 14, 2025

No incidents reported.

Jun 13, 2025

No incidents reported.

Jun 12, 2025
Resolved - Earlier this morning, between approximately 8am and 10am Eastern Time, the HTML message bodies on a subset of scheduled mailings may have appeared blank when sending. A configuration update applied to background worker nodes temporarily resulted in some of these HTML messages failing to render at send time. All background worker nodes are rendering all HTML message bodies properly at this time. No transactional messages (e.g., form or event confirmation messages) were affected but, due to the specific and isolated nature of this issue, we are unfortunately unable to determine which specific HTML bodies may have failed to render properly at send time. We have put in place additional safeguards in order to help prevent this type of an issue from re-occurring during configuration updates in the future.
Jun 12, 11:05 EDT