- Detected by Pingoru
- Jun 17, 2026, 03:56 PM UTC
- Resolved
- Jun 15, 2026, 09:15 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jun 17, 2026, 03:56 PM UTC
On the evening of June 15th, 2026 between 4:15 PM and 9:00 PM CDT, we observed instances where Alerts and Analytics were delayed. Our engineering team identified the root cause and implemented the necessary changes to address this issue.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 02:26 PM UTC
- Resolved
- Jun 12, 2026, 06:52 PM UTC
- Duration
- 4h 26m
Affected: Media/CMSThird Party Services
Timeline · 2 updates
-
monitoring Jun 12, 2026, 02:26 PM UTC
We are currently observing Meta service degradation that could prevent Live Feed and News posts from being delivered to Facebook and Instagram. We will continue to monitor the situation and follow up with additional information as it becomes available.
-
resolved Jun 12, 2026, 06:52 PM UTC
Meta services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- May 15, 2026, 01:36 PM UTC
- Resolved
- May 15, 2026, 02:31 PM UTC
- Duration
- 54m
Affected: Media/CMS
Timeline · 2 updates
-
identified May 15, 2026, 01:36 PM UTC
We are currently investigating an issue where the Quick Links section is not displaying properly on some sites after an update yesterday evening. Our team is in the process of issuing a fix, we will update this status by or before 9:30am CT.
-
resolved May 15, 2026, 02:31 PM UTC
Our team has identified the issue that caused the Quick Links header section to not display as expected. A fix has been implemented and headers should now be displaying properly on websites. Please reach out to Apptegy Support if you have any continuing quick link issues following our fix.
Read the full incident report →
- Detected by Pingoru
- May 14, 2026, 05:35 PM UTC
- Resolved
- Jun 03, 2026, 02:55 PM UTC
- Duration
- 19d 21h
Timeline · 2 updates
-
monitoring May 14, 2026, 05:35 PM UTC
Apptegy’s Security and Infrastructure teams have reviewed CVE-2026-42945 (https://nvd.nist.gov/vuln/detail/CVE-2026-42945) and determined that our systems are not impacted, as our existing configurations prevent the vulnerability from being exploited. We will continue to monitor the situation as it evolves and plan to upgrade our NGINX servers as a precautionary measure when feasible.
-
resolved Jun 03, 2026, 02:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- May 08, 2026, 08:38 PM UTC
- Resolved
- May 15, 2026, 02:41 PM UTC
- Duration
- 6d 18h
Affected: Third Party Services
Timeline · 2 updates
-
monitoring May 08, 2026, 08:38 PM UTC
At this time, we have no reason to believe that Apptegy or any data under Apptegy's care has been impacted by the recent Instructure security incident. Apptegy operates independently of Instructure and Canvas, and our platforms do not share infrastructure with the affected systems. Our Incident Response and Support teams are actively monitoring the situation for any developments and will assess any downstream implications as new information becomes available. If anything changes that could affect you, we will communicate it promptly and transparently. Our Support team is available to assist if you have any questions or concerns.
-
resolved May 15, 2026, 02:41 PM UTC
This incident has been resolved.
Read the full incident report →
- 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
-
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.
-
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 →
- 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
-
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.
-
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 →
- 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
-
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.
-
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.
-
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 →
- 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
-
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.
-
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
-
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.
-
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.
-
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.
-
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.
-
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 →
- 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
-
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
-
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.
-
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 →
- 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
-
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.
-
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.
-
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.
-
identified Mar 12, 2026, 11:52 PM UTC
Our team is preparing to deploy. Our expected resolution time is now 7:30PM CDT.
-
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 →
- 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
-
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.
-
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 →
- 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
-
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.
-
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 →
- 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
-
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
-
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.
-
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.
-
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.
-
resolved Feb 24, 2026, 05:37 PM UTC
US Cellular alert delivery rates have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Jan 25, 2026, 06:42 PM UTC
- Resolved
- Jan 26, 2026, 02:06 AM UTC
- Duration
- 7h 23m
Affected: AlertsThird Party Services
Timeline · 3 updates
-
monitoring Jan 25, 2026, 06:42 PM UTC
Our carrier partners are currently observing delays with voice calls. Alerts sent during this time may take longer to complete, and analytics may take longer to populate. Alerts are still being successfully sent, please do not send duplicate Alerts at this time.
-
monitoring Jan 25, 2026, 11:15 PM UTC
Our carrier partner has confirmed that they have deployed additional resources and as a result, Alert voice call turnaround time has begun to improve. We will continue to monitor services and ensure that Alert delivery is as efficient as possible.
-
resolved Jan 26, 2026, 02:06 AM UTC
Alert performance has remained healthy following our carrier's deployment of additional resources. We will continue to actively monitor Alerts performance throughout the week to ensure efficient delivery.
Read the full incident report →
- Detected by Pingoru
- Jan 22, 2026, 11:07 PM UTC
- Resolved
- Jan 23, 2026, 03:10 PM UTC
- Duration
- 16h 3m
Affected: Third Party Services
Timeline · 2 updates
-
monitoring Jan 22, 2026, 11:07 PM UTC
Microsoft has reported that Microsoft 365 services are currently experiencing degraded service functionality. Their service issues currently impact email delivery, which may impact the following Apptegy services: - Delivery of Alerts sent to email providers that utilize Microsoft 365 may be delayed - Delivery of 2FA (2 Factor Authentication) codes used to authenticate Staff or Guardians when logging in https://status.cloud.microsoft/
-
resolved Jan 23, 2026, 03:10 PM UTC
Microsoft 365 services have returned to normal operation.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 07:37 PM UTC
- Resolved
- Jan 15, 2026, 05:17 PM UTC
- Duration
- 21h 39m
Affected: Third Party Services
Timeline · 2 updates
-
monitoring Jan 14, 2026, 07:37 PM UTC
Verizon is currently experiencing service outages in North America. The following Apptegy services could be impacted: - Alerts (both SMS and Calls) sent to Verizon users may be delayed - Analytics for Alerts sent to Verizon 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 Verizon. Other cellular carriers like Xfinity Mobile may be impacted due to their reliance on the Verizon network.
-
resolved Jan 15, 2026, 05:17 PM UTC
Verizon has confirmed their outage was resolved yesterday, January 14th, at 10:15 PM Eastern Time. https://www.verizon.com/about/news/update-network-outage
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 08:15 PM UTC
- Resolved
- Jan 09, 2026, 09:18 PM UTC
- Duration
- 1h 3m
Affected: Third Party Services
Timeline · 3 updates
-
identified Jan 09, 2026, 08:15 PM UTC
Apptegy support chat is currently unavailable due to an issue with our third party partner, Intercom. We are working with them to resolve this issue as quickly as possible, you can view their status page here: https://www.intercomstatus.com/us-hosting We will continue to update our status here as we have more information. Please reach out to your Client Success Manager if you need anything in the meantime.
-
monitoring Jan 09, 2026, 08:54 PM UTC
Intercom has reported that they have implemented a fix and are monitoring for recovery. We will mark this resolved once we have confirmation from the Intercom team.
-
resolved Jan 09, 2026, 09:18 PM UTC
Apptegy chat support has remained operational following Intercom's recent fix. This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 15, 2025, 12:13 AM UTC
- Resolved
- Dec 16, 2025, 12:44 AM UTC
- Duration
- 1d
Affected: Alerts
Timeline · 6 updates
-
identified Dec 15, 2025, 12:13 AM UTC
We are observing delays related to Analytics within Alerts. Our engineering team is actively investigating this issue and our support team is monitoring for anyone reaching out.
-
identified Dec 15, 2025, 12:46 AM UTC
We are currently observing delays with Analytics becoming available and Alerts being sent. While Alerts traffic is delayed, they are still being sent successfully. Please do not attempt to resend at this time. Our support team is actively monitoring this issue and will remain online until service performance returns to normal.
-
identified Dec 15, 2025, 01:36 AM UTC
We have added additional capacity in order to reduce delays with Alerts and Analytics. We are still working through the current backlog, so you may still observe Alerts taking longer than normal. We will continue to provide updates here as services return to normal.
-
identified Dec 15, 2025, 02:22 AM UTC
We are no longer encountering delays with Alerts being sent, however Analytics updates are still experiencing delays. Our team is continuing to monitor system health and post updates here as soon as possible.
-
monitoring Dec 15, 2025, 03:07 AM UTC
Alerts have continued to send without unexpected delays over the last 45 minutes. Analytics are now also populating as expected. We will continue to monitor system performance to ensure that we maintain normal operation.
-
resolved Dec 16, 2025, 12:44 AM UTC
Alerts system performance has remained healthy following our upgraded capacity. This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 09, 2025, 12:06 AM UTC
- Resolved
- Dec 09, 2025, 11:34 PM UTC
- Duration
- 23h 27m
Affected: Media/CMSOther Services
Timeline · 5 updates
-
identified Dec 08, 2025, 04:16 PM UTC
We are currently experiencing delayed responses from Apptegy services that support functionality for the areas of the platform listed below. Public facing websites should not be impacted at this time. Impacted areas: - Live Feed - News - Documents - Events - CMS page editing We are working to return these services to normal operation very soon. We will post an update no later than 11am CST.
-
monitoring Dec 08, 2025, 04:59 PM UTC
We’re seeing improvements in performance and continuing to monitor the affected services.
-
monitoring Dec 09, 2025, 12:06 AM UTC
We are still observing instances of degraded performance. We have scheduled maintenance beginning today at 11:00pm Central Time. During this maintenance window, some Media, Alerts, and CMS services will be unavailable. Public facing websites will remain accessible. Scheduled Alerts will still be delivered during this maintenance window. We will provide an update once this maintenance has been completed.
-
monitoring Dec 09, 2025, 05:49 AM UTC
We have completed our planned maintenance and all services have returned to normal operation. This incident will remain open for an observation period while we verify services are performing as expected.
-
resolved Dec 09, 2025, 11:34 PM UTC
We have monitored system performance today and have not observed any unusual activity. This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 09:35 PM UTC
- Resolved
- Dec 05, 2025, 10:31 PM UTC
- Duration
- 55m
Affected: Rooms
Timeline · 2 updates
-
identified Dec 05, 2025, 09:35 PM UTC
We have identified an issue that may prevent staff users from creating new Announcements within Rooms on iPhone in the Apptegy Staff app (Thrillshare Mobile). Our team has identified a resolution and submitted the updated version of the app to Apple for approval. We expect that this update will be available within the App Store no later than the end of the day Monday, December 8.
-
resolved Dec 05, 2025, 10:31 PM UTC
The Apptegy for Staff app update has been published to the App Store: https://apps.apple.com/us/app/apptegy-for-staff/id1024147876 This has resolved the issue where staff were intermittently unable to create new Announcements.
Read the full incident report →
- Detected by Pingoru
- Nov 12, 2025, 05:41 PM UTC
- Resolved
- Nov 13, 2025, 04:32 PM UTC
- Duration
- 22h 51m
Affected: Rooms
Timeline · 2 updates
-
investigating Nov 12, 2025, 05:41 PM UTC
We are aware of instances where badges in Rooms are not presenting an accurate count of unread messages. Email and Push notifications are still being delivered as expected. We have confirmed the root cause is related to one of our third party providers and we are working with them to resolve this as quickly as possible.
-
resolved Nov 13, 2025, 04:32 PM UTC
This issue was resolved at 10:16am CST. Message badges should now be accurately reflecting the count of unread messages within Rooms.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 09:15 PM UTC
- Resolved
- Oct 21, 2025, 10:45 AM UTC
- Duration
- 13h 30m
Affected: RoomsThird Party Services
Timeline · 4 updates
-
identified Oct 20, 2025, 09:15 PM UTC
Apptegy is currently investigating an issue that is impacting Rooms login on iOS (Apple) mobile devices, which appears to be related to LaunchDarkly, a third-party service our system relies on. This is likely also due to the ongoing AWS Outage. We are working to gather more information and will provide an update as soon as we know more. We appreciate your patience and will continue to keep you updated at status.apptegy.com!
-
identified Oct 20, 2025, 09:34 PM UTC
Important note! If you're on an iOS (Apple) mobile device and cannot login to your District's Rooms account, please use your mobile browser (i.e. Google Chrome, Safari, etc.) and navigate to rooms.thrillshare.com to login to your account.
-
monitoring Oct 21, 2025, 03:19 AM UTC
We are seeing improvements in the login experience on iOS (Apple) devices for users attempting to access District mobile apps. We will continue to monitor the situation through tomorrow morning.
-
resolved Oct 21, 2025, 12:20 PM UTC
✅ Resolved Oct 21, 5:43 AM ET The login issue impacting Rooms access on iOS (Apple) devices has been fully resolved. The root cause was linked to a downstream issue with a third-party service (LaunchDarkly), which was affected by the broader AWS outage in the US-EAST-1 region. The third-party provider has recovered, and Apptegy systems are now operating normally. iOS users can log in through the mobile app without issue. We will continue to monitor performance throughout the day. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 03:03 PM UTC
- Resolved
- Oct 21, 2025, 03:30 AM UTC
- Duration
- 12h 27m
Affected: Third Party Services
Timeline · 4 updates
-
identified Oct 20, 2025, 03:03 PM UTC
Apptegy has identified the root cause of the issue, which appears to be related to Amazon Web Services, a third-party service our system relies on. This may cause issues logging into Thrillshare and cause delays in response times for support. Amazon Web Services (AWS) is used broadly and is impacting services many applications rely on to maintain connections to users and data, and as such may impact data for Alerts and Rooms as well as website availability. We are actively monitoring the situation and working to mitigate impact where possible. We’ll continue to post updates as we learn more or as the situation changes. Thank you for your continued patience and please check back at status.apptegy.com for the most recent updates!
-
monitoring Oct 20, 2025, 09:41 PM UTC
We are continuing to monitor the AWS Outage and it's impact on our platform and other third party vendors.
-
monitoring Oct 21, 2025, 03:18 AM UTC
We are seeing improvements in the login experience on iOS (Apple) devices for users attempting to access District mobile apps. We will continue to monitor the situation through tomorrow morning.
-
resolved Oct 21, 2025, 12:22 PM UTC
✅ Resolved The broader service disruptions caused by the AWS US-EAST-1 region outage have been fully resolved. The incident impacted several third-party dependencies that Apptegy services rely on. All systems are now operating normally. We will continue to monitor for any residual effects and appreciate your patience during this time.
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2025, 01:39 PM UTC
- Resolved
- Oct 15, 2025, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 16, 2025, 01:39 PM UTC
We experience a brief performance degradation of our Engage newsletter product during the evening of October 15th from 6:00 - 6:15pm ET. ✅ Next Steps: We will continue monitoring system performance to ensure ongoing stability. ✅ Stay Updated: Visit status.apptegy.com for future service updates.
Read the full incident report →