Apptegy Outage History

Apptegy is up right now

There were 10 Apptegy outages since February 12, 2026 totaling 464h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.apptegy.com

Minor April 28, 2026

We are investigating reports of Documents that are not accessible

Detected by Pingoru
Apr 28, 2026, 01:59 PM UTC
Resolved
Apr 28, 2026, 02:20 PM UTC
Duration
21m
Affected: Media/CMSClient Websites
Timeline · 2 updates
  1. investigating Apr 28, 2026, 01:59 PM UTC

    We are investigating reports that some Documents are not available, both within the Media section and on public websites. Some document links are not resolving as expected, and some documents aren't able to be edited. We expect to have a resolution within the next hour.

  2. resolved Apr 28, 2026, 02:20 PM UTC

    We have deployed a fix and have confirmed that previously inaccessible Documents are now working as expected. We have also verified that Documents can be reliably edited and remain accessible after changes are made.

Read the full incident report →

Minor April 21, 2026

Delayed Alerts processing

Detected by Pingoru
Apr 21, 2026, 03:39 PM UTC
Resolved
Apr 15, 2026, 10:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Apr 21, 2026, 03:39 PM UTC

    On the evening of April 15th, 2026 between 5:30 PM and 8:00 PM CDT, we observed instances where Alerts were delayed and a small number of Alerts were not successfully generated. In some cases, Alerts appeared as "Published" in Analytics but did not reach recipients. Our engineering team identified the root cause and implemented the necessary changes to address this issue.

Read the full incident report →

Notice April 20, 2026

Duplicate Alert deliveries reported

Detected by Pingoru
Apr 20, 2026, 11:01 PM UTC
Resolved
Apr 21, 2026, 02:43 PM UTC
Duration
15h 42m
Affected: Alerts
Timeline · 2 updates
  1. investigating Apr 20, 2026, 11:01 PM UTC

    We are investigating reports of duplicate Alerts sent between 4:15 PM and 4:45 PM CDT today (April 20th) that appear to be repeats of Alerts originally sent on April 15th. We will follow up with additional information as it becomes available.

  2. resolved Apr 21, 2026, 02:43 PM UTC

    We have completed our investigation into the duplicate Alerts sent between 4:15 PM and 4:45 PM CDT on April 20, 2026. A deployment unexpectedly restarted a small number of previously queued jobs, resulting in Alerts originally intended for April 15th to be sent on April 20th. We have implemented updated expiration rules that will prevent this from occurring again in the future.

Read the full incident report →

Minor April 17, 2026

Documents are inaccessible for some regional ISP users

Detected by Pingoru
Apr 17, 2026, 03:21 PM UTC
Resolved
Apr 29, 2026, 10:08 PM UTC
Duration
12d 6h
Affected: Media/CMSOther Services
Timeline · 3 updates
  1. investigating Apr 17, 2026, 03:21 PM UTC

    We are currently investigating an issue where some users are unable to access documents. Our initial findings indicate that this is isolated to specific regional internet service providers. The issue appears to be related to the provider's default DNS servers failing to resolve some AWS content. We will follow up with additional information as it becomes available.

  2. monitoring Apr 17, 2026, 04:29 PM UTC

    We have contacted the relevant internet service providers exhibiting this issue in order to share our findings. We are now awaiting confirmation that they are taking the actions necessary to resolve the DNS resolution errors.

  3. resolved Apr 29, 2026, 10:08 PM UTC

    We previously provided guidance to the relevant ISPs for them to address stale DNS records. We will continue to monitor for any additional reports and will reopen this incident if necessary.

Read the full incident report →

Minor April 10, 2026

Intermittent Login Failures

Detected by Pingoru
Apr 10, 2026, 03:02 PM UTC
Resolved
Apr 11, 2026, 05:28 PM UTC
Duration
1d 2h
Affected: Media/CMS
Timeline · 7 updates
  1. investigating Apr 10, 2026, 02:10 PM UTC

    Our team has identified an issue where some users are unable to log in. We are investigating the root cause and will follow up with additional information by 10am CDT.

  2. identified Apr 10, 2026, 03:02 PM UTC

    Our team has identified the issue affecting user login. We are currently preparing to deploy changes and we will follow up with additional information by 11am CDT. Users that are unable to login should be able to resolve the issue by clearing their browser cache using the instructions below: Chrome: https://support.google.com/accounts/answer/32050 Firefox: https://support.mozilla.org/en-US/kb/clear-cookies-and-site-data-firefox Edge: https://support.microsoft.com/en-us/microsoft-edge/view-and-delete-browser-history-in-microsoft-edge-00cf7943-a9e1-975a-a33d-ac10ce454ca4 Safari: https://support.apple.com/guide/safari/manage-cookies-sfri11471/mac

  3. monitoring Apr 10, 2026, 04:02 PM UTC

    Our team has completed deploying required changes, the login issue should now be resolved. Users that are still unable to login should attempt to refresh their browser. We will continue monitor the performance of user login throughout the rest of the day.

  4. identified Apr 10, 2026, 06:15 PM UTC

    Our team has identified another change that needs to be deployed in order to fully address this issue. We will follow up with additional information by 2:30 pm CDT.

  5. identified Apr 10, 2026, 07:34 PM UTC

    Our team is continuing to work on deployment in order to fully address this issue. We will follow up with additional information by 3:30 pm CDT.

  6. monitoring Apr 10, 2026, 09:15 PM UTC

    Our team has deployed the necessary changes and the login issue should now be resolved. Users that are still unable to login should refresh their browser. We will continue to monitor systems throughout the weekend.

  7. resolved Apr 11, 2026, 05:28 PM UTC

    After monitoring the situation overnight, we have not received any additional reports.

Read the full incident report →

Minor March 16, 2026

AT&T service degradation in North America (SMS/Text)

Detected by Pingoru
Mar 16, 2026, 05:12 PM UTC
Resolved
Mar 16, 2026, 11:44 PM UTC
Duration
6h 32m
Affected: AlertsThird Party Services
Timeline · 3 updates
  1. monitoring Mar 16, 2026, 05:12 PM UTC

    AT&T is currently experiencing SMS service outages in North America. The following Apptegy services could be impacted: - Text Messages sent to AT&T users may be delayed - Analytics for Alerts sent to AT&T may take longer to populate - Guardians attempting to login via 2FA may not be able to receive codes if their cellular service is provided by AT&T

  2. monitoring Mar 16, 2026, 07:41 PM UTC

    We have verified that SMS-based text messages (like those sent from Alerts) are not impacted by AT&T's outage. Our telephony provider has confirmed that only RCS messages are impacted by AT&T's service outage. Our Third Party Status tracker will be moved back to 'Operational' if no additional issues are found by the end of business today.

  3. resolved Mar 16, 2026, 11:44 PM UTC

    No new incidents have been reported by our telephony provider. The service degradation previously mentioned caused no issues with SMS delivery rates for Alerts or Rooms for AT&T users.

Read the full incident report →

Minor March 12, 2026

Some CMS pages are inaccessible

Detected by Pingoru
Mar 12, 2026, 09:55 PM UTC
Resolved
Mar 12, 2026, 11:56 PM UTC
Duration
2h 1m
Affected: Media/CMS
Timeline · 5 updates
  1. identified Mar 12, 2026, 09:55 PM UTC

    Our team has identified an issue where some CMS pages are not loading properly. We have identified the root cause and are preparing a fix. We will follow up with additional information by 5:30PM CDT.

  2. identified Mar 12, 2026, 10:28 PM UTC

    We are testing and confirming our prepared fix and expect to deploy it shortly. We expect to resolve this issue no later than 6:30PM CDT.

  3. identified Mar 12, 2026, 11:29 PM UTC

    Our team is still verifying that our tentative solution will effectively resolve the issue. Our revised resolution time is now 7:00PM CDT.

  4. identified Mar 12, 2026, 11:52 PM UTC

    Our team is preparing to deploy. Our expected resolution time is now 7:30PM CDT.

  5. resolved Mar 12, 2026, 11:56 PM UTC

    This issue has been resolved. The previously impacted CMS pages are now accessible.

Read the full incident report →

Minor March 2, 2026

Document folder links are not resolving as expected

Detected by Pingoru
Mar 02, 2026, 10:42 PM UTC
Resolved
Mar 02, 2026, 11:13 PM UTC
Duration
31m
Affected: Client Websites
Timeline · 2 updates
  1. identified Mar 02, 2026, 10:42 PM UTC

    Some links to Document folders are not loading as expected. Our team has identified the root cause and we are working on implementing a fix. Documents are still accessible when navigating from the root documents directory (*example-domain*.com/documents), only direct links to folders are exhibiting issues.

  2. resolved Mar 02, 2026, 11:13 PM UTC

    Document folder links are now loading properly. This issue has been resolved.

Read the full incident report →

Major February 25, 2026

Rooms Service Degradation

Detected by Pingoru
Feb 25, 2026, 06:33 PM UTC
Resolved
Feb 25, 2026, 06:38 PM UTC
Duration
5m
Affected: Rooms
Timeline · 2 updates
  1. identified Feb 25, 2026, 06:33 PM UTC

    Rooms performance is currently degraded, resulting in some Rooms services being unreachable. Our team is implementing a fix and expect to have an update posted within the next 15 minutes.

  2. resolved Feb 25, 2026, 06:38 PM UTC

    Rooms has returned to normal operation and we have confirmed that all services are healthy.

Read the full incident report →

Minor February 19, 2026

US Cellular service degradation in North America

Detected by Pingoru
Feb 19, 2026, 07:53 PM UTC
Resolved
Feb 24, 2026, 05:37 PM UTC
Duration
4d 21h
Affected: AlertsThird Party Services
Timeline · 5 updates
  1. investigating Feb 19, 2026, 07:53 PM UTC

    US Cellular is currently experiencing service outages in North America. The following Apptegy services could be impacted: - Alerts (both SMS and Calls) sent to US Cellular users may be delayed - Analytics for Alerts sent to US Cellular may take longer to populate - Guardians attempting to login via 2FA may not be able to receive codes if their cellular service is provided by US Cellular

  2. identified Feb 20, 2026, 10:46 PM UTC

    Our carrier partner has identified a recent increase in failed deliveries at the operator. They have opened an investigation with US Cellular in order to determine a root cause.

  3. monitoring Feb 23, 2026, 10:31 PM UTC

    An investigation by our carrier partner found that US Cellular was incorrectly processing incoming messages, resulting in a decreased Alert success rate. This issue has been addressed by US Cellular as of 3pm CST. We expect that Alert delivery to US Cellular recipients has returned to normal, however we will continue to monitor Alert delivery rates.

  4. monitoring Feb 24, 2026, 04:07 AM UTC

    An investigation by our carrier partner found that US Cellular was incorrectly processing incoming messages, resulting in a decreased Alert success rate. This issue has been addressed by US Cellular as of 3pm CST. We expect that Alert delivery to US Cellular recipients has returned to normal, however we will continue to monitor Alert delivery rates.

  5. resolved Feb 24, 2026, 05:37 PM UTC

    US Cellular alert delivery rates have returned to normal operation.

Read the full incident report →

Looking to track Apptegy downtime and outages?

Pingoru polls Apptegy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Apptegy reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Apptegy alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Apptegy for free

5 free monitors · No credit card required